In every company, Test engineer will write the test cases in a test case template, which is nothing but a Standard Test case template which can vary from project to project or from company to company.

Test case template can be prepared in a Test case management tool, MS Excel, MS Word.

Header:

1. Test case name/ ID-

   Here a Unique testcase name for individual test cases are given, if test case management tool is used test case ID will be automatically generated.

2. Project name-

   Name of the project should be mentioned.

3. Release name -

   Based on the name/ number of release it should be mentioned.

4. Requirement number -

   Requirement number is nothing but a ticket number for which the test cases are written for.

5. Module Name-

   These are the major Sub- modules of the product/ Software.

6. Pre Conditions-

   These are set of settings or actions that need to be performed before the execution of the Test cases.

   As part of pre- condition the below settings need to be checked-

   1. Check whether the software is installed or not.

   2. Check for Internet connection.

   3. Check for Browser settings.

   4. Check for "Role and Permissions".

   5. Check for Username and Password.

   Example- Gmail.com(Application)-

   Testcase: Login as User A, compose mail to User B, Click on Sent Items and check if the mail is displayed in Sent Items menu.
   Pre- Condition:

   Check for Internet connection.

7. Test Data or Test Harness-

   It is the data created using the same application before executing the Test cases.

   Example- Gmail.com(Application)-

   Testcase: Login as User A, compose mail to User B, Click on Sent Items and check if the mail is displayed in Sent Items menu.
   Test Data

   Create User A and User B account.

8. Severity-

   This describes the impact of feature on the application. Test engineer will test execute the testcases based on the severity.

   There are 3 types of severity

   1. Critical

   2. Major

   3. Minor

9. Test case type-

   Test case type is classified based on the type of testing that is to be done

   Example-

   Smoke testing, System testing, Adhoc testing, Compatibility testing....

10. Test case execution hours-

    It is the total time taken to write test cases and execute the written test cases in the application.

BODY:

Test case body will have

1. Serial no-

   Specific serial number for each Test scenario.

2. Test scenario-

   Summary/ action of the test that is being done.

3. Steps by step procedure-

   Unique step number for the Steps to executed.

4. Action/ Description-

   It consists of the navigation steps.

5. Input-

   The data that need to be entered into the application while testing the software.

6. Expected Result-

   Detail about how the application should behave when a test case is is executed.

7. Status-

   "Pass/ Fail" of the testcase based on expected result and actual result comparison

8. Comments(Optional)-

   If the testcase is failed, the reason can be mentioned in the comment section.

FOOTER:

It has the details such as

1. Author name-

   Person one who writes the Test cases.

2. Reviewed by-

   Person who reviews the Test cases.

3. Approved by-

   Person one who approves the Test cases.

4. Approval date-

   The date of Test case approval.