FIT2001 Lecture Notes - Lecture 10: Black-Box Testing, White-Box Testing, Software Testing
L10 - Testing
The aim is to get the system to fail rather than confirm that is it correct. All systems must be
tested for functional and non-functional aspects.
Testing Process
●Plan - what to test
●Design - how you are going to test it
●Schedule - when you are going to test it
●Execute - what was the result of the testing
Testing in Different Methodologies
Iterative
●When defects are found and fixed, these must be retested
●Test + Fix + Re-test = Accepted
Agile
●Testing integrated throughout the lifecycles
●Tests the software continuously throughout its development
Waterfall
●Generally all testing and quality controls points come late in the project.
Test Methods
Black Box
●Internals not known
●Testing the functional/ non-functional requirements without reference to the internal
structure of the system
●Typically executed in functional test phases
●Can be independently tested
White Box
●Uses an internal perspective of the system to design test cases based on the internal
structure
●Requires programming skills to identify all paths through the software
Document Summary
The aim is to get the system to fail rather than confirm that is it correct. All systems must be tested for functional and non-functional aspects. Design - how you are going to test it. Schedule - when you are going to test it. Execute - what was the result of the testing. )hen defects are found and fixed, these must be retested. Test + fix + re-test = accepted. Tests the software continuously throughout its development. Generally all testing and quality controls points come late in the project. Testing the functional/ non-functional requirements without reference to the internal structure of the system. Uses an internal perspective of the system to design test cases based on the internal structure. Requires programming skills to identify all paths through the software. Maximum coverage of a scenario is possible. The combination of black and white box testing. Look into the box being testing long enough to understand how it has been implemented.