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.

Can I test file uploads using TCSI Data Entry (previously known as the TCSI Portal)?

Services Australia (SA) and the Department of Education, Skills and Employment (DESE) are conducting TCSI Data Entry testing internally. We are working through options to allow providers to test file uploads. If there are specific scenarios you would like to verify with us, let us know and we can work with you on them.

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, 2020 data elements, validation rules etc.
  • Verifying migrated data: To be confident that historical data has been migrated correctly to TCSI.
  • Required for software implementation: Require integration testing as part of any additional development and customisation that enables your implementation.

How will TCSI support you for each of these scenarios?