Requirements as the heart of testing
Testing is part of all (digital) solutions, whether it's a mobile app, a progressive web app, a website or an IoT gadget. To know what exactly needs to be tested, you need clearly defined requirements. We're happy to support you in eliciting and defining the requirements for your product, a process known as requirement engineering.
Together, we define what your product needs to be able to do (functional requirements) and under what conditions it should run (non-functional requirements).
Functional requirements
Functional requirements usually involve features, for example: exactly what happens when button XY is clicked. Based on these requirements, we create user stories and define the acceptance criteria. User stories and acceptance criteria form the basis for creating test cases, which we use to perform and document the testing.
Non-functional requirements
Non-functional requirements describe how and under what conditions a function should behave – they can be categorized into performance and quality characteristics as well as constraints. This includes, for example, requirements for server locations or performance, data protection regulations, or system compatibility requirements. Depending on the product, the list can be nearly endless. We're happy to support you in identifying the requirements for your project.