Story status
Draft
Implementation status
Planned
Targetted user
Description
As a SUT operator, when I execute a test run through an intermediary tool that captures the messages exchanged between the two systems under test, I shall be able to see the messages that have been captured to select the ones that are relevant.
When I am executing a test case, for each test step, I shall see the list of messages that have been captured and that are relevant for the test step. The messages that are displayed shall be selected based on
- The timestamp (between the start time of the test or test step and now);
- The sending and receiving endpoints;
- The message type (or at least transaction or protocol if the message type cannot be identified)
For each message, I shall see:
- Timestamp,
- Sender (Ideally the tool resolves the system's keyword based on the hostname, or hostname, or IP address),
- Receiver (Ideally the tool resolves the system's keyword based on the hostname, or hostname, or IP address),
- Message type.
The information used as "message type" may vary depending on the underlying protocol:
- For HL7v2: use content of MSH-9 (message type) + MSH-12 (HL7v2 version)
- For HTTP SOAP: use the Action element of the SOAP header
- For HTTP RESTful: Operation (HTTP VERB) + Resource type
- For DICOM: Action and SOP Class
- For Syslog: MSGID and optionally when MSGID = "IHE+RFC-3881", the value AuditEvent/EventIdentification/EventTypeCode@csd-code
Jira issue