Prerequisite
As a SUT Operator I have selected a test case to execute and the test partners for this test case.
Description
As a SUT operator, before I can execute a test case against my test partner's system under test, I shall see the network details to contact it. It will allow me to configure my system under test to direct the messages to the correct network interface or to configure my application and/or firewall.
If an intermediary tool is used, I shall see the details in the same place as the SUT's details for sake of consistency and not to loose time, looking in various locations.
For any SUT, I need to know at least the IP address or FQDN.
For the SUT acting as responders in the test case, I shall see the port number to use (might be the details about the SUT or the intermediary tool). I also need to know whether the endpoint is secured or not and which versions of TLS are supported.
Depending on the underlying standard, I need additional details to be shared (regardless whether the SUT acts are responder or initiator):
- HL7v2: Application and Facility names;
- HL7v3: Device and Organisation identifiers;
- DICOM: AETitle.
If the transaction to be executed relies on the HTTP protocol, I shall know what is the resource path for the service(s) I need to hit.
When I initiate a given test case against another well-identified system under test, the tool shall show to any user who operates one of the systems under test involved in the test run:
- Whether the messages shall be exchanged directly between the SUTs or whether the messages shall go through an intermediary tool;
- For the intermediary tool (if needed):
- Its IP address or FQDN;
- The ports to be used for the different services hosted by all the SUTs involved in the test;
- For a given port, whether the communication is secured by MTLS or not
- For each system under test:
- Its IP address or FQDN;
- The ports to be used for the different services I need to contact to execute the test case;
- For a given port, whether the communication is secured by MTLS or not
- The list of TLS versions that are supported by the system under test;
- For HL7v2 based applications: the application and facility names
- For DICOM based application: the AETitle
- For HTTP based services, the path to the different resources
- For HL7v3 based application: the device and organisation identifiers.