In Requirement Based Testing, test cases are based on (prioritised) requirements. Every requirement results in one or more test cases. After test execution the test manager reports on test cases executed and issues found and solved.

However, this information is not sufficient to make a go/no-go decision as the Business thinks in terms of risk!

Risk Based Testing seems the solution. A list of (prioritised) product risks is created. Test cases are based on these risks. Reports state the risks covered. A better-founded go/no-go decision is possible.

To create test cases requirements are still necessary.

The solution is combining risks and requirements. Together with stakeholders from Business and IT a list of prioritised product risks is created. Every risk is linked to the related requirement(s). This way the test team might run into vague, contradicting or missing requirements. Issues are found at an early stage and solving them is especially important for product risks with a high priority. For requirements with no related risks, one can wonder whether they should be build or that they are redundant.

This track is intended for people who look for a test approach that assures that testing is tuned to the Business requirements.

Key points:
1. Risk and Requirement Based Testing assures that testing is done according to the business needs, which improves the Business Alignment.
2. Vague, contradicting or missing requirements are identified. Solving this increases the quality of the requirements and the quality of the test. It might also be input for process improvement.
3. Improved commitment from the business. Testing will be more appreciated.