Testing Glossary
From Software testing and development
This testing glossary tries to provide a common sense description for many of the testing terms regularly used in the world of testing.
Contents |
[edit] Black Box
Testing a system with no knowledge of the internal logic. This is testing the application as the user would use it.
[edit] White Box
Test cases are based on the internal logic of the application are called White Box tests. Analysing the code can ensure that each condition of each decision can be tested ensuring that every line of code is tested. White box testing is often more thorough, but also much more time consuming than Black box testing and requires some knowledge of development processes.
[edit] System Under Test (SUT)
Refers to the system being tested.
[edit] Test Condition
A test condition is anything that can be tested. This means that a test condition must have an observable result i.e. a result that can be tested. The test conditions are traditionally derived from the functionality defined in the Functional Specification.
[edit] Test Case
A Test Case provides the inputs and process required to validate a test condition. An expected result within the test case tells the tester what the correct outcome of following the test process should be.
Test Data can be separated from Test Cases improving reuse and maintainability.
[edit] Test Script
The term Test Script is typically used when refering to automated testing. It is a detailed set of instructions that are followed in order to test a strictly controlled outcome.
It is because of this rigidity that test scripts are often more costly to maintain than test cases
[edit] Test Data
This is the term given to data created to trigger a particular test condition. Often data must be reset or cleaned in order to rerun a test.
