Print Page | Close Window

Test Cases 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=2960 Printed Date: 02Dec2024 at 4:34pm Topic: Test Cases Posted By: tanushree Subject: Test Cases Date Posted: 17Oct2007 at 3:42am Test Cases As testers build the Master Matrix, they also build their individual test cases. These are the specific functions testers must verify within each test category to qualify the feature. A test case is identified by ID number and prioritized. Each test case has the following criteria: - Purpose - Reason for the test case - Steps - A logical sequence of steps the tester must follow to execute the test case - Expected Results - The expected result of the test case - Actual Result - What actually happened when the test case was executed - Status - Identifies whether the test case was passed, failed, blocked or skipped. - Pass - Actual result matched expected result - Failed - Bug discovered that represents a failure of the feature - Blocked - Tester could not execute the test case because of bug - Skipped - Test case was not executed this round - Bug ID - If the test case was failed, identify the bug number of the resulting bug.

Print Page | Close Window