effective testing

7/29/2019 effective testing

1/20


2/20

Types of Test case TemplatesMehernath


3/20

Test Case

What is meant by Test Case.

Test case is a description of what to be tested, what data to be

given and what actions to be done to check the actual result against

the expected result.

Test Cases are valuable because they are repeatable, reproducible

under the same environments

characteristics of good test case :

TC should start withwhat you are testing

TC should be independent.

TC should not containIfstatements.

TC should be uniform.

E.g.. ,Links


4/20

Test Case Templates

The following are the different Test case Templates used

in Fidelity Projects.

JBU Format (Dot format)

Excel Format (General format)

Test Director Format

OTR Format (Online Test Repository format)

Word Format


5/20

JBU Format

This Format consists of the following columns.

Test Conditions : Test case description or condition to verify.

Test case ID :Assign a Identification number consistent throughout

Results (expected result) : What is the expected behavior

No. of Cycles /Pass or Fail : End result Pass or Fail

Normal/Abnormal/Boundary conditions.


6/20

JBU Format (Dot Format-1)


7/20



8/20



9/20

Excel Format


User Type : Single user/Client, Multi user/Multi Client .

User ID : SSN # OR PIN #

Scenario :

Action / Steps :Action or Steps to perform test case.

Expected Results : Expected behavior of the test case

Tester, Pass/Fail, Notes.


10/20

Excel Format (General)


11/20



This format is extracted from Test Director S/W, we can upload directly to

The Test Director tool.

Step number : Test case number like Step 1, Step 2.

Description : Test case description or Action Steps

Expected Results : Expected behavior of the test case


12/20



13/20

OTR Format (1)


This template allow the OTR to present the test cases over the web

and run automatic reports. It consists ofnumber of columns.The

Standard columns are :

TestcaseID :Do not populate this field. The database will do thenumbering once the cases are loaded.

TCIdentifier :[Required Field] This is where you number/identify

your cases any way you want to. People all seem to label their

cases differently, and this is where you do it.

Functional Category :[Required Field] Once your project comes

up with a list of the functional categories youll be using, add the

appropriate one to each of your testcases here.


14/20

OTR Format (2)

TCStatus

[Required Field] The OTR has the following available statuses:

Master Case, New, Pass, Fail, Invalid, and Deferred.

Scenario[Required Field] Commonly referred to as Testcase Description,

this is where you describe what you are doing in your testcase in a

general way. Specific instructions regarding the case can be put in

the Procedures (or steps) column

Expected Results

This is where you describe what should happen from performing the

scenario.


15/20

OTR Format (3)

Procedures

Explicit steps that one needs to follow for the execution/validation

of the test case. This ensures that the scenario is executed in a

specific way if it is important to the test case.Plan : Enter the plan number relevant for this test case if

applicable.

SSN :Enter the SSN number relevant for this test case if applicable.

Clone :Enter the Clone relevant for this test case if applicable.

Test Environment :Enter the Test Environment relevant for this

test case if applicable.


16/20

OTR Format (4)

CustomName1, CustomName2, CustomName3

Leave these fields blank. This is where the testers record their

feedback to you. You should rename one or more of these fields to

make it more apparent like Actual Results, Comments, andNotes, but you can name these fields anything youd like.

Execution Date & Cycle :[One or the other is Required] As a

group, every one whos creating testcases for your project should.

Tester :[Required Field] Enter the testers name, badge, or

whatever in here.


17/20

OTR Format (Online Test Repository)


18/20

OTR Format (Online Test Repository)


19/20

Word Format


20/20

Documents

effective testing