Designing Test Cases

Input required for designing test cases:

  1. Software Requirement Specification
  2. Integration Test Plan
  3. Detailed Design & Analysis document

Test Items:

List of Test Items to be tested

· Brief description on each item

Environmental needs:

· Hardware: - Specify characteristics and configuration of hardware required to execute the test case

· Software: - Specify the system and application software required to execute the test case

Test Case Design Method:

· Black Box Testing

Test Case Description:

· Test Case ID

· Name of the person prepared the test cases

· Name of the person for executing the test

· Date and Version of the execution

· Purpose

· Test Case Description

· Input value

· Expected result

· Actual Result

Roles and Responsibility:

· Test Cases need to design prior to application development and generally prepared by test designer

Test case Output:

· Test Case Document

Test Case Report

Designing test cases:

· Objectives:

  1. To check the flow of messages between modules/components.
  2. To verify the object life time as per the sequence diagram.
  3. Error Handling-testing should be done

Guidelines:

To check the flow of messages between modules/components.

  1. Understand the High and Low level design
  2. Study the sequence and collaboration diagram that shows the integration of different components (Use Cases integration to build system)
  3. Identify the components to be integrated from the sequence diagrams
  4. Identify the main (start) method name, which calls method in other module.
  5. Identify the parameters passed
  6. Identify the data structure of the parameters
  7. Identify the domain values of each parameter passed
  8. Divide the input domain into equivalence classes, such that all valid, invalid values will fall under classes
  9. Identify boundary values of each equivalence class as input data
  10. Identify some random values from the class as input data
  11. Identify the order in which the parameters passed between the components
  12. Write stubs or driver programs for the test case

To verify the object life time as per the sequence diagram

Identify the relative object life time from sequence diagram

Write program such that it prints messages when

1. An object is created

2. An object is destroyed

3. Check the output against the sequence diagram

Error Handling-testing should be done

  1. Error noted must correspond to error encountered
  2. Error condition must not cause system intervention prior to error handling
  3. Exception-condition processing must be correct

RELATED POST

TEST CASE DESIGN

TEST CASE DESIGN TWO

DESIGN OF TEST CASES PART THREE

TEST CASE DESIGN PART THREE

TEST CASE DESIGN PART FOUR

TEST CASE DESIGN PART FIVE

TEST CASE DESIGN PART SIX

TEST CASE DESIGN PART SEVEN

TEST CASE DESIGN PART EIGHT

TEST CASE DESIGN PART NINE

REVIEWS AND APPROVAL OF TEST CASES

WRITING SOFTWARE TEST CASES PART ONE

WRITING SOFTWARE TEST CASES PART TWO

WRITING SOFTWARE TEST CASES PART THREE

WRITING SOFTWARE TEST CASES PART FOUR

No comments:

Post a Comment