General principles
The scope of the test conformance suite includes integration testing, interoperability testing and peer to peer testing for both business and government transactions.
The test scope for SuperStream encompasses business-to-business AS4 ebMS message exchange and payload (XBRL) testing and also government-to-business USM and EPF.
The testing also makes reference to the ATO enabling services, which are as follows:
- SuperTICK – SBR within the ATO own this service which is referenced as part of the data standard
- FVS – SBR within the ATO own this service which is referenced as part of the data standard.
B2B test use cases are initiated from fund registry systems, therefore processes will vary to capture the required set of data to support a rollover transaction. The test cases defined in this document will provide a generic set of steps to support these activities. It is the responsibility of the fund to capture data in their specific process.
To streamline testing the following rules apply to registry system testing:
- If multiple funds use a common registry system, a single pass through for a chosen fund would constitute a pass for all other funds associated with the registry system.
- In a more complex environment, that contains multiple registry systems with various funds, at least one fund within each registry system should be tested as best practice.
- One Unique Superannuation Identifier (USI) (product) for each fund is the minimum requirement for testing. Funds are not expected to test all products within their systems.
Integration test cases
Integration test cases are the responsibility of each solution implementation team.
A checklist of integration test cases is provided and represents the minimum requirement – see Integration test cases. The full extent of integration testing will need to be agreed between each fund and their solution provider/s.