1 / 7

Testing

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)

delu
Download Presentation

Testing

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Testing Worshop in Software Engineering Project Department of Computer Science Ben-Gurion university Worshop in SE Project

  2. 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) • Test non-functional requirements (data coverage) • Integration testing • Test integration scenarios derived from functional and non-functional requirements • Black-box testing • Test scenarios derived from use cases (data coverage) • Test non-functional requirements (data coverage) • Regression testing

  3. Unit testing – Follow computation paths • White-box testing: • Unit testing • Follow computation paths (code coverage) • Test scenarios derived from use cases (data coverage) • Test non-functional requirements (data coverage) Code coverage: • Statement, line coverage • Branch coverage • Code complexity – e.g., cyclomatic complexity • Related to data coverage

  4. Unit testing – Use-case scenarios • White-box testing: • Unit testing • Follow computation paths (code coverage) • Test scenarios derived from use cases (data coverage) • 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?

  5. Unit testing – Non-functional requirements • White-box testing: • Unit testing • Follow computation paths (code coverage) • Test scenarios derived from use cases (data coverage) • Test non-functional requirements (data coverage) • How to create Data? • How to test success/failure • Beware of side-effects

  6. Integration testing • White-box testing: • Unit testing • Integration testing • Test integration scenarios derived from functional and non-functional requirements • Use sequence diagrams to emphasize inter-module interaction

  7. Black-box: Test Use case scenarios How different from white-box testing? • Black-box testing • Positive tests • Negative tests • Use customer advice for testing data • Test scenarios derived from use cases (data coverage) • Test non-functional requirements (data coverage)

More Related