12.3 Methods of Testing and Test Data CIE AS

Testing that is only concerned with testing that input and output work with the test data.​ (a)  

• Black box testing
• White Box testing
• Alpha testing
• Beta testing
• Dry Run testing
• Stub testing
• Systems Testing

Testing that uses test data to test every possibility of input and output based on examining the code of the program.​ (a)  

• White Box testing
• Alpha testing
• Beta testing
• Dry Run testing
• Stub testing
• Systems Testing

Testing that is done by a testing team within the company making the software. ​ (a)   ​

• Beta testing
• Dry Run testing
• Stub testing
• Systems Testing
• Black Box
• Alpha Testing

Testing done when all the parts of the solution are complete. (a)   ​

• White Box
• Alpha testing
• Beta testing
• Dry Run testing
• Stub testing
• Systems Testing
• Black Box

Testing that is done by selected users outside of the company making the software. (a)   ​

• Alpha testing
• Beta testing
• Dry Run testing
• Stub testing
• Systems Testing
• Black Box

Testing that is done on just one small part of the program. ​ (a)  

• Alpha testing
• Beta testing
• Dry Run testing
• Stub testing
• Systems Testing
• Black Box
• Acceptance testing

Testing when all parts of the solution are complete. Customer can see the tests and their results and agrees that everything is working OK.​ (a)  

• Alpha testing
• Beta testing
• Dry Run testing
• Stub testing
• Systems Testing
• Black Box
• Acceptance Testing

Testing done when only some parts of the solution are complete.​​ ​ (a)  

• Alpha testing
• Beta testing
• Stub testing
• Systems Testing
• Black Box

Testing when all the parts of the solution are complete. Checks that all parts work together.​ (a)  

• Alpha testing
• Beta testing
• Stub testing
• Systems Testing
• Black Box
• Integration Testing

Testing that uses trace tables and suitable test data​ (a)  

• Alpha testing
• Beta testing
• Stub testing
• Systems Testing
• Black Box
• Dry Run Testing