Testing

Aims of testing:

to provide certainty to software developers
to provide a repeatable, reliable and externally discoverable set of test cases
to ensure that software developers can retain end-to-end testing results for their own use
to provide a scalable and flexible test environment.

What software developers need to do in testing

Software developers will need to:

enable their product to use the SBR Taxonomy for the 'SBR Forms in scope testing schedule' - listed on Common components.
validate message prior to sending
test the end-to-end process (i.e. from the time the user initiates a reporting transaction to the time it is successfully completed)
provide feedback to SBR on the Software Developer Kit (SDK)
undertake compliance testing of their products, in accordance with the SBR compliance regime.

What the SBR Program will provide to software developers

SBR will provide the support and infrastructure needed to participate effectively in this testing.

SBR has:

created an external test environment to simulate the SBR production environment. This will cover all the component parts of SBR, including the generic facilities and the agency-specific services connected to them
defined all the SBR testing boundaries (including interfaces), as well as the entry criteria for each boundary interface
provided an SBR test coordinator for first level management and support of all boundary interfaces for the interconnected testing environments.

SBR will also:

ensure that SBR agencies have tested their own services involved in SBR to a standard sufficient for software developers to engage in their own testing
provide a suite of test services that can be used to test both the technical (web service) and business (e.g. activity statement) implementations. Supporting the test services will be a library of test credentials, Australian Business Numbers (ABN) and test data that can be assigned to software developers and will be recognised by agencies (these will be supplied as part of the registration process).
offer a simple message connectivity test (‘message.ping’) designed as an end-to-end connectivity test from business software, through core services, to agencies and back. Further details can be found in the Web Services Implementation Guide (WIG) available on the downloads page.

Simple message connectivity testing

Simple message connectivity testing commenced in October with software developers (both commercial and in-house) developing SBR-enabled products. Software developers can register for testing by providing business name and contact details in an email to SBRServiceDesk@ato.gov.au . SBR will acknowledge requests for registration by return email.

Following simple message connectivity testing software developers will be able to commence the SBR conformance testing of their products as outlined in the attached SBR Program Self-Certification Testing Guide (PDF 368KB).

More information

If you would like more information about SBR’s test plans, particularly how software developers can get involved, please email SBRServiceDesk@ato.gov.au