Top Banner
1 Test Cases CSSE 376, Software Quality Assurance Rose-Hulman Institute of Technology March 13, 2007
12

1 Test Cases CSSE 376, Software Quality Assurance Rose-Hulman Institute of Technology March 13, 2007.

Dec 18, 2015

Download

Documents

Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: 1 Test Cases CSSE 376, Software Quality Assurance Rose-Hulman Institute of Technology March 13, 2007.

1

Test Cases

CSSE 376, Software Quality Assurance

Rose-Hulman Institute of Technology

March 13, 2007

Page 2: 1 Test Cases CSSE 376, Software Quality Assurance Rose-Hulman Institute of Technology March 13, 2007.

2

Outline

Test design process Developing test cases

Page 3: 1 Test Cases CSSE 376, Software Quality Assurance Rose-Hulman Institute of Technology March 13, 2007.

3

Test Design Process

1. Design tests elaborate test plan based on requirements

2. Develop test cases based on knowledge of system behavior

3. Verify test cases verify procedures debug test cases

Page 4: 1 Test Cases CSSE 376, Software Quality Assurance Rose-Hulman Institute of Technology March 13, 2007.

4

1. Design Tests

Define test objectives what, not how based on requirements

Define input specifications files, databases not keyboard or mouse input

Page 5: 1 Test Cases CSSE 376, Software Quality Assurance Rose-Hulman Institute of Technology March 13, 2007.

5

1. Design Tests (continued)

Define test configuration for each test operating system version network configuration

Review test designs for coverage and accuracy all requirements covered? all inputs identified? all configurations identified?

Page 6: 1 Test Cases CSSE 376, Software Quality Assurance Rose-Hulman Institute of Technology March 13, 2007.

6

2. Develop Test Cases

Develop detailed test procedures use black-box techniques like equivalence

partitioning and boundary value analysis specify actions and expected results

Define test setup and cleanup, noting inter-case dependencies restart computer at start of testing reset system to known configuration at

start of each test

Page 7: 1 Test Cases CSSE 376, Software Quality Assurance Rose-Hulman Institute of Technology March 13, 2007.

7

Equivalence Partitioning

Divide the input into independent categories (partitions) use the requirements specification consider type of each input

Select a value from each category Why is this a good idea?

Page 8: 1 Test Cases CSSE 376, Software Quality Assurance Rose-Hulman Institute of Technology March 13, 2007.

8

Cartoon of the Day (1/2)

Page 9: 1 Test Cases CSSE 376, Software Quality Assurance Rose-Hulman Institute of Technology March 13, 2007.

9

Cartoon of the Day (2/2)

Page 10: 1 Test Cases CSSE 376, Software Quality Assurance Rose-Hulman Institute of Technology March 13, 2007.

10

Boundary Value Analysis

For each input partition identified earlier: pick values on the boundary pick values on each side of the

boundary Why is this a good idea?

Page 11: 1 Test Cases CSSE 376, Software Quality Assurance Rose-Hulman Institute of Technology March 13, 2007.

11

3. Verify Test Cases

Review test procedures are the inputs unambiguous? are the outputs unambiguous?

Debug test cases (during first run) run the test as specified note flaws in test case as well as

flaws in software

Page 12: 1 Test Cases CSSE 376, Software Quality Assurance Rose-Hulman Institute of Technology March 13, 2007.

12

Summary: Test Design Process

1. Design tests elaborate test plan based on requirements

2. Develop test cases based on knowledge of system behavior

3. Verify test cases verify procedures debug test cases