Receiver reviews received the message is ignored by message, ignoring payload the other party Any complexities in relation to certificates used for signing, compression etc., are eliminated by this simple test. It will, however, be necessary to have the SSL certificate configured to https to work INTERG1.3 Send a simplified As above plus the receiver Parties must communicate As above with manual message from the sender checks that the received to each the desired verification that the MSH to the receiver MSH message has PayloadInfo target ABN and target USI target/source ABN/USI with PayloadInfo part part properties correctly that they would like in the values in the partinfo properties configured for a configured for a target fund payload info part properties. properties are as requested particular source / target that their application knows Proper values are not fund combination about. This is just a manual strictly required for this test check as the MSH is not but setting them correctly required to perform this during this test means that type of validation of they will not need to be application layer entities changed in subsequent tests where they are required to match particular entities in application layer INTERG1.4 Test message signing and As above plus configure Tests that message signing Messages should be signed signature validation MSH to sign messages and validation works for and be successfully targeted at the partner you positive scenarios validated are testing with and validate the signature of messages received from that partner As plus configure an Tests that message Messages should be signed incorrect certificate for validation fails for negative and fail validation outgoing messages. Send a scenarios message and confirm that receiver responds with a SOAP fault INTERG1.5 Test message As above plus message Tests the sender/receiver Payload should be compression compression turned on MSH's message compressed across the wire but be uncompressed by functionality the receiving MSH and
Receiver reviews received message, ignoring payload the message is ignored by the other party Any complexities in relation to certificates used for signing, compression etc., are eliminated by this simple test. It will, however, be necessary to have the SSL certificate configured to https to work INTERG1.3 Send a simplified message from the sender MSH to the receiver MSH with PayloadInfo part properties configured for a particular source / target fund combination As above plus the receiver checks that the received message has PayloadInfo part properties correctly configured for a target fund that their application knows about. This is just a manual check as the MSH is not required to perform this type of validation of application layer entities Parties must communicate to each the desired target ABN and target USI that they would like in the payload info part properties. Proper values are not strictly required for this test but setting them correctly during this test means that they will not need to be changed in subsequent tests where they are required to match particular entities in application layer As above with manual verification that the target/source ABN/USI values in the partinfo properties are as requested INTERG1.4 Test message signing and signature validation As above plus configure MSH to sign messages targeted at the partner you are testing with and validate the signature of messages received from that partner Tests that message signing and validation works for positive scenarios Messages should be signed and be successfully validated As plus configure an incorrect certificate for outgoing messages. Send a message and confirm that receiver responds with a SOAP fault Tests that message validation fails for negative scenarios Messages should be signed and fail validation INTERG1.5 Test message compression As above plus message compression turned on Tests the sender/receiver MSH's message functionality Payload should be compressed across the wire but be uncompressed by the receiving MSH and
Rollover_v2.0_conformance_testing_guide_DRAFT_20170807.docx