...
The first version (1.0) of the Testbed will cover the following PEPPOL AS2 and AS4 profile use cases:
- System under test (SP AP) is receiving
- Positive tests
- TB AP sends a valid document to service provider (SP) AP using a valid certificate (should pass) (of reasonable size)
- Document type ID/process ID/no SMP lookup (URL must be provided by test user in the Test Controller, forwarded to Backbone APs)
- Tast for the Testbed Controller: it must be possible to identify which Backbone AP sent out which file - correlate Backbone AP and sent out file;
- Verification; SP AP send file back to Testbed AP (see 2. a. i.) (maybe a problem because AP software changes are required!)
- Handle different Content-Transfer-Encodings (binary, base64, 7bit etc.) - for the payload (AS2 specific)
- Support SHA-1 and SHA-256 as MIC algorithms (AS2 specific)
- Try to verify if all the AS2 MDN HTTP headers are according to the specs (if proxying is possible) (AS2 specific)
- Document type ID/process ID/no SMP lookup (URL must be provided by test user in the Test Controller, forwarded to Backbone APs)
- TB AP sends a valid large (50 MB+) document to SP AP (should pass)
- Verification; SP AP sends file back in 2.a.ii
- Same verification steps as described above should be applied
- The SP AP implementation (not the instance under test!) needs to be on the list of CEF eDelivery compliant implementations (https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery+AS4+conformant+solutions) (AS4 specific)
- TB AP sends a valid document to service provider (SP) AP using a valid certificate (should pass) (of reasonable size)
- Negative tests
- TB AP sends an invalid document (valid SBDH without a payload) to SP AP (should fail with negative MDN)
- TB AP sends an invalid document (No SBDH, no payload at all) to SP AP (should fail with negative MDN)
- TB AP sends an invalid document (No SBDH, valid payload only) to SP AP (should fail with negative MDN)
- TB AP sends an invalid document (Invalid SBDH, XML syntax error) to SP AP (should fail with negative MDN)
- TB AP sends an invalid document (Invalid SBDH, missing mandatory field) to SP AP (should fail with negative MDN)
- TB AP sends an invalid document (SBDH endpoint ID differs from the Payload endpoint ID/or document type mismatch) to SP AP (out of scope for V1)
- TB AP sends a valid document to SP AP using an invalid certificate (expired PEPPOL AP certificate) (should fail)
- TB AP sends a valid document to SP AP using an invalid certificate (revoked PEPPOL AP certificate) (should fail) - may cause problems in practise; Error level warning only?
- TB AP sends a valid document to SP AP using an invalid certificate (with a non-PEPPOL certificate) (should fail)
- TB AP sends a valid document to SP AP using an invalid certificate (with a PEPPOL SMP certificate) (should fail)
- TB AP sends a valid document to SP AP using an old TLS version (e.g. TLS 1.1) (should be rejected by SSL handshake)
- Positive tests
- System under test is sending
- Positive tests
- SP AP sends a valid document to TB AP using a valid certificate
- Sending more than one different document type might be an issue for testing with real-life-test systems (out of scope for V1)
- Handle different Content-Transfer-Encodings (binary, base64, 7bit etc.) - for the MDN (AS2 specific)
- Verify if that all the AS2 HTTP headers have correct values (according to the AS2 specs and the PEPPOL proprofile) (AS2 specific)
- SP AP sends a valid large (50 MB+) document using a valid certificate
- Consider reasonable read timeout values
- SP AP sends a valid document to TB AP using a valid certificate
- Negative tests
- SP AP is sending a document type that is not supported by the TB AP (e.g. OrderResponse) (should fail with negative MDN/Receipt) (for a later version of the Testbedout of scope for V1)
- Verification: verify that the negative MDN was received
- Out of scope version 1: list of negative self-tests, that cannot be verified by the Testbed
- SP AP is sending a document type that is not supported by the TB AP (e.g. OrderResponse) (should fail with negative MDN/Receipt) (for a later version of the Testbedout of scope for V1)
- Positive tests
The first version (1.0) of the Testbed will also cover the following use cases (utilising an AS4 implementation):
- Testbed (TB) AP (XX AS4) sends a valid document to service provider (SP) AP using a valid certificate (should pass)
- TB AP sends an empty document to SP AP (should fail)
- TB AP sends a large (50 MB+) document to SP AP (should pass)
- TB AP sends a valid document to SP AP using an invalid certificate (should fail)
- Step 1 to 4are repeated for alternate AP implementations (TB will support this functionality out of the box but won't be enabled in version 1.0 since no other AP implementations will be integrated)
- SP AP sends a valid document to TB AP using a valid certificate
- SP AP is requested to send valid documents to TB AP (for available alternate AP implementations)
- SP AP requested to send to TB AP that uses an expired certificate in SMP response (transaction should never be initiated)
- SP AP requested to send to TB AP that uses a revoked certificate in SMP response (transaction should never be initiated)
In a long term scenario the centralized Testbed should be used for:
...
Requirements for the Testbed software
- What about GITB
- REST API needs to be defined
Next meeting: June 27th, 13:00 to 15:00 CEST
Attachments
Attachments |
---|