OVS Conformance for Schedule Publishers

This page provides a step-by-step guide for measuring the conformance with the DCSA OVS 3.0.0 standard of a schedule publisher application.

To access all conformance documentation, return to the DCSA Conformance page.

 

Create and configure the sandbox

Use the instructions in the Conformance Sandboxes page to create a sandbox with the following parameters:

Use the instructions in the Conformance Sandbox Configuration page to configure how the DCSA synthetic schedule consumer running in the sandbox will make API requests to your OVS schedule publisher application.

 

Run each scenario

Read the Conformance Scenarios page to understand the key concepts involved in executing DCSA conformance scenarios to measure the conformance of your application with the implemented DCSA standard.

Start each scenario from the sandbox home page that is supported by your application at this time, and perform each action as explained in the general scenario page above and illustrated in the example below.

 

Example OVS scenario run

This is a step-by-step example of running a typical OVS scenario:

• SupplyScenarioParameters(carrierServiceName)
• GetSchedules

 

Supply scenario parameters

As soon as you start the scenario, you will be prompted to supply the scenario parameters with which your application can run this scenario.

Copy the example JSON parameters into the text area below, and adjust each attribute to a value that would cause your application to accept an OVS schedules request received from the DCSA synthetic schedule consumer running in the sandbox:

 

Get Schedules

As soon as you submit the scenario parameters, the DCSA synthetic schedule consumer running in the sandbox will use the parameters to build and submit a request to your OVS application.

Once your application has received the request and responded with a list of schedules, the updated scenario status should look like this:

Press "Action completed" and confirm, to complete the step "Get Schedules", which also completes the scenario.

Back to the sandbox overview, the scenario is now complete and you can start another scenario, or restart the same one if there were errors that you want to fix in your carrier application and retest: