QA TestCases Template

7/31/2019 QA TestCases Template

1/29

\\vboxsrv\conversion_tmp\scratch20804\102977962.xls.ms_office

1 Purpose/Overview Brief summary description.

2 List Items to be tested Refer to the functional requirements that specify the features and functions to be tested.

3 Items not to be Tested List the features and functions that will not be covered in this test plan. Identify briefly th

Context Implication

1 Successful transaction or update The expected results have happened, update to the database has been verified as compl

has been confirmed through related client functions, where applicable.

2 Valid or invalid field formats Valid formats are accepted and invalid format return the appropriate error message in th

validation is completed).

3 Defaults Any and all possible default values are present and correct as retrieved from database re

4 Required fields Creative Commercials Insurance

Result Condition Descirption

P PASS All expected results were met.

F FAIL

At least one of the expected results were not met.

- When a failure occurs, file a bug in the bug database.

N NOT RUN

e case cou no e comp e e ue o some ne wor , ar ware, so ware or o er pro

- The case could not be completed due to some network, hardware, software or other pr

- A Not Run situation may also require having to file a bug. That should be evaluated o

the case number in the bug description.

- If a large block of tests fails or cannot be run for the same reason, every case should b

1 Acceptance Testing

Conditions that must be met before testing can begin.

Listed test cases will be used for acceptance criteria that can be reused by a smoke test.

2 Integration/System Testing Specify the tests will be carried out to fully exercise the program as a whole to ensure th

s stem function ro erl .3 Regression Testing At each stage of new development or maintenance, a subset of the regression test librar

feature or function that has changed from the previous version.

Unit, integration, and system tests are all viable places for regression testing.

For small maintenance fixes, identify this subset. In the final phase of a complete develo

cycle is run.

Emphasize regression tests for functions that are new or that have changed, for compon

- -

The Test Cases portion of this document outlines the specific cases to be tested. The Test Cases Procedures portion of this docu

to perform each test case.

Testing Synopsis

Pass Criteria - The following guidelines are used to ensure good bug tracking and to provide a framework for incid

Testing Levels

Setup Data for Testing

Provide any additiona details, link to DocuShare collection (input files, sql scripts, data generation scripts)

Verification

Verification and Validation have specific implications within the summary of a test case:

Introduction Copyright 2006 eMeter Corporation.


2/29


4 Negative Testing Testing aimed at showing software does not work (Showing error when no

Introduction Copyright 2006 eMeter Corporation.


3/29


Document HistoryVersion Author Date

1.0 Rafi Uddin,Shaik 2/28/2012

Review LogVersion Reviewed By Date

1.0 XXXX 3/3/2012

2.0 XXXX 3/12/2012

Rev History Copyright 2006 eMeter Corporation. Page 3 of 29


4/29


1

2

3

4

5

1

2

3

45

Pass

- P -

Fail

- F -

Not Executed

- N -

0 0 11

write what are the items which are going NOT to be tested in this release

Write the purpose of testing this application

Test Overview

Items not to be Tested

Items to be tested

write what are the items which are going to be tested in this release

Total

Nuber of TCComments

Write a detailed purpose and overview of the application under test

Purpose/Overview

Test Cases Execution Results

TestSynopsis Copyright 2006 eMeter Corporation.


5/29


Type Comments

Input Files

SQL ScriptsData Generation Scripts (xml files) write the DB url link for test data

Summaryadd additional steps if you think if

you need them

Steps/Comments

additional instructions if you think you need to include

DocuShare Collection

Additional Details/Instructions

Link

SetupTestData Copyright 2006 eMeter Corporation.


6/29


Test Case ID Test Case Description

Funct

Sp

R

Num

Online payment processing of vehicle insurances

1 Check accont status for existing customers1.1 Verif that account number can not be left em t when checkin acct.status

1.21.3

1.4

1.51.6

1.7

1.8

1.9

1.101.11

2 Register form

Test Cases T

TestCases Copyright 2006 eMeter Corporation.


7/29




8/29




9/29




10/29


Regression

Negative

Level



11/29




12/29


YYYY



13/29




14/29


Test Case

Id

Test Case Description Preconditions


1.1 Verify that account number can not be left empty when checking ac 1. Customer should have internetconnection

2. Customer information is already

entered into the database server

3.Customer has the capability to pay

the bills online

Test Cases

TestProcedures Copyright 2006 eMeter Corporation


15/29


Test Case

Id


Test Cases

TestProcedures Copyright 2006 eMeter Corporat


16/29


Test Case

Id


Test Cases



17/29


Test Case

Id


Test Cases



18/29


Test Case

Id


Test Cases



19/29


Test Case

Id


Test Cases



20/29


Test Case

Id


Test Cases



21/29


Test Case

Id


Test Cases



22/29


Test Case

Id

Test Case Description


1.1 Verify that account number can not be left empty when checking ac

Test Cases Expected Result with Verification

StepsVerification Steps

1. Verify that the user can reach the

web page

http://www.chkacct.ccinsurance.com

2. Verify that all 4 radio buttons activ

and inactive and closed and

suspended are not selected.

3. Verify that check acct status button

is visible

TestProcedures Copyright 2006 eMeter Corporatio


23/29


Test Case

Id


Test Cases Expected Result with Verificatio

Steps

Verification Steps



24/29


Test Case

Id



Steps

Verification Steps



25/29


Test Case

Id



Steps

Verification Steps



26/29


Test Case

Id



Steps

Verification Steps



27/29


Test Case

Id



Steps

Verification Steps



28/29


Test Case

Id



Steps

Verification Steps



29/29


Test Case

Id



Steps

Verification Steps

Documents

QA TestCases Template