Having an excellent test case template makes it easier for your team to communicate and work efficiently. So what exactly needs to go into your test case template?

Read more - http://ow.ly/hkd51

Try ReQtest today - http://www.reqtest.com/
Like us on Facebook -   / reqtest  

Transcript -

Hi, I'm Carla from ReQtest, today we are going to show you how to develop a test case template.

Having an excellent test case template makes it easier for your team to communicate and work efficiently.

Ok, let's be honest here, A template is nothing more than a bunch of headings. The key is knowing which of these headings are important.

You probably won't need every single heading in every situation, so start with the main few and add others as you need them.

First up you need an ID field which obviously has to be unique so as to identify the test case. If you use a good test management tool, (like ReQtest) the tool will automatically assign an ID. Easy Peasy!

Next you need a title. This should be a concise, revealing description of the test case, such as "Add customer". The title is important because it's normally the first thing you see when scanning through a list of test cases.

The pre-conditions field isn't relevant to every test case, so you may want to keep it as an optional field. Only use pre-conditions if you actually need them, for example, if a set of customers needs to be loaded into the system before testing begins.

Test Steps give the tester a numbered list of steps to perform in the system, making it easier to understand the test case.

It is recommended to have between 3 and 8 steps in a test case, no less and no more.
Finally, the tester needs to know the expected result to assess if the test case was successful.

Of course there are many other headings that could be useful in a test case, including Post-Conditions, Test Data, Priority, Version, Author and more.

You can read all about those by clicking the link below.

I'll see you next time!