Manual Test Case

The most basic definition of a test case is a set of conditions under which a tester determines whether an application under test is working as intended.

The most basic definition of a test case is a set of conditions under which a tester determines whether an application under test is working as intended. Our test cases at QA Mentor are a little more informative. We will create manual test cases in any format requested, but most often use a template that can be easily uploaded into Quality Center. Each test case contains a great deal of very important information, including but not limited to the following:

Test Case ID

Each test case has a unique ID that can be easily used for a traceability matrix mapping to requirements.

Objective

We define the purpose or objective of each test case in the context of the phase of testing it will be used.

Precondition

These are the tasks, steps, or data requirements necessary in order to execute the test case. For example, users may need to be created or permissions may need to be configured before the test case can be run.

Post Condition

This section explains any data that may need to be removed after the test case is complete. In order to keep databases clean, scripts may be run to delete users or other data after execution.

Steps

The heart of the test case, the steps provide detailed descriptions for each user action necessary to execute it.

Expected Results

These are taken directly from requirements and indicate the functionality or behavior of the system in response to each of the steps taken. For example, clicking on a link should open a specific page, or entering invalid information should present the user with an error message.

Pass/fail

This column indicates whether or not each test step behaved as expected.

Actual Results

If functionality was different than expected, observations are put in this column to describe the actual behavior.

Execution Results

Complete description of the results of the execution that contain all defect numbers attributed to each test case step the issues were found in.

Scroll Up