The objective of testing is to prove that the application model supports the desired user behaviours. If the application does not support an impact, even if it works correctly from a technical perspective, it is something that needs to be corrected. Such an correction may have a cost impact, but this is outside the scope of the Genus Modeling Process.

 

Several types of tests are performed dependent of what has been built in the previous phase. If just a small amount of non-critical adjustments have been made, maybe just a selection of the test steps need to be run. If many adjustments have been made, or a few critical adjustments have been made, a full system test covering all test steps need to be run. The first step in the test phase is therefore to analyze risks and decide the scope of the test.

 

One or more of the following types of tests are then performed:

  • Unit Test. Testing the selection of steps in the test script that touches the bug fixes or adjustments within a single unit of the application.
  • Integration Test. If the bug fixes or adjustments affect the interaction between modules or applications, this interaction must be tested by performing a selection of steps in the test script.
  • System Test. The entire Application is tested by performing all the steps in the test script. Performed by the Contractor.
  • Acceptance test. As a System Test, but always performed by the Customer.

 

In order to move to the transition phase, the Customer must approve the tests by signing off the test documentation.