Difference between revisions of "Test case specification template"

From Apache OpenOffice Wiki
Jump to: navigation, search
m (Undo revision 32026 by Rex (Talk))
m (Undo revision 32025 by Rex (Talk))
Line 1: Line 1:
This document can be used as a skeleton to write test case specifications.
This document can be used as a skeleton to write test case specifications.
<H1 ALIGN=CENTER><U>Test Name: <B>Rex</B></U></H1>     
<H1 ALIGN=CENTER><U>Test Name: <B>Enter Test Name Here</B></U></H1>     

Latest revision as of 11:30, 25 October 2009

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:

Status of Document:

Test purpose

Verify that OpenOffice.org use it right.

Known issues:

Preconditions of the test:

  • locales
  • language settings
  • etc.

Test documents

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


  • Acronym 1
  • ...

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

Explanation of fields

  1. Document Owner: Your name should be written here.
  2. Last Document Change: Date has to be written in form like this: 10. Nov. 2005
  3. 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
  4. Test purpose: Add test purpose here
  5. Known issues: Add major known issues here
  6. Preconditions of the test: Add preconditions here
  7. 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.
  8. 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. 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...)
  9. 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 test case specification)
<H3> (heading 3 for the sub parts of the test case specification)
<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)

HTML Code of the Test Case Specification Template

    <title>Test case specification document</title>
        H5 { text-decoration: underline }
<body text="#000000" bgcolor="#FFFFFF">
    <!-- add test title here - Second -->
    <H1 ALIGN=CENTER><U>Test Name: <B>Test Name</B></U></H1>    
    <!-- ++++++++++++++++++++++++++++++++ -->        
      <COL WIDTH=30%>
      <COL WIDTH=40%>
      <COL WIDTH=30%>
            <!-- Your name should be written here -->
				<P><FONT STYLE="font-size: 8pt"><B>Document Owner:</B><BR></FONT><SPAN STYLE="font-weight: medium">Your Name</SPAN></P>
            <!-- Date has to be written in form like this: 10. Nov. 2005 -->
				<P><FONT STYLE="font-size: 8pt"><B>Last Document Change:</B><BR></FONT><SPAN STYLE="font-weight: medium">DD. MMM. YYYY</SPAN></P>
            <!-- Status of this document can be: Preliminary, Standard, Obsolete -->
				<P><FONT STYLE="font-size: 8pt"><B>Status of Document:</B><BR></FONT><SPAN STYLE="font-weight: medium">Preliminary</SPAN></P>
    <!-- ++++++++++++++++++++++++++++++++ -->
    <!-- add test purpose here -->
    <H3>Test purpose</H3>
    <P>Verify that OpenOffice.org use it right.</P>
    <!-- ++++++++++++++++++++++++++++++++ -->
    <!-- add major known issues here -->
    <h3>Known issues:</h3>
        <li><a href="http://www.openoffice.org/issues">issue </a>
    <!-- ++++++++++++++++++++++++++++++++ -->
    <!-- add Preconditions here -->
    <H3>Preconditions of the test:</H3>
        <LI>language settings
    <!-- ++++++++++++++++++++++++++++++++ -->
    <!-- add test documents here if needed -->
    <H3>Test documents</H3>
        <LI><a href="http://www.openoffice.org/testdocument.sxw">Test document</a>
    <!-- ++++++++++++++++++++++++++++++++ -->
    <!-- add test cases here -->
    <H3>Test cases</H3>
    <H5>Test case 1</H5>
        <LI>new document
        <LI>do this
    <H5>Test case 2</H5>
        <LI>new document
        <LI>do this
    <!-- ++++++++++++++++++++++++++++++++ -->
    <!--  add Problematic areas here if needed  -->
    <H3>Problematic areas</H3>
    <P>something that looks like a bug</P>
    <!-- ++++++++++++++++++++++++++++++++ -->    
    <!-- add Acronyms here if needed -->
    </ul><!-- ++++++++++++++++++++++++++++++++ -->
    <hr><!-- add link to specification here -->
    <h3>References (specification, API-documentation, ...):</h3>
        <li><a href="http://specs.openoffice.org/">http://specs.openoffice.org/</a>
        <li><a href="http://">http://</a></li>
    <!-- ++++++++++++++++++++++++++++++++ -->
Personal tools