Operational test

This article or the following section is not adequately provided with supporting documents ( e.g. individual evidence ). Information without sufficient evidence could be removed soon. Please help Wikipedia by researching the information and including good evidence.

Evidence is missing. - SteEis ( Discussion  |  Rating  |  Posts ) 11:11, December 11, 2018 (CET)

In software development, the term operational test describes a series of coordinated tests that are intended to prove that the software meets the needs of the company and is working correctly.

The operational test is the last step in the project plan before commissioning. An alternative to the operational test is parallel processing. After the successful operational test, the key date is changed to the software system to be introduced .

The operational test is carried out in the company that will put the software into operation after a successful test. The operational test takes place shortly before commissioning and often in parallel with employee training .

If the company gives the okay for commissioning based on the operational test, then this okay is in fact equivalent to acceptance of the software. Defects that occur afterwards must be remedied in accordance with the agreed warranty.

Requirements for the operational test are:

• All hardware and software components are installed and tested ready for operation.
• The development of the software has been completed and tested in accordance with the specification.
• The software works stably.

The operational test should encompass all functions of the software with practical tasks:

• The data required for the test correspond to real data
• The data input and the handling of the software are carried out by experienced employees of the customer. These employees have been trained in advance on the software to be introduced.
• The operational test should also correspond to the company's quantity structure.