Sample Test Case Template with Examples [Download]


I get many requests to share a good test case template. I’m surprised many testers are still documenting test cases with Word docs or Excel files. They prefer excel spreadsheets because they can easily group test cases by test types and most importantly they easily get test metrics with Excel formulas. But I’m sure as volume of your tests goes on increasing, you will find it extremely difficult to manage.

Test case example

If you are not using any test case management tool, I strongly recommend using any open source tool to manage and execute your test cases.

Test case formats vary by organization. But using a standard test case format for writing test cases is one step closer to setting up testing process on your project. It also minimizes ad-hoc testing done without proper test case documentation. But even if you use standard templates you need to setup test cases writing, review and approval, test execution and most importantly test report preparation process, all using manual methods.

Also if you have process to review test cases by business team then you must format these test cases in a template agreed by both the parties.

Here is how to make this manual test case management process a bit easier with the help of simple testing templates.

Note: I’ve listed maximum fields related to test case. But it is advised to use only those fields which are used by your team. Also if you think any field is used by your team but missing from this list feel free to add it in your customized template.

Below are the standard fields of sample test case template:

Test case ID: Unique ID for each test case. Follow some convention to indicate types of test. E.g. ‘TC_UI_1′ indicating ‘user interface test case #1′.

Test priority (Low/Medium/High): This is useful while test execution. Test priority for business rules and functional test cases can be medium or higher whereas minor user interface cases can be low priority. Test priority should be set by reviewer.

Module Name – Mention name of main module or sub module.

Test Designed By: Name of tester

Test Designed Date: Date when wrote

Test Executed By: Name of tester who executed this test. To be filled after test execution.

Test Execution Date: Date when test executed.

Test Title/Name: Test case title. E.g. verify login page with valid username and password.

Test Summary/Description: Describe test objective in brief.

Pre-condition: Any prerequisite that must be fulfilled before execution of this test case. List all pre-conditions in order to successfully execute this test case.

Dependencies: Mention any dependencies on other test cases or test requirement.

Test Steps: List all test execution steps in detail. Write test steps in the order in which these should be executed. Make sure to provide as much details as you can. Tip – to efficiently manage test case with lesser number of fields use this field to describe test conditions, test data and user roles for running test.

Test Data: Use of test data as an input for this test case. You can provide different data sets with exact values to be used as an input.

Expected Result:  What should be the system output after test execution? Describe the expected result in detail including message/error that should be displayed on screen.

Post-condition: What should be the state of the system after executing this test case?

Actual result: Actual test result should be filled after test execution. Describe system behavior after test execution.

------------

Status (Pass/Fail): If actual result is not as per the expected result mark this test as failed. Otherwise update as passed.

Notes/Comments/Questions: To support above fields if there are some special conditions which can’t be described in any of the above fields or there are questions related to expected or actual results mention those here.

Add following fields if necessary:

Defect ID/Link: If test status is fail, then include the link to defect log or mention the defect number.

Test Type/Keywords: This field can be used to classify tests based on test types. E.g. functional, usability, business rules etc.

Requirements: Requirements for which this test case is being written. Preferably the exact section number of the requirement doc.

Attachments/References: This field is useful for complex test scenarios. To explain test steps or expected result using a visio diagram as a reference. Provide the link or location to the actual path of the diagram or document.

Automation? (Yes/No): Whether this test case is automated or not. Useful to track automation status when test cases are automated.

With the help of above fields I’ve prepared test case example templates for your reference:

Download test case template with example:

- DOC file and
- XLS file

xls template

Also refer few more articles on writing effective test cases here and here. Use these test writing guidelines and above template to write and manage test cases effectively on your project.

Personally, I prefer to use test case management tool. You can start with any open source tool. It will be a good addition for your efforts to setup testing process and also save lot of time instead of manually maintaining these documents.


The Best Software Testing Training You'll Ever Get!

software testing QA training

38 comments ↓

#1 Ketan Shingate on 12.12.12 at 5:03 pm

thanks for sharing. we will add some of these fields in our template

#2 Guest on 12.12.12 at 5:32 pm

Its a very detailed document mentioning each and every thing. I use to keep my test cases as simple as i can but really i love this format as well.Definitely i will include some of them to my test case document.

#3 Muzaffar A. on 12.12.12 at 8:27 pm

Can you please share some good open source test management tools as well?

#4 Kanif on 12.13.12 at 3:54 am

Nice article Vijay..

Here you can get a most popular free and paid Testing Tools list used in the testing of the software application:
http://www.softwaretestingclass.com/software-testing-tools-list/

#5 varma on 12.13.12 at 5:24 am

you can use test link – http://www.teamst.org/

#6 Vijay on 12.13.12 at 6:42 am

@ Muzaffar – Here is a list of some good open source test management tools. Remember when it’s open source there are very few choices and many tools have limitations for advance use. You can’t find every solution in one tool.

Use these tools and find which is best for your needs. I find TestLink good for small projects. Features – manage test cases, keywords, requirements, test plan, test case assignments, builds and many more good features.

TestLink (http://www.teamst.org/) – It’s a web based tool to manage test cases and requirements.

Bugzilla Testopia (http://www.mozilla.org/projects/testopia/) – It’s and extension to Bugzilla defect tracking tool.

TestCube (http://www.jatakasource.org/testcube/) – web based test case management

RTH-turbo (http://requirementsandtestinghub.wordpress.com/faq/) – One more web based test management tool

Testitool (http://www.majordojo.com//testitool/) – manage test plan and test cases

This should be enough for you to get started. I’ll cover more recommendations with details for both open source and commercial test case management tools in a separate post.

#7 mahesh on 12.13.12 at 4:06 pm

thanks for sharing. we will add some of these fields in our template

#8 shruthi on 12.13.12 at 4:16 pm

Very usefull article.

Thanks a lot for sharing these.

#9 shruthi on 12.13.12 at 4:18 pm

Very useful article.

Thanks a lot for sharing these.

#10 anu on 12.15.12 at 10:29 am

Thanks for this article. It is very useful for me. Since a long time i am searching for this.

#11 anu on 12.15.12 at 10:32 am

Thanks for this article. It is very useful for me…..

#12 Fuad Mak on 12.23.12 at 9:32 pm

Thank you for sharing this information. It will be useful to our testers at RentTesters and SQA Solution.

#13 radha krishna on 12.31.12 at 4:42 am

good information

#14 aruna on 01.01.13 at 10:07 am

Very very useful site….As a newbie in the field of software testing…this site helps me a lot…..great job….God bless u

#15 Testingwalk on 01.02.13 at 6:03 am

I want to add one more field before Test Steps as “Description”. We can describe here that what we are testing Like: Testing the functionality of …… Page.

#16 m on 01.10.13 at 11:44 am

mokka

#17 raw on 01.13.13 at 3:18 pm

thanks allot for this ,this is realy awesome for us

#18 Manpreet on 01.17.13 at 1:12 pm

Very Useful site..Thanks for all your help…:) Keep it up…!!

#19 kumar on 02.04.13 at 4:47 am

very useful n valuable

#20 CrazyTexan4 on 02.09.13 at 8:42 pm

very good test case template. Anyone wanting to take Software Testing to another level can buy exam papers @ ISEB-sofwaretesting.weebly.com

#21 Partap on 02.11.13 at 6:37 am

Can Anybody send me User Acceptance Test Cases for any VOIP application ?

#22 Vimala on 02.11.13 at 7:52 pm

I am very much interested in software testing jobs, I have completed a course, I understand well but I am not sure if I can check for jobs because I am 38 now, is there any age bar for that?

#23 aparna on 02.13.13 at 12:45 pm

Hi i connected to your site, its helpful for me thanks…

#24 Sugam on 02.17.13 at 10:29 am

Thanks for sharing the info friend. It’s really useful.

#25 Rajaram on 02.22.13 at 4:50 am

Hi.. this is very useful to me thanks..

#26 lokesh sharma on 02.26.13 at 6:18 pm

which testing perform first either retest and regression test after bug fixing.

send answer on lokesh22sharma@gmail.com

#27 arun on 03.15.13 at 10:47 am

MY query is …I’m asked “write testcase for bottle” .Should i use the table format like test case template or test scenario ……or just 1.Description and Expected result alone ?please reply ASAP

#28 Sindhuja M on 04.12.13 at 5:40 am

Hi,This description is very much useful for testers like us.Thanks a lot.

#29 bhumi on 06.26.13 at 7:35 am

very useful site …. good

#30 Aditi on 07.23.13 at 11:11 am

good1..

#31 glad on 07.26.13 at 7:06 am

Hi, this test case is useful and help us a lot. Thanks.

#32 Shrabani on 08.29.13 at 6:53 am

Hi,
This is really very much useful. But I am still not clear regarding the difference between “precondition” and “dependencies”. Can you explain it in more details with example?
Thanks in advance

#33 karthika on 09.06.13 at 2:47 pm

This is very useful to me and every one will like this thank u

#34 Cynthia Mitchell on 02.04.14 at 2:34 pm

I like the template you provided. Can you complete the template with a real live example so I know how interpret and enter the information in the template. I am new to this and need lots of help. If you could use an example of logging into a system to test querying an individual’s contact information. Thanks.

#35 Kals on 02.24.14 at 6:10 am

Good work.. will be helpful..!

#36 mamta on 02.26.14 at 7:28 am

Hello Sir,
Can you please tell me, how i will write the testcases of clinic management web application

#37 mamta on 02.26.14 at 7:30 am

Hello Sir, please tell how to write test cases of prescription templete.

#38 Rajesh Modi on 03.01.14 at 6:52 pm

Hi,
I am a graduate. I am searching for job in software testing. can you guide me to get job.

Thanks in advance,
Rajesh. Modi
9742773880

Leave a Comment