Test and Inspection Management

Tests and inspections are used to describe the checks that must be carried out before a product is put into service, or on an ongoing basis during production and operation.

• Examples of test applications
• How to use tests
• The test documentation also includes a record of its execution
• Common questions
  • You can't create a protocol for the test
• You can't add a request to the test

Examples of test applications

• Software checks following integration
• Checks on the finished product before commissioning
• Handover inspection of a completed flat
• Ongoing checks on the correct functioning of technical equipment

All the cases listed have a defined inspection procedure, which usually includes points specific to the particular product; the tests are derived not only from the product itself and its characteristics, but also from general standards (e.g. requirements for electrical inspections). A test for a product or part thereof therefore includes a description of what needs to be checked, with the option of referring simultaneously to the regulations and standards taken into account in the test.

How to use tests

Tests are

• Part of the project documentation, where they cover tests carried out during the project, or
• Part of quality and safety management, where they describe ongoing checks as part of the operational management of production, buildings and technical equipment

Tests are typically created at the same time as the environment and the elements being tested are prepared. In AyMINE, tests are linked to

• To the requirements they test,
• The activities that carry them out,
• Descriptions of the elements being tested

The test documentation also includes a record of its execution

The test itself serves as documentation of how the testing should be carried out. It is not a record of the testing activity. Therefore, alongside the tests, the following are created:

• Tasks within which the tests are carried out. Tasks may be carried out repeatedly, meaning that the tests are repeated
• Records of the test results. These always relate to a specific execution of the test

Common questions

You can't create a protocol for the test

A test is a documentation of how to perform a specific test – effectively a test assignment. The test itself is performed on the basis of a task; ideally a test task.

A protocol is automatically created from the task on the individual progress steps (on the activity tabs). New Protocol button can also create a complex protocol and insert all necessary attachments in documents.

You can't add a request to the test

You can add a request to the test. On the relations tab you can select a request and attach it. Directly by the New (relationship) button.

What are the types of tests, what they are for and what they are based on is discussed in this article.