What does a good test case look like

by admin on September 24, 2013

What does a good test case look like? What are key elements that one should keep in mind? Please share your views….

#SQASolutionShare on FacebookShare on Google+Share on LinkedInTweet about this on TwitterEmail this to someone

{ 10 comments… read them below or add one }

Mack Gill September 21, 2013 at 6:10 pm

In my opinion, the key elements are test case id, unit to test, assumptions, test data, steps to be executed, priority, expected result, actual result, priority, severity etc.

Melanie Taylor September 21, 2013 at 6:10 pm

In my opinion a key element would be to have a very clear and precise SOP in place, which can be used across the board in all test cases. Accuracy is key, and without a constant practice in place, tests results can be unstable. Furthermore, I believe that any case study should be carried out by a minimum of three people, in order to identify common results as well as possible differentiation.

benfang September 22, 2013 at 6:10 pm

In writing test case, the most difficult part is the expected result. Sometimes it is difficult to determine the expected result. For example, in scientific computation, it often needs an expert to provide such a result.

Earlene September 22, 2013 at 7:10 pm

Here are the things I want to see in test cases. 1. Test Case Name that identifies what the case is about. 2. Preconditions or setup steps. 3. Step by step with expected results listed on each step. 4. I also like to include if known what is not acceptable behavior. So if it is an enhancement to an existing product, the unacceptable would be it acts as it did before. Also, if I need test data, I like to have a file attached with test data or examples of test data for say SoapUI have an example of a valid XML.

Mark Orlicky September 22, 2013 at 7:10 pm

What I’ve had difficulty with in the past concerns level of detail. When I know the application well and describe the expected results, its easy for me to forget that a newbie tester needs to be able to run it, too. At the same time, I don’t want to provide so much info that its like I’m writing the Users Manual with the Test Case!

Brian A. Neiman, Sr September 22, 2013 at 7:10 pm

A good test case is written so that anyone can execute it. This is also a money saver as app expertise is not required. It also will have value for regression testing into the future.

Rajesh Ballakoor September 22, 2013 at 7:10 pm

I have a question to the team, when and where do you apply Test Case development methodology? like boundary value analysis and equivalence class partitioning etc. How would one know what is the coverage the Test case provides after it is executed?

Mohit Rastogi September 22, 2013 at 7:10 pm

Hi all,
You can see the detailed answer in the following link:


Anmol Bagga September 24, 2013 at 6:10 pm

A test case has components that describes an input, action or event and an expected response, to determine if a feature of an application is working correctly

Test cases should test how your system should work, not what it actually does.

In fact a good test case stands alone, sets up pre-test conditions, exercises the application under test (AUT), verifies one thing, reports the results of the verification, then if applicable, cleans up (usually data) and reports the overall test case result; pass or fail.

A test case should include following fields:

1. TC Name: It should not be lengthy n just to differentiate the TC amongst all TC’s of test plan.
2. Description: It is different than TC name and to describe what we are going to verify in this TC.
3. Preconditions (Prerequisite): It should include all the required and mandatory conditions that are required to follow the input steps
4. Input/Steps: define the path to the check point. Mention each n every step to get the expected result
5. Expected Result: what should be the desired outcome of input as per requirement

Manager, Quality Engineering September 24, 2013 at 6:10 pm

A good test case is one, which can be executed by anyone. Even who has mere understanding of the application should be able to execute a test case and report defects. Few key elements that one should keep in mind:
– Test Cases should be written in a manner that they are independent of each other.
– Pr-requisites should be appropriately mentioned
– Steps should be clearly documented and result against each step should be mentioned
(if required) for better understanding.
– Test Case should not be written at a UI level. They should be independent of UI so that any future change or refactoring does not require rewriting of test cases.

Previous post:

Next post: