Sample Test Case Template In Excel Format Word
Sample Test Case Template Document Excel
Reference

Several standard fields of a sample Test Case template are listed below. Test case ID: Unique ID is required for each test case. Follow some convention to indicate the types of the test. For Example, ‘TCUI1’ indicating ‘user interface test case #1’. Download Manual Testing Test Case Template. Excel Word PDF. With this manual testing test case template, you can record testing steps and data, analyze expected results versus actual results, and determine whether or not you can consider a test to be a success. With space to record each individual step of the testing process, the test ID. Test Case Template 3 Test Case Template 2 Test Case Template 1 General Test Case Template 1 Test Case Template 1 of 3 Software case template a service of RBCS software testing training Test Case Name: Mnemonic identifier Test ID: Five-digit ID, XX.YYY: XX suite number, YYY test number. Test Suite(s): The name of the test suite(s) that use this.

Abhishek

30.03.2018

Franklyn Edwin

01.12.2017

Sample Test Case Template In Excel Format Word

Thanks for these templates, very simple and easy to document.

Tova Dyar

10.06.2017

I stumbled accross your blog post after a google search. Lucky me! This was just what my team and I needed to get a good discussion goint on this subject. We have been trying to come to a unanimous position for quite a while. We think your post will be very helpful to us in achieving that.

Mihaylo

12.06.2017

Thank you for drawing attention to our article. We are pleased that our article has helped you.

Sample Use Case

Sample Test Case Template Document Excel

Use Case ID:	Enter a unique numeric identifier for the Use Case. e.g. UC-1.2.1
Use Case Name:	Enter a short name for the Use Case using an active verb phrase. e.g. Withdraw Cash
Created By:			Last Updated By:
Date Created:			Last Revision Date:
Actors:		[An actor is a person or other entity external to the software system being specified who interacts with the system and performs use cases to accomplish tasks. Different actors often correspond to different user classes, or roles, identified from the customer community that will use the product. Name the actor that will be initiating this use case (primary) and any other actors who will participate in completing the use case (secondary).]
Description:		[Provide a brief description of the reason for and outcome of this use case.]
Trigger:		[Identify the event that initiates the use case. This could be an external business event or system event that causes the use case to begin, or it could be the first step in the normal flow.]
Preconditions:		[List any activities that must take place, or any conditions that must be true, before the use case can be started. Number each pre-condition. e.g. Customer has active deposit account with ATM privileges Customer has an activated ATM card.]
Postconditions:		[Describe the state of the system at the conclusion of the use case execution. Should include both minimal guarantees (what must happen even if the actor’s goal is not achieved) and the success guarantees (what happens when the actor’s goal is achieved. Number each post-condition. e.g. Customer receives cash Customer account balance is reduced by the amount of the withdrawal and transaction fees]
Normal Flow:		[Provide a detailed description of the user actions and system responses that will take place during execution of the use case under normal, expected conditions. This dialog sequence will ultimately lead to accomplishing the goal stated in the use case name and description. Customer inserts ATM card Customer enters PIN System prompts customer to enter language performance English or Spanish System validates if customer is in the bank network System prompts user to select transaction type Customer selects Withdrawal From Checking System prompts user to enter withdrawal amount … System ejects ATM card]
Alternative Flows: [Alternative Flow 1 – Not in Network]		[Document legitimate branches from the main flow to handle special conditions (also known as extensions). For each alternative flow reference the branching step number of the normal flow and the condition which must be true in order for this extension to be executed. e.g. Alternative flows in the Withdraw Cash transaction: 4a. In step 4 of the normal flow, if the customer is not in the bank network System will prompt customer to accept network fee Customer accepts Use Case resumes on step 5 Nero 9 full download. 4b. In step 4 of the normal flow, if the customer is not in the bank network System will prompt customer to