Introduction

The system provides different ways to control the requirements, with one of them being the requirement test.

Tests allow identifying problems or defects when meeting compliances and are a great way to ensure records are compliant, without depending on analyses made during audits.

We can imagine the following scenario: an organization goes through yearly audits but, in order to avoid problems, prefers its compliances to be evaluated during this period. 

Tests can verify requirements faster, as they do not involve as many steps as an audit process.

Tests can be done in two ways: by test case, for cases in which the requirement will always be tested in different ways. 

For example: when testing different screens from a software, specific characteristics will be evaluated for each screen.

Or by sample, with or without population, for cases in which sampling is necessary to test the requirement.

For example: it is not possible to evaluate whether all parts manufactured by a factory are compliant; thus, a sampling is made to apply the test.

See further details about the configuration of each test type:

• Creating a test plan by test case; 
• Creating a test plan by sample.