Testing
We start by supporting our clients to define the most appropriate test strategy, including the final user acceptance criteria, and then help plan the different phases and their outputs. We also provide necessary support to meet objectives.
Our testing process is divided into four main parts:
- Unit Tests: for testing parameterisation and programming components
- Module Tests: for testing business modules separately and independently
- System Integration Tests: for testing the Avaloq Banking System in an integrated environment within an end-to-end business view
- User Acceptance Tests: for performing the final business tests to ensure that the Avaloq Banking System meets acceptance criteria and is ready for production.
On top of the tests mentioned above, we run a series of parallel day tests, where each business user records all the transactions and modifications made within the existing banking system over a given day and then enters them into Avaloq Banking System to compare and analyse the results between the two systems.
The idea is to have a complete business day as a test set, instead of relying on predefined test cases. This makes the tests much more robust. Furthermore, parallel day tests help business users get better trained on the Avaloq Banking System by doing ‘real’ work, thus increasing their confidence and ability with the system.
To make sure all tests cycles run smoothly, we organise training sessions prior to each testing phase. This gives everyone involved the know-how needed to handle the system effectively.
Progression through each test phase is a formal process and there are clear check points to ensure each transition is acceptable.