Glossary · Engineering, integration and validation
Test case
Also known as: Test scenario
German: Testfall
In systems and software testing, a test case is a set of preconditions, inputs, actions and expected results, derived from a requirement or specification, used to check whether a test item behaves as intended. Test cases are traced to the requirements they cover.
- Validation
- Standards
In one sentence
A test case defines preconditions, inputs, actions and expected results used to check whether a system behaves as required.
Example
Test case TC-042: with the guard door open, press start; expected result: the conveyor does not start and message 1203 appears on the HMI.
How it applies
- Engineering: Test cases are derived from requirements and specifications. Each should test one clear behavior and state an observable expected result. ISO/IEC/IEEE 29119 describes test processes and documentation.
- Testing: Test cases are executed during module tests, Factory acceptance test (FAT), Site acceptance test (SAT) and after changes. Test coverage shows which requirements have test cases.
- Automation: Test cases for control software can be automated in Software-in-the-loop (SIL) setups and Continuous integration (CI) pipelines.
- Documentation: Test cases can also verify documentation, for example whether the manual's procedures produce the described result. The documentation team can reuse the preconditions and steps to check task instructions.
Test case vs. test procedure
A test case states what is tested and what result is expected. A Test procedure describes the sequence of actions to execute one or more test cases, including setup and equipment.