Example usage
Testing covers the whole software lifecycle, not just running the program. For a payroll system, testing includes reviewing the requirements for completeness (static testing), designing test cases from the payslip rules, executing them against the system (dynamic testing), and evaluating whether the system is fit for purpose. The goal is to determine that the system satisfies specified requirements, to demonstrate fitness for purpose, and to detect defects.
FAQ
What is the difference between testing and debugging? Testing is a process of planning, preparation, and evaluation to find defects and demonstrate quality. Debugging is the development activity of locating and fixing the cause of a detected defect. Testing finds the defect; debugging removes it.
Is testing only about executing the software? No. Testing includes static activities such as reviews of requirements, design, and code. Static testing finds defects without executing the software, often earlier and cheaper.
What does “fit for purpose” mean? That the software demonstrably meets the needs of its users and stakeholders in practice, beyond the letter of the specified requirements.
Can testing prove the absence of defects? No. Testing can only show the presence of defects, not their absence — exhaustive testing is impossible except in trivial cases.
Related terms
- static testing — reviews and analysis without execution
- dynamic testing — testing that executes the software
- test plan — documents how testing will be conducted
- test design — deriving test cases from the test basis
- test execution — running tests and comparing results
- test completion — the closing activities of the test process
- quality assurance — process-level activities that support testing
- debugging — locating and fixing defects found by testing
