The project consists of functional, manual tests that are carried out according to the specified scenarios, which contain individual test cases for which the corresponding data is created.

The documentation of test cases that test individual system functionalities in different contexts required a great deal of attention and concentration. The steps of each case and at the same time the expected results differ depending on the context, i.e. the test scenario in which they are used. Thus, individual forms are repeatedly tested in different contexts, which often differed in details.<br />The flexibility of the system configuration and the multitude of possible options made it difficult to comprehensively test the availability of the designed functionalities. Often the same components used in the same locations had different values and uses depending on the system configuration, the state of the facility and the role in which the activity was performed.

An in-depth analysis of the submitted test scenarios and an understanding of the relationship between a particular use case and its context proved to be key to success.
This was followed by a balanced assignment of individual scenarios for execution by the testers. Careful attention to logical and business process-compliant test execution sequences enabled efficient verification of the expected results of each test.
As part of the control and testing of the business process itself, the testers were paired up in pairs or threes. Each received their own set of scenarios, which were combined with the copies of the other testers to form a logical whole.
By taking turns executing the scenarios, they simulated the business process of case handling and the flow of information in the system.

The project was carried out in the form of an agile model in which the quantity and quality of the test scenarios were prepared for the individual sprints. Before the start of the sprint, the availability and stability of the test environment was checked, which was a prerequisite for the start of the work.
The sprints could be divided into the following phases:

• Phase I: Completeness analysis of the quantity and quality of the tasks in the sprint.
• Phase II: Checking the completeness and consistency of the documentation versions.
• Phase III: Carrying out tests.
• Phase IV: Summarising the results, discussing the identified defects with the contractor.
• Phase V: Presentation of the report in the sprint.

• Independent and professional opinion on the quality of the software created.
• Reliable and thorough functional testing in various configurations and aspects.
• Review of business processes and procedural issues during testing