Difference between revisions of "Quaste TCS Tool Specification"

From Apache OpenOffice Wiki
Jump to: navigation, search
 
Line 1: Line 1:
 +
<div style="background-color: yellow; text-align: center; font-weight: bold">
 +
This specification is a DRAFT still in discussion.<br>
 +
</div>
 +
 +
== Abstract ==
 +
 +
There is a need of a tool for writing TCS (Test Case Specification) and manage them over [http://quaste.services.openoffice.org QUASTe].<br>
 +
Such a tool already exists (SUN internally) but its version 1.0 has many usability drawbacks and missing features.<br>
 +
 +
 +
 +
 +
http://quaste.services.openoffice.org/index.php?option=com_quaste&task=testresults_analyze
 +
__TOC__
 +
 +
== References ==
 +
 +
{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0;  border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
 +
|-
 +
| width="300" bgcolor="#dddddd" | '''Reference Document''' || bgcolor="#dddddd" | '''Check''' || bgcolor="#dddddd" | '''Location (URL)'''
 +
|-
 +
| |'''[http://wiki.services.openoffice.org/wiki/Specification#Before_Writing_a_Software_Specification_--_What_Else_Do_I_have_to_Do.3F Prerequisites]'''
 +
| [passed/failed]
 +
| n/a
 +
|-
 +
| '''Product Requirement, RFE, Issue ID''' (required)
 +
| [available/not available]
 +
| <PLEASE ENTER LOCATION HERE>
 +
|-
 +
| '''Accessibility Check''' (required)
 +
|
 +
| See accessibility section for check list
 +
|-
 +
| '''[[Test case specification]]''' (required)
 +
| [available/not available]
 +
| <PLEASE ENTER LOCATION HERE>
 +
|-
 +
| IDL Specification
 +
| [available/not available]
 +
| <PLEASE ENTER LOCATION HERE>
 +
|-
 +
| [http://wiki.services.openoffice.org/wiki/The_Three_Golden_Rules_for_Writing_OpenOffice.org_Specifications '''Software Specification Rules''']
 +
| n/a
 +
| n/a
 +
|-
 +
| Other, e.g. references to related specs, Product Concept Document
 +
|
 +
| <PLEASE ENTER LOCATION HERE>
 +
|-
 +
|}
 +
 +
== Contacts ==
 +
 +
{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0;  border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
 +
|-
 +
| width="300" bgcolor="#dddddd" | '''Role''' || bgcolor="#dddddd" | '''Name''' || bgcolor="#dddddd" | '''E-Mail Address'''
 +
|-
 +
| '''Developer'''
 +
| Helge Delfs
 +
| hde@openoffice.org
 +
|-
 +
| '''Quality Assurance'''
 +
| Éric Savary
 +
| es@openoffice.org
 +
|-
 +
| '''Documentation'''
 +
| Helge Delfs <br> Éric Savary
 +
| hde@openoffice.org <br> es@openoffice.org
 +
|-
 +
| '''User Experience'''
 +
| Éric Savary
 +
| es@openoffice.org
 +
|-
 +
|}
 +
 +
== Acronyms and Abbreviations ==
 +
{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0;  border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
 +
|-
 +
| bgcolor="#dddddd" | '''Acronym / Abbreviation''' || bgcolor="#dddddd" | '''Definition'''
 +
|-
 +
| <WYSIWYG>
 +
| <What You See Is What You Get>
 +
|-
 +
|}
 +
 +
== Detailed Specification ==
 +
<START '''TYPING''' HERE>
 +
[[Specification_Template_Help#Detailed_Specification|Help]] | [[UI-Elements|User Interface Element Templates]] | [[Specification_Example|Example Spec]]
 +
 +
== Accessibility ==
 +
Accessibility is the responsibility of the I-Team, beginning with UX, DEV and QA, to ensure that the following requirements are fulfilled:
 +
 +
# Is the feature '''fully keyboard accessible'''?''<br>(Ex: "I can go everywhere and use every function using the keyboard only"''<br/> ''<nowiki><START TYPING HERE></nowiki>''
 +
# Have I specified '''visual alternatives''' for the&nbsp;case that the&nbsp;specified feature includes audio as output? <br/> <nowiki><START TYPING HERE></nowiki>
 +
# Are '''text alternatives '''for all icons and graphics available?<br/> <nowiki><Start typing here></nowiki>
 +
# '''Don't provide important information in colors alone'''''<br>(Ex: marking important information hard coded in red)''<br/> ''<nowiki><START TYPING HERE></nowiki>''
 +
# Does the specified feature respect '''system settings''' for '''font, size, and color '''for '''all''' windows and user interface elements? <br/> <nowiki><START TYPING HERE></nowiki>
 +
# Have I ensured that&nbsp;'''flash rates''' do not exceed 2 hertz for blinking text, objects, or other elements? In any case, try to '''avoid flashing '''UI elements<br/> <nowiki><START TYPING HERE></nowiki>
 +
# Ensure that assistive technology (AT) (like ZoomText or Orca) is able to read everything.<br/> <nowiki><START TYPING HERE></nowiki>
 +
 +
QUESTIONS?
 +
 +
If you need '''help''' while '''designing, implementing or testing''' the accessibility of the UI, ask/visit:
 +
 +
# The [http://wiki.services.openoffice.org/wiki/Accessibility_(A11y)_Quick_Test_Check_List accessibility check list at the OpenOffice.org Wiki]
 +
# [mailto:accessibility@ui.openoffice.org accessibility@ui.openoffice.org] (The accessibility mailing lists, preferred)
 +
# For specific implementation details, architecture: [mailto:mt@openoffice.org mt@openoffice.org] (Malte Timmermann)
 +
# For specific UX and testing questions: [mailto:es@openoffice.org es@openoffice.org] (Éric Savary)
 +
 +
 +
== Migration ==
 +
<START TYPING HERE --- If this part is irrelevant state a reason for its absence.>
 +
 +
== Configuration ==
 +
<START TYPING HERE --- If this part is irrelevant state a reason for its absence.>
 +
 +
[[Specification_Template_Help#Configuration|Help]] | [[Configuration-Table|Configuration Table Template]]
 +
 +
== File Format ==
 +
<START TYPING HERE --- If this part is irrelevant state a reason for its absence.> [[Specification_Template_Help#File_Format|Help]]
 +
 +
[[Specification_Template_Help#File Format|Help]] | [[File Format Table|File Format Table Template]]
 +
 +
== Open Issues ==
 +
<State a bulleted list of issues Issue here>
 +
 +
 
[[Category:Developer Tools]]
 
[[Category:Developer Tools]]
 
[[Category:Specification]]
 
[[Category:Specification]]

Revision as of 11:38, 14 October 2009

This specification is a DRAFT still in discussion.

Abstract

There is a need of a tool for writing TCS (Test Case Specification) and manage them over QUASTe.
Such a tool already exists (SUN internally) but its version 1.0 has many usability drawbacks and missing features.



http://quaste.services.openoffice.org/index.php?option=com_quaste&task=testresults_analyze

References

Reference Document Check Location (URL)
Prerequisites [passed/failed] n/a
Product Requirement, RFE, Issue ID (required) [available/not available] <PLEASE ENTER LOCATION HERE>
Accessibility Check (required) See accessibility section for check list
Test case specification (required) [available/not available] <PLEASE ENTER LOCATION HERE>
IDL Specification [available/not available] <PLEASE ENTER LOCATION HERE>
Software Specification Rules n/a n/a
Other, e.g. references to related specs, Product Concept Document <PLEASE ENTER LOCATION HERE>

Contacts

Role Name E-Mail Address
Developer Helge Delfs hde@openoffice.org
Quality Assurance Éric Savary es@openoffice.org
Documentation Helge Delfs
Éric Savary 		hde@openoffice.org
es@openoffice.org
User Experience Éric Savary es@openoffice.org

Acronyms and Abbreviations

Acronym / Abbreviation Definition
<WYSIWYG> <What You See Is What You Get>

Detailed Specification

<START TYPING HERE> Help | User Interface Element Templates | Example Spec

Accessibility

Accessibility is the responsibility of the I-Team, beginning with UX, DEV and QA, to ensure that the following requirements are fulfilled:

  1. Is the feature fully keyboard accessible?
    (Ex: "I can go everywhere and use every function using the keyboard only"
    <START TYPING HERE>
  2. Have I specified visual alternatives for the case that the specified feature includes audio as output?
    <START TYPING HERE>
  3. Are text alternatives for all icons and graphics available?
    <Start typing here>
  4. Don't provide important information in colors alone
    (Ex: marking important information hard coded in red)
    <START TYPING HERE>
  5. Does the specified feature respect system settings for font, size, and color for all windows and user interface elements?
    <START TYPING HERE>
  6. Have I ensured that flash rates do not exceed 2 hertz for blinking text, objects, or other elements? In any case, try to avoid flashing UI elements
    <START TYPING HERE>
  7. Ensure that assistive technology (AT) (like ZoomText or Orca) is able to read everything.
    <START TYPING HERE>

QUESTIONS?

If you need help while designing, implementing or testing the accessibility of the UI, ask/visit:

  1. The accessibility check list at the OpenOffice.org Wiki
  2. accessibility@ui.openoffice.org (The accessibility mailing lists, preferred)
  3. For specific implementation details, architecture: mt@openoffice.org (Malte Timmermann)
  4. For specific UX and testing questions: es@openoffice.org (Éric Savary)


Migration

<START TYPING HERE --- If this part is irrelevant state a reason for its absence.>

Configuration

<START TYPING HERE --- If this part is irrelevant state a reason for its absence.>

Help | Configuration Table Template

File Format

<START TYPING HERE --- If this part is irrelevant state a reason for its absence.> Help

Help | File Format Table Template

Open Issues

<State a bulleted list of issues Issue here>

Retrieved from "https://wiki.openoffice.org/w/index.php?title=Quaste_TCS_Tool_Specification&oldid=142761"
Personal tools