Iterative, Final/terminal

Types of testing: Iterative, Final/terminal

2.3.2 Testing

Testing — Note 2 of 5

The difference between testing modules of a program during development and testing the program at the end of production

What you need to know

Testing takes place at two main stages. Iterative testing happens throughout development: individual modules or sub-programs are tested as they are built, and results are used to make improvements. Final (terminal) testing happens at the end of development and tests the complete program, including alpha testing (by developers) and beta testing (by end users).

What to know

Iterative testing: individual modules are tested as they are built; results are used to make improvements immediately.
Alpha testing is carried out in-house by the development team to fix remaining issues.
Beta testing is done by real end-users before the final release.
Both types of testing are needed: iterative catches bugs early, final testing checks the whole system.

Key terms

Iterative testing: Happens DURING development / whilst writing the program / before development is complete.
Final/terminal testing: Happens at the END of development, testing the whole/complete program before release.

Exam technique

Tip:'When is iterative testing performed?' → DURING development / whilst writing the program / after each module is completed.
Tip:When naming a test type, give the NAME then DESCRIBE it. 'Iterative testing — completed during development after each module' scores. 'Boundary — testing the boundary' does NOT score (just repeats the name).

Ready to test yourself?

Practise 2.3.2 questions

← Previous noteTesting2.3.2 Testing Next note →Syntax and logic errors2.3.2 Testing

Back to Testing

Revise another OCR GCSE topic: Defensive Design