From Fedora Project Wiki

m (Remove specific test case reference from general test case template)
Line 1: Line 1:
= Description =
= Description =
{{{description|A brief description of the functionality being tested.}}}
{{{description|A brief description of the functionality being tested.}}}
The test is to discover the problems of IBus and associated input methods (IM).


= How to test =
= How to test =

Revision as of 12:57, 7 May 2009

Description

A brief description of the functionality being tested.

How to test

Be as specific as required for the target audience.


  1. Start here ...
  2. Next do this ...
  3. Finally click that

Expected Results

The following must be true to consider this a successful test run. Be brief ... but explicit.


  1. Step #1 completes without error
  2. The system boots into runlevel 5
  3. Program completes wth exit code 0


Template documentation [edit]

This documentation is transcluded from Template:QA/Test Case/doc. It will not be transcluded on pages that use this template.

You'll want to use this template as follows:

{{QA/Test_Case
|description=This test case ensures that the disk drive(s) are properly dismounted when Fedora is being shut down or when a Reboot is done.
|setup=Install the pre-release version of Fedora that is to be tested on a bare metal system using the default Anaconda settings except to reclaim all disk space in the process.
|actions=
Be as specific as required for the target audience. 
# Start here ...
# Next do this ...
# Finally click that
|results=
The following must be true to consider this a successful test run. Be brief ... but explicit. 
# Step #1 completes without error
# The system boots into runlevel 5
# Program completes with exit code 0
|optional=Optionally provide hints for exploratory testing.
}}
This will result in the example page shown below. Please read QA:SOP test case creation to see how to properly write a test case and categorize it.