Unit and Integration Testing

For each unit of code developed, the developer is responsible for unit testing their source code and logging the results (“Pass” or “Fail”) in the Unit and Integration Test Log with their signature. Prior to the migration of code to the Integration Testing environment, the Technical Lead and/or an assigned designee reviews the code and sign-offs as the reviewer.

Component Integration Testing does not start if any of the unit components defined within the integration component have failed Unit Testing. An assigned designee who was not involved in developing the unit components performs Integration Testing. Results of Integration Testing are also captured in the Unit and Integration Test Log.

This Unit and Integration Test Log provides supporting information, not limited to: description of source code, date of executed test, result of test (“Pass” or “Fail”), and name of tester.

System Testing

The purpose of system testing is to demonstrate the following:

1. The system provides:
   • Results in agreement with expected output for a range of inputs and scripts
   • Intended responses and error messages for a range of incorrect inputs
2. The functional requirements are successfully implemented
3. The technical design is sound

Performance Testing

The performance testing focuses on ensuring that the performance criteria setup by the business are satisfied.

User Acceptance Testing

Upon completion of confirmed requirements, Ishi’s business process resource works in conjunction with designated business users to derive test scenarios based on the requirements. These scenarios act as the template or an outline for the tests required during UAT.