We are committed to ensuring that all software which is released to our clients undergoes rigorous testing and QA signoff.
This article summarises our approach to Quality Assurance prior to the release of new versions of time@work and expense@work.
Our QA Team has developed a rigorous testing procedure to ensure the correctness, completeness, security and quality of the solutions developed and implemented by systems@work.
In particular our testing methodology is designed to focus on the reliability, stability, maintainability and usability of our applications.
The “Testing Cycle” used by systems@work is based on industry standard methodologies and can be summarised as follows:
1. Requirements & Design Analysis:
We review the design specifications for the release and the functionality which is expected to be included or modified in the release. During this phase our testers also work with the developers in determining what aspects of a design are testable and under what parameter those tests work.
2. Test Planning & Development:
Here the Test Strategy is created and the Test Plan(s) produced. The Test Plan will include details of the Test Procedures and Scenarios.
3. Test Execution:
Testers execute the software based on the plans and tests and report any errors found to the development team.
4. Test Reporting:
Once testing is completed, testers generate metrics and make final reports on their test effort and whether or not the software tested is ready for release.
5. Retesting the Defects
In common with most software companies once the internal testing is complete we may release software under a beta programme. In this situation versions of our software, known as beta-versions, are released to a limited audience of clients and prospects outside of systems@work. This is done so that further testing can ensure the product is tested in live “real world” environments.
For further information on our Testing and QA procedures please contact our Account Management or Support Departments.