FIT4004 Lecture Notes - Lecture 9: Integration Testing, Big Bang, Patient Protection And Affordable Care Act
15 Jun 2018
School
Department
Course
Professor
Week 9 - Integration testing
Software integration: the process by which the individual units which make up a software
system are integrated together to make a complete system
Integration approaches:
Big bang integration
Developers write every single module in the system independently, unit test them, &
only once they are all complete stick them all together, and test the completed system
- Very bad. So bad. Number of faults that can happen from so many untested
(integration-wise) components being combined together. Bad.
- Example of bad = Obamacare that went through “couple of days of testing” then
BAM. Bad. everything went poof
Top-down testing
1. Start with a module that has no dependencies (look at example below)
2. Write and execute tests for module with dummy data for modules it interacts
with
3. Replace dummy data with actual modules and test again
4. Rinse, wash and repeat
Example
1. Start with MainClass
2. Write tests with dummy data instead of method calls for SummaryGen and
ReportMaker
3. Replace dummy data with real SummaryGen and ReportMaker
Document Summary
Software integration: the process by which the individual units which make up a software system are integrated together to make a complete system. Developers write every single module in the system independently, unit test them, & only once they are all complete stick them all together, and test the completed system. Number of faults that can happen from so many untested. Example of bad = obamacare that went through (cid:522)couple of days of testing(cid:523) then. Example: start with mainclass, write tests with dummy data instead of method calls for summarygen and. Reportmaker: replace dummy data with real summarygen and reportmaker. Using above example: write tests to test the four leaf units filefetcher, nettransfer, xmlgenerator and pdftranslator first then integrate them with datafetcher & reportmaker & create + execute tests. Units near the bottom are designated operational units, which are tested bottom-up. Units near the top are designated logic units, and are tested top down, until you meet in the middle.
