Print Page | Close Window

What is Test Case? How to write a good test case?

Printed From: One Stop Testing
Category: Software Testing @ OneStopTesting
Forum Name: Test Cases @ OneStopTesting
Forum Discription: You must be well versed in writting Good Test Cases as they only will decide whether you can catch most of bugs or not.
URL: http://forum.onestoptesting.com/forum_posts.asp?TID=4833
Printed Date: 23Dec2024 at 6:47am


Topic: What is Test Case? How to write a good test case?
Posted By: ashwini_123
Subject: What is Test Case? How to write a good test case?
Date Posted: 27Feb2008 at 4:18am

What is Test Case? How to write a good test case?


Test Cases are the implementation of a test case design which will help the software tester to detect defects in the application or the system being tested. This should be the primary goal of any test case or set of test cases. When I write a test case, I think of both types of test cases, positive test cases and negative test cases. Positive test cases are those which execute the happy path in the application and make sure that the happy path is working fine. Negative test cases as the name suggests are destructive test cases which are documented with some out-of-box thinking to break the system.
A Test Case should be documented in a manner that is useful for the current test cycle and any future test cycles. At a bare minimum each test case should contain: Sr No, Summary or Title, Description, Steps to reproduce, Expected Results, Actual Results and Status of the test case or remarks.

Test Case Summary or Title

The Summary or title should contain the essence of the test case including the functional area and purpose of the test. Using a common naming convention that groups test cases encourages reuse and help prevents duplicate test cases from occurring.

Test Case Description

The description should clearly state what sequence of events to be executed by the test case. The Test Case description can apply to one or more test cases; it will often take more than one test case to fully test an area of the application.

Test Case Steps to reproduce

Each test case step should clearly state the navigation, test data, and events required to accomplish the step. Using a common descriptive approach encourages reuse and conformity.

Expected Results of Test Case

The expected behavior of the system after any test case step that requires verification / validation - this could include: screen pop-ups, data updates, display changes, or any other discernable event or transaction on the system that is expected to occur when the test case step is executed.

Status or Remarks

The operational status of the test case - Executed or not executed etc.


Replies:
Posted By: getzephyr
Date Posted: 30May2008 at 12:48am

Test case is a document which describes INPUT,ACTION,EVENT and EXPECTED RESPONSE to determine if feature of an application is working correctly or not. There are several http://www.getzephyr.com/products/test_management_tools.php - test management tools available to write test case, even though I would like to suggest you to try Zephyr, a comprehensive test management system; it helps to open your Test Case Creation application and the areas or test cases assigned to you are right there, all neatly organized for you to start writing them.

A test case should have an input description, Test Sequence and an Expected Behavior.
ex.,
Test Sequence:
Schedule a report [ This can be treated as a Title as well as Test Sequence. Sequence here is the order in which this step is to be executed. The test case document should be prepared in such a way that the test cases should follow a sequence]

Test Input Description:
1.Login to <Abc page> as administrator.
2. Go to Reports page
3. Click on the ‘Schedule reports' button
4. Add reports
5. Update



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


Print Page | Close Window