Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Launch the service from VidiNet Dashboard.

...

You can choose to automatically connect and configure the Baton QC service to your VidiNet-based VidiCore API instance by selecting a target instance in the “VidiCore API” dropdown. You will need to provide VidiCore API credentials in order for VidiNet to apply the configuration:

  1. a Baton QC service endpoint in /API/resource/vidinet

  2. a set of sample Baton QC Test Plans in /API/analyze-preset

Once the service has been launched successfully, it will appear under “My Services” in the VidiNet Dashboard. This is where you will be able to see service connection details, spend summary, service credentials, and more.

Manual service configuration

If you do not select a target VidiCore API instance (e.g. if you are running VidiCore API locally), you need to manually configure your VidiCore instance with a service endpoint. The instructions on how to do this can be found in the APIdoc. You also need to manually add Test Plans to your VidiCore API instance. The instructions for this can be found here.

Usage instructions

Instructions on how to use the Baton QC service, from the VidiCore API, can be found in the APIdoc.

Import custom Test Plans

For existing or advanced users of Baton QC, custom Test Plans from any on-prem Baton QC Enterprise system can easily be imported to VidiCore for use with the VidiNet Baton QC Service. Read more here.

Using Dynamic Parameters

For very advanced users of Baton QC, the ability to use Dynamic Parameters is supported (= override Test Plan settings as part of the job instruction). Read more here

Once the service has been launched successfully, it will appear under “My Services” in the VidiNet Dashboard. This is where you will be able to see service connection details, spend summary, service credentials, and more.

Usage instructions

Instructions on how to use the Baton QC service, from the VidiCore API, can be found in the APIdoc.