F452 ch6 testing

Black box testing (functional testing): 

• Different sets of input data are tested to see if they produce the expected outcome.
• Sets of data are picked to represent certain scenarios.
• Example: Checking age inputs between 0 & 100; valid data include 8, 76 & 50; invalid data include 600, 109 or -5; borderline data 

White box testing (structural testing):

• The algorithm i the code is tested ti check that all parts of the code to check that all parts of the code work as intended.
• Every possible route or path of execution through the program is identified and tested.

• *key difference: white box testing requires access to the code and to be able to understand it.

Alpha testing:

• Partially complete with lots of bugs.
• Carried out within the company.
• Any bugs are identified and quickly fixed.

Beta testing:

• Nearly complete and is released to potential users outside the company.

Acceptance testing:

• Program is now complete and it is demonstrated to the end user. The purpose is to show that it works correctly and all desired features are implemented.
• The program is tested against the requirements which were agreed between the user & the programmers. 

Bottom up testing:

• Each individual module is tested as soon as it's written using pre-prepared testing data.
• Test data:
• Normal data.
• Extreme values.
• Incorrect data.

Top down testing:

• The skeleton of the complete system is tested, with individual modules being replaced by stubs which display a message is a procedure is executed.

Integration testing:

• When all modules have been tested individually they need to be tested together.