Manual Testing class - 10

                                   Test Case

A Test Case Is A Set Of Steps Or Sequence Of Steps With The User Actions Performed And The Response From
 The System Documented To Validate A System.

Test Cases Are Derived From The Requirements And Use Cases.

Test Engineers Are Responsible In Deriving The Test Cases After The Test Scenario Identification.

Test Cases Are Often Prepared Or Documented In Word Or An Excel Document.

Qualities Of Good Test Case:

1. Every Test Case Should Be Simple , Clear And    Understandable.

2. Every Test Case Should Be Unique ( No Redundancy)

3. Every Test Case Should Follow A Naming Convention.

4. Every Test Case Should Have A Proper Start And End Positions.

5. Every Test Case Should Be Consistent And Should Be Documented In The Standard Template

6. Every Test Case Should Be Traceable To The Requirement.

7. There Should Not Be Any Missing Links In A Test Case.

Fields in Test Case Template:

1. Project

2. Module

3. Created By

4. Created On

5. Reviewed By

6. Reviewed On

7. Documents Referred

8. Test Case Id/Name:

It Is The Identifier For The Test Case, It Should Be Unique and It Should Follow A Naming Convention.

Ex: Tc01_Project_Module_Functionality

9. Test Case Description:

It Describes The Objective Or Purpose Of The Test Case

Test Case Id And Test Case Description Are Unique For The Entire Test Case.

10. Step Name:

It Is A Step Identifier, Which Is Unique For Every Operation Performed.

It Is A Collection Of At least One Action Performed And The Subsequent Response From The System.

Ex: Step1

    Step2

    Step3...

11. Step Description:

It Is The Action Performed By The User On The System

12. Test Data:

It Is The Input Required To Perform The Operation On The Current Step.

In Test Case, We Identify The Data Required To be Generated To Execute The Test Case.

13. Expected Result:

It Is The Expected Behavior Of The System Based On The Operation Performed As Per The Requirements.

14. Priority:

It Defines The Importance Of The Test Case, This Is Derived Based On The Complexity Of The Functionality
, Which Is Often Categorized Into Three,

High, Medium And Low

Note: The Test Execution Process Is Carried Out Based On It's Priority, All High Priority TC Should Be Executed
First Then Medium And Then Low.

15. Review Comments:

The Deviations Or Changes That Were Identified During The Review Phase By The Reviewer.