testing
DESCRIPTION
Testing. Worshop in Software Engineering Project Department of Computer Science Ben-Gurion university. Classification. Tests are boolean: Pass or fail! White-box testing: Unit testing Follow computation paths (code coverage) Test scenarios derived from use cases (data coverage) - PowerPoint PPT PresentationTRANSCRIPT
![Page 1: Testing](https://reader036.vdocuments.us/reader036/viewer/2022082422/56813d7d550346895da75c35/html5/thumbnails/1.jpg)
Testing
Worshop in Software Engineering ProjectDepartment of Computer Science
Ben-Gurion university
1Worshop in SE ProjectSpring 2013
![Page 2: Testing](https://reader036.vdocuments.us/reader036/viewer/2022082422/56813d7d550346895da75c35/html5/thumbnails/2.jpg)
Software Engineering, 2005 Design Patterns – Creational patterns 2
Classification Tests are boolean: Pass or fail!1. White-box testing:
1. Unit testing1. Follow computation paths (code coverage)2. Test scenarios derived from use cases (data coverage)3. Test non-functional requirements (data coverage)
2. Integration testing1. Test integration scenarios derived from functional and
non-functional requirements
2. Black-box testing1. Test scenarios derived from use cases (data coverage)2. Test non-functional requirements (data coverage)
3.Regression testing
![Page 3: Testing](https://reader036.vdocuments.us/reader036/viewer/2022082422/56813d7d550346895da75c35/html5/thumbnails/3.jpg)
Software Engineering, 2005 Design Patterns – Creational patterns 3
Unit testing – Follow computation paths
1. White-box testing:1. Unit testing
1. Follow computation paths (code coverage)2. Test scenarios derived from use cases (data coverage)3. Test non-functional requirements (data coverage)
Code coverage: Statement, line coverage Branch coverage
Code complexity – e.g., cyclomatic complexity Related to data coverage
![Page 4: Testing](https://reader036.vdocuments.us/reader036/viewer/2022082422/56813d7d550346895da75c35/html5/thumbnails/4.jpg)
Software Engineering, 2005 Design Patterns – Creational patterns 4
Unit testing – Use-case scenarios
1. White-box testing:1. Unit testing
1. Follow computation paths (code coverage)
2. Test scenarios derived from use cases (data coverage)
3. Test non-functional requirements (data coverage)
Use-case coverage: Build scenarios for use-case alternatives
Use sequence diagrams for scenario specification What is the relevance of use-case diagrams?
Data coverage How to test “big, complex” data, like a big graph?
![Page 5: Testing](https://reader036.vdocuments.us/reader036/viewer/2022082422/56813d7d550346895da75c35/html5/thumbnails/5.jpg)
Software Engineering, 2005 Design Patterns – Creational patterns 5
Unit testing – Non-functional requirements
1. White-box testing:1. Unit testing
1. Follow computation paths (code coverage)2. Test scenarios derived from use cases (data coverage)3. Test non-functional requirements (data coverage)
How to create Data? How to test success/failure Beware of side-effects
![Page 6: Testing](https://reader036.vdocuments.us/reader036/viewer/2022082422/56813d7d550346895da75c35/html5/thumbnails/6.jpg)
Software Engineering, 2005 Design Patterns – Creational patterns 6
Integration testing
1. White-box testing:1. Unit testing
2. Integration testing1. Test integration scenarios derived from functional and
non-functional requirements1. Use sequence diagrams to emphasize inter-module
interaction
![Page 7: Testing](https://reader036.vdocuments.us/reader036/viewer/2022082422/56813d7d550346895da75c35/html5/thumbnails/7.jpg)
Software Engineering, 2005 Design Patterns – Creational patterns 7
Black-box: Test Use case scenarios
How different from white-box testing?
1. Black-box testing Positive tests Negative tests Use customer advice for testing data
1. Test scenarios derived from use cases (data coverage)
2. Test non-functional requirements (data coverage)