AQA A2 Computing 7.3 Testing

Question 1

What are the 12 testing strategies?

Answer 1

Bottom-up testing
Top-down testing (aka interface testing or stub testing)
Mixed-level testing
Dry running (aka hand tracing, walkthroughs or desk checking)
White-box testing (aka structural testing)
Black-box testing
Unit testing
Integration testing
System testing
Alpha testing
Beta testing
Acceptance testing

Question 2

Bottom-up testing

Answer 2

The system is developed from the bottom up and the lowest-level modules are tested first.

Question 3

Top down testing (aka interface testing or stub testing)

Answer 3

A skeleton of the complete system is tested. Functionality is added module by module from the top-down and tested as it is added.

Question 4

Mixed level testing

Answer 4

A combination of top-down and bottom-up testing is used as different approaches are taken

Question 5

Dry running (aka hand tracing, walkthroughs or desk checking)

Answer 5

Code is read through and checked by hand. A trace table is completed to check the values of the variables at every stage of execution

Question 6

White-box testing (aka structural testing)

Answer 6

Tests are derived from a knowledge of the program code. Tests are devised to execute every possible path through the program.

Question 7

Black-box testing (aka functional testing)

Answer 7

Tests are derived from the program specification. Test cases are devised that test all of a programs inputs. The outputs are then examined for correctness.

Question 8

Unit testing

Answer 8

Each function, method or procedure is tested individually for correctness.

Question 9

Integration testing

Answer 9

Tests that separately developed modules work together as planned