TCSI - Testing for providers

This page is written for education providers who have engaged a third-party Student Management Software (SMS) developer to build functionality to report to TCSI via APIs.

It outlines the types of testing you have told us about help increase your level of confidence in the solution, as well as how TCSI can support you with this. It also explains the types of testing being conducted as part of the TCSI project to help create a solution that is secure, reliable and meets the needs of both government and education providers.

For providers who are conducting TCSI testing using TCSI Data Entry file upload via the department, please see our For TCSI Data Entry users page.

What are some reasons you might be interested in testing directly with TCSI?

Through our engagement with you, we understand that you would like to directly test with TCSI for the following reasons:

Confirming and familiarising yourself with new reporting functionality: To confirm your SMS' reporting functionality and trial new processes, changes to data elements, validation rules etc.
Required for software implementation: Some providers may need to perform additional customisation, configuration or integration on top of a vendor’s product. If you anticipate that this may impact your SMS’ interaction with TCSI, the best approach is to co-ordinate and arrange direct test access for your provider organisation through your vendor.

Setting up for API testing

Establish test data

Whilst actual live or production data should not be used for testing purposes, providers can consider using de-identified data, with the acknowledgement and confirmation of certain conditions. These conditions are:

The provider is sufficiently satisfied that the data has been de-identified in such a way that it cannot be un-scrambled or re-identified
In the event that this data is published or exposed externally, the provider maintains no concern to its privacy or security sensitivity. Essentially, the government will treat this data as unclassified material
In the event that data is able to be un-scrambled or re-identified, the provider holds all responsibility for this and any associated implications.

The department strongly advises providers to seek internal legal advice prior to exploring the usage of de-identified production data for testing in the TCSI test environment.

Mock CHESSN, TFN and USI

Commonwealth Higher Education Student Support Number (CHESSN)

Mock CHESSNs will be allocated in the test environment according to the CHESSN Management in TCSI guide. Reporting sufficient information against a student record will result in a mock CHESSN being allocated.

Tax file number (TFN)

Providers and developers can generate mock TFNs for testing. To reduce interaction between test accounts, the TFN must begin with the test provider code assigned for your test account. TFNs will verify if the final digit is an even number (2, 4, 6, or 8). All other final characters will return verification fail messages.

TFN must start with test provider code and end with an even number to verify

Unique Student Identifier (USI)

For assistance acquiring mock USIs, please see the System Developers - USI System and Support page via the Office of the Student Identifiers Registrar.

For checking the USI character algorithm in your software solution, please submit a USI Check Algorithm request via the Office of the Student Identifiers Registrar.

Configure your test account

The TCSI test environment refresh was successfully completed on 4 March 2023. All data reported by providers has been removed along with the system unique identifiers (UIDs).

Providers and TCSI developers can now apply for access to the test environment by completing the TCSI test account request.

The form requires:

a business case that outlines the intended use for the test account
contact details for the test account owner
confirmation that personal information will not be used in the test environment.

Our team will review requests and provide detail on next steps, including another form, if approval is received.

You can view a demonstration of the new test account process that was presented at our TCSI drop in session on 15 March 2023.

Report data

TCSI - Testing for providers

What are some reasons you might be interested in testing directly with TCSI?

Setting up for API testing