1 / 6

Setup Phase-2 ( System Testing)

Setup Phase-2 ( System Testing). Course Software Testing & Verification 2013/14 Wishnu Prasetya. What to test ?. The minimum is to test the functionalities specified by : your use cases ( dont have) requirement document.

celine
Télécharger la présentation

Setup Phase-2 ( System 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. Setup Phase-2(System Testing) Course Software Testing & Verification 2013/14 WishnuPrasetya

  2. What to test ? • The minimum is to test the functionalities specified by : • your use cases (dont have) • requirement document

  3. Test Cases, for a GUI-based Program(we want programmatic test cases) System Under Test Programmatic test-case : write textField1 “abc@com” ; click button1 ; assertgetState().z.contains “abc@com” GUI • Manually constructed • Can be programmatically executed  so that you can re-execute them as often as you like!

  4. Use Record & Replay to Construct Such a Test Case (we need such infrastructure  implement it) System Under Test Programmatic test-case : replay(log1) assertgetState().z.contains “abc@com” GUI log-1

  5. Adequacy(complement block coverage with model coverage) • Want a stronger coverage (than block coverage) • we will choose model-based coverage, in particular pair-based or path-based coverage over your model. • Multiple FSAs to model programs that are both event-driven and have autonomous behavior. tick move(d) tick alive destroyed gameover tick move(d)

  6. Adequacy, few notes • Use split and merge to adjust your abstraction level • Notice that : • split corresponds to introducing partitions • e.g. pair-based and path-based coverage over your model correspond to pair-wise and full-combination coverage in partition-based testing

More Related