This document can be used as a skeleton to write test case specifications.

Test Name: Enter Test Name Here

Document Owner:
Your Name

Last Document Change:
DD. MMM.YYYY

Status of Document:
Preliminary

Test purpose

Verify that OpenOffice.org use it right.

Known issues:

issue

Preconditions of the test:

locales
language settings
etc.

Test documents

Test document

Test cases

Test case 1

new document
do this

Test case 2

new document
do this

Problematic areas [Optional]

something that looks like a bug

Acronyms:

Acronym 1
...

References (specification, API-documentation, ...):

Explanation of fields

Document Owner: Your name should be written here.
Last Document Change: Date has to be written in form like this: 10. Nov. 2005
Status of Document: Preliminary, Standard, Obsolete
1. PRELIMINARY: Status is the initial conception of a test document.
2. STANDARD: A test document is considered to be stable (and reviewed).
3. OBSOLETE: Is a test document that has been identified unnecessary. For example due to; technology changes, parts have been removed from product
Test purpose: Add test purpose here
Known issues: Add major known issues here
Preconditions of the test: Add preconditions here
Test documents: Add test documents (if needed):
1. Best if a test case works without test documents
2. Second best if test documents are created during the test.
3. Sometimes an existing test document saves a lot of time (i.e. one with many different languages or fonts takes time to create). Only in this case, include it in the test case and place a link to the test documents into the test case. If “arbitrary documents from real life” are required for a test, different documents should be used in each test cycle.
Test cases: Add test cases here
1. Use detailed test instructions:
  1. load documents specified above
  2. select dialog “foo”
  3. click here
  4. click there
  5. [...]
2. Expected result of the test operation
3. Variations of the test run:
  1. 1. Repeat the test under different (pre)conditions again
    2. Select different options of the feature
    3. Try different test approaches (using the mouse, using keyboard shortcuts, travel with <Tab>-key through a dialog...)
Problematic areas [Optional]: Something that looks like a bug, but is the intended behavior or a known limitation.

Technical Instructions to Create a Test Case Specification

The test has to be written in HTML.

Use a text editor for creating and editing. The reason is that the office application low up the code and reformats the page.

Use the following HTML tags only:

<UL> (unordered list)
<OL> (ordered list)
<LI> (list item)
<H1> (heading 1 for the title of the testplan)
<H3> (heading 3 for the sub parts of the testplan)
<H5> (heading 5 for the sub parts of the test cases)
<HR> (horizontal line for separate each chapter)
<TABLE>, <TR> and <TD> (to create tables)

Test case specification template

Contents