Planning and documentation – quality from the start
The best quality assurance consists of good planning, a structured approach and regular contact with the customer and end user.
In our experience, a well-planned and stable software architecture has a positive effect on quality and can be flexibly adapted to new requirements and environments - even years later.
We carry out tests continuously even during the planning phase, for example to check the technical feasibility of selected requirements or to measure the performance of key components.
For every case
In our test database we collect test scenarios that map planned processes and requirements. These are used once the components have been completed. We distinguish between tests for the setup (installation tests), tests of operation by the user (system tests) and tests of the code (unit tests).
The test cases are collected during planning and development, incorporated into our test planning and refined. The test cases can be carried out both manually and automatically.
Black-box and white-box tests
Strictly speaking, system and installation tests simulate the user's operating steps. These are known as black-box tests. Black box means that the software code is not taken into account.
In white-box tests, knowledge of the software code is taken into account. Unit tests allow this to be controlled precisely. This makes it possible to carry out stress tests as well as to examine performance and behaviour in the event of incorrect input. We use Visual Studio for unit tests.
kununu