Difference between revisions of "NativeBrOffice TestCase"

From Apache OpenOffice Wiki
Jump to: navigation, search
 
Line 32: Line 32:
 
<H5>Test case 1</H5>
 
<H5>Test case 1</H5>
 
* Install BrOffice.org
 
* Install BrOffice.org
* Check that doesn't appear any text or image referencing OpenOffice.org
+
* Check that doesn't appear any text or image referencing OpenOffice.org on the install process
<H5>Test case 2</H5>
+
* Check appears the name BrOffice.org at the top of the window
* new document
+
<H5>Test case 3</H5>
* do this
+
* Open BrOffice.org
<HR>
+
* Check the logo which appears is from BrOffice.org
<H3>Problematic areas [Optional]</H3>
+
* A small OpenOffice.org logo and its mention is allowed.
<P>something that looks like a bug</P>
+
<H5>Test case 4</H5>
<HR>
+
* Go to the About dialog
<h3>Acronyms:</h3>
+
* Check the image that appears contains the BrOffice.org logo
* Acronym 1
+
* ...
+
 
<HR>
 
<HR>
 
<h3>References (specification, API-documentation, ...):</h3>
 
<h3>References (specification, API-documentation, ...):</h3>
Line 48: Line 46:
 
* [http://... http://...]
 
* [http://... http://...]
 
<HR>
 
<HR>
<H1>Explanation of fields</H1>
 
# '''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
 
## PRELIMINARY: Status is the initial conception of a test document.
 
## STANDARD: A test document is considered to be stable (and reviewed).
 
## 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):
 
## Best if a test case works without test documents
 
## Second best if test documents are created during the test.
 
## 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
 
## Use detailed test instructions:
 
### load documents specified above
 
### select dialog “foo”
 
### click here
 
### click there
 
### [...]
 
## Expected result of the test operation
 
## Variations of the test run:
 
#### Repeat the test under different (pre)conditions again
 
#### Select different options of the feature
 
#### 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.
 
 
<H1>Technical Instructions to Create a Test Case Specification</H1>
 
: 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:
 
<PRE>
 
<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)
 
</PRE>
 
  
<H1>HTML Code of the Test Case Specification Template</H1>
 
<PRE>
 
<html>
 
<head>
 
    <title>Test case specification document</title>
 
    <style>
 
    <!--
 
        H5 { text-decoration: underline }
 
    -->
 
    </style>
 
</head>
 
<body text="#000000" bgcolor="#FFFFFF">
 
   
 
    <!-- add test title here - Second -->
 
    <H1 ALIGN=CENTER><U>Test Name: <B>Test Name</B></U></H1>   
 
    <!-- ++++++++++++++++++++++++++++++++ -->       
 
    <HR>
 
    <TABLE WIDTH=100% BORDER=1 CELLSPACING=0>
 
      <COL WIDTH=30%>
 
      <COL WIDTH=40%>
 
      <COL WIDTH=30%>
 
  <TR>
 
  <TD>
 
            <!-- 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>
 
            </TD>
 
  <TD>
 
            <!-- 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>
 
            </TD>
 
  <TD>
 
            <!-- 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>
 
            </TD>
 
        </TR>
 
  </TABLE>
 
    <!-- ++++++++++++++++++++++++++++++++ -->
 
    <!-- add test purpose here -->
 
    <H3>Test purpose</H3>
 
    <P>Verify that OpenOffice.org use it right.</P>
 
    <!-- ++++++++++++++++++++++++++++++++ -->
 
    <HR>   
 
    <!-- add major known issues here -->
 
    <h3>Known issues:</h3>
 
    <ul>
 
        <li><a href="http://www.openoffice.org/issues">issue </a>
 
    </ul>
 
    <!-- ++++++++++++++++++++++++++++++++ -->
 
    <hr>
 
    <!-- add Preconditions here -->
 
    <H3>Preconditions of the test:</H3>
 
    <UL>
 
        <LI>locales
 
        <LI>language settings
 
        <LI>etc.       
 
    </UL>
 
    <!-- ++++++++++++++++++++++++++++++++ -->
 
    <HR>
 
    <!-- add test documents here if needed -->
 
    <H3>Test documents</H3>
 
    <UL>
 
        <LI><a href="http://www.openoffice.org/testdocument.sxw">Test document</a>
 
    </UL>
 
    <!-- ++++++++++++++++++++++++++++++++ -->
 
    <HR>
 
    <!-- add test cases here -->
 
    <H3>Test cases</H3>
 
    <H5>Test case 1</H5>
 
    <UL>
 
        <LI>new document
 
        <LI>do this
 
    </UL>
 
    <H5>Test case 2</H5>
 
    <UL>
 
        <LI>new document
 
        <LI>do this
 
    </UL>
 
    <!-- ++++++++++++++++++++++++++++++++ -->
 
    <HR>
 
    <!--  add Problematic areas here if needed  -->
 
    <H3>Problematic areas</H3>
 
    <P>something that looks like a bug</P>
 
    <!-- ++++++++++++++++++++++++++++++++ -->   
 
    <hr>
 
    <!-- add Acronyms here if needed -->
 
    <h3>Acronyms:</h3>
 
    <ul>
 
        <li>
 
    </ul><!-- ++++++++++++++++++++++++++++++++ -->
 
    <hr><!-- add link to specification here -->
 
    <h3>References (specification, API-documentation, ...):</h3>
 
    <ul>
 
        <li><a href="http://specs.openoffice.org/">http://specs.openoffice.org/</a>
 
        <li><a href="http://">http://</a></li>
 
    </ul>
 
    <!-- ++++++++++++++++++++++++++++++++ -->
 
</body>
 
</html>
 
</PRE>
 
 
[[Category:Specification]][[Category:Quality_Assurance]]
 
[[Category:Specification]][[Category:Quality_Assurance]]

Revision as of 05:05, 20 April 2007

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

Test Name: Enter Test Name Here

Document Owner:
Caio Sousa

Last Document Change:
20. Apr.2007

Status of Document:
Preliminary

Test purpose

Verify that BrOffice.org brand countains no references to the product OpenOffice.org.


Known issues:

  • None

Preconditions of the test:

  • Got a BrOffice.org branded build

Test documents

  • Don't apply

Test cases

Test case 1
  • Install BrOffice.org
  • Check that doesn't appear any text or image referencing OpenOffice.org on the install process
  • Check appears the name BrOffice.org at the top of the window
Test case 3
  • Open BrOffice.org
  • Check the logo which appears is from BrOffice.org
  • A small OpenOffice.org logo and its mention is allowed.
Test case 4
  • Go to the About dialog
  • Check the image that appears contains the BrOffice.org logo

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


Personal tools