Revant Pande and

Ali Marjaie

WHAT IS A TEST CASE?

IEEE Standard 610 (1990) defines test case as follows:

A set of test inputs, execution conditions, and expected results developed for a particular objective, such as to exercise a particular program path or to verify compliance with a specific requirement.

DESIGN

To conceive or fashion in the mind; invent: design a good reason to attend the STAR testing conference. To formulate a plan for; devise: design a marketing strategy for the new product.

To plan out in systematic, usually documented form: design a building; design a test case.

To create or contrive for a particular purpose or effect: a game designed to appeal to all ages.

To create or execute in an artistic or highly skilled manner.

COMPONENTS OF TEST CASESWell designed test cases are composed of

three parts:

Inputs

Outputs

Order of execution

TEST CASE SPECIFICATION

Test Case Specification IdentifierTest ItemsInput SpecificationsOutput SpecificationsEnvironmental NeedsSpecial Procedural RequirementsIntercase Dependencies

TEST CASE DESIGN It is the responsibility of the testers to design

tests that

Reveal defects

Can be used to evaluate software performance, usability, and reliability.

BY AN EFFECTIVE TEST CASE WE MEAN ONE THAT HAS A GOOD POSSIBILITY OF

REVEALING A DEFECT

ADVANTAGES OF EFFECTIVE TEST CASES

If test cases are effective there is :-A greater probability of detecting defects.A more efficient use of organizational

resources. A higher probability for test reuse. Closer adherence to testing and project

schedules and budgets.The possibility for delivery of a higher-

quality software product.

BLACK BOX & WHITE BOX TESTING

The Black Box ApproachA tester considers the software-under test to

be an opaque box.

The White Box Approach Focuses on the inner structure of the

software to be tested.

BLACK BOX & WHITE BOX TESTING

HOW TO WRITE GOOD TEST CASES?

Write a test plan and test casesUse templates with cautionAssume that you will not be performing

the testWrite the test objectives as hypothesesUse a mix of valid and invalid testsDocumenting Test Results

INFORMATION REQUIRED WHILE DOCUMENTING TEST RESULTS

Tester's name and departmentDate and time the test was performedName & Version of the operating systemFull description of the resultsResolution of any problem

ADVANTAGES AND DISADVANTAGES OF DOCUMENTATION

Advantages1. Gives an approach, Description, Pre-conditions to achieve the expect result.2. Test Cases are useful while writing Traceability Matrix.3. It shows or avails the traceability of the entire requirements.

Disadvantages1. Without or miswritten Test Cases or human errors in the Test Cases cause the project failure.

HOW TO PRIORITIZE TEST CASES

There are two different methods to determine priorities:

  Using an informal method - Gathering

the information and estimate the priority.

Using a formal method - FMEA.

METHOD 1 - INFORMAL         The following may be the example for the

priority scale 1-4 P1 - These are the test cases that are run first to determine if a given

build is even testable.        P2 - These are the test cases that are executed the most often to ensure

functionality is stable, intended behaviors and capabilities are working.

P3 - These are the test cases where the testing of a given functional area or feature is to get more detailed and the majority of aspects for the function are examined including boundary, error and configuration tests.

P4 - These are the test cases that are frequently tested. They are may or may not be tested. It does’nt mean those are not important but just that they are not run often in the life of the project.

Method 2 – FORMAL

FMEA is a technique for systematically identifying potential failures in a system or process. It can also be used for understanding and prioritizing possible failure modes. But use FMEA only if it is appropriate.

Q?THANK YOU