Archive

Posts Tagged ‘Test Case’

Good Test Case

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.

Categories: Test Case Tags:

Test Case

Test Case : Test case is a document that describes an input, action or event and an expected response to determine if a feature of an application is working correctly and meets the user requirements.A Good test case is the one that has high probability of finding as yet undiscovered error.

The Test case document contains the following fields:

  • Test case id : This is an id given to every test case and it should be unique.
  • Test case decription : This field contains the brief description of what we are going to test in that application.
  • Test input : This contains the input that we are going to give to test the application or system.
  • Test Action : This field explains the action to be performed to execute the test case.
  • Expected results : This fielsd contains the description of what tester should see after all test steps has been completed.
  • Actual results : This field contains a brief description of what the tester saw after the test steps has been completed.
  • Result:This is often replaced with either pass or fail. If both the expected result and actual result are same then the result is pass else the result is fail.
Categories: Test Case Tags: