Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Testing Fluid Components

Section
Column
width60%
Wiki Markup


h2. Testing Methods


Currently there are two methods of testing: manual and unit.


\\

Presently the [doh.robot|http://dojotoolkit.org/2008/08/11/doh-robot-automating-web-ui-unit-tests-real-user-events] is being investigated for automated testing.

Selenium and Windmill were being investigated for automated testing but have been put aside for the time being.

Testing Environments

The testing environments are based on Yahoo's A-grade browsers

 

Win 2000†

Win XP

Win Vista

Mac 10.4†

Mac 10.5

Firefox 3

A-grade

A-grade

A-grade

A-grade

A-grade

Firefox 2

 

A-grade

 

 

A-grade

IE 7.0

 

A-grade

A-grade

 

 

IE 6.0

A-grade

A-grade

 

 

 

Opera 9.5

 

A-grade

 

 

A-grade

Safari 3.1*

 

 

 

A-grade

A-grade

* Does not support keyboard accessibility (a11y)

Not currently available for testing

Reporting Bugs

Any bugs found should be reported in Jira

To reduce the chance of creating a duplicate bug report, it is a good idea to browse Jira first.

Reporting Format

All bug reports should include at least the following information

  • Title of bug report
  • The component it affects
  • The version it affects
  • A description of the bug
  • steps to reproduce the bug

Using Jira

Registering in Jira

Before you can report any bugs, you need to create an account in Jira.

From the main Jira page click on the "Signup" link. Image Removed
 
Fill out the registration form completely and submit. Image Removed

Browsing

There are several ways to browse the bug reports in Jira.

Using the "Quick Search" field at the upper right corner, search by keyword(s). Image Removed
 
The "Home" page contains saved filters Image Removed
 
The "Browse Project" page contains project level filters; e.g. by component, assignee, and etc.
 
Image Removed
The "Find Issue" page allows for the creation of a custom query. Image Removed
 

Creating a New Bug

Login, if you haven't already done so.

Click the "Create New Issue" link at the top of the page. Image Removed
 
For step 1 of 2, you can use the default selections. Click the 'Next' button to proceed to step 2 or 2.
Image Removed

In step 2 of 2 you will need to fill out the form and click the 'Create' button to complete. See the "Reporting Bugs" section above, for necessary information to include here.

Image Removed
 


[Selenium|http://selenium.openqa.org/] and [Windmill|http://windmill.osafoundation.org/] were being investigated for automated testing but have been put aside for the time being.

\\

h2. Testing Environments

|| || {color:#990033}Win 2000†{color} || Win XP || Win Vista || {color:#990033}Mac 10.4†{color} || Mac 10.5 ||
| *[*Firefox 3*|#ff3]* | {center}(?)
{center} | {center}(/)
{center} | {center}(/)
{center} | {center}(?)
{center} | {center}(/)
{center} |
| *[*Firefox 2*|#ff2]* | | {center}(/)
{center} | | | {center}(/)
{center} |
| *[*IE 7.0*|#ie7]* | | {center}(/)
{center} | {center}(/)
{center} | | |
| *[*IE 6.0*|#ie6]* | {center}(?)
{center} | {center}(/)
{center} | | | |
| *[*Opera 9.5*|#o95]* | | {center}(/)
{center} | | | {center}(/)
{center} |
| *[*Safari 3.1\**|#s31]* | | | | {center}(?)
{center} | {center}(/)
{center} |

The testing environments are based on [Yahoo's A-grade browsers|http://developer.yahoo.com/yui/articles/gbs/]
|| || Win 2000† || Win XP || Win Vista || Mac 10.4† || Mac 10.5 ||
| *Firefox 3* | A-grade | A-grade | A-grade | A-grade | A-grade |
| *Firefox 2* | | A-grade | | | A-grade |
| *IE 7.0* | | A-grade | A-grade | | |
| *IE 6.0* | A-grade | A-grade | | | |
| *Opera 9.5* | | A-grade | | | A-grade |
| *Safari 3.1\** | | | | A-grade | A-grade |
\* Does not support keyboard accessibility (a11y)

*†* Not currently available for testing

\\

h2. Reporting Bugs

Any bugs found should be reported in [Jira|http://issues.fluidproject.org]

To reduce the chance of creating a duplicate bug report, it is a good idea to browse Jira first.

h3. Reporting Format

All bug reports should include at least the following information
* Title of bug report
* The component it affects
* The version it affects
* A description of the bug
* steps to reproduce the bug

\\

h2. Using Jira


h3. Registering in Jira

Before you can report any bugs, you need to create an account in Jira.

From the main [Jira|http://issues.fluidproject.org] page click on the "Signup" link. !Picture 2.png|align=left!
 
\\
\\

Fill out the registration form completely and submit. !Picture 3.png|align=left!\\
\\
\\

h3. Browsing

There are several ways to browse the bug reports in Jira.

Using the "Quick Search" field at the upper right corner, search by keyword(s). !Picture 4.png|align=left!
 
\\
\\

The "Home" page contains saved filters !Picture 5.png|align=left!
 
\\
\\
\\
\\

The "Browse Project" page contains project level filters; e.g. by component, assignee, and etc.
 
\\  !Picture 9.png|align=left!\\
\\
\\
\\
\\
The "Find Issue" page allows for the creation of a custom query. !Picture 8.png|align=left!
 
\\

h3. Creating a New Bug

Login, if you haven't already done so.

Click the "Create New Issue" link at the top of the page. !create new.png|align=left!
 
\\
\\

For step 1 of 2, you can use the default selections.  Click the 'Next' button to proceed to step 2 or 2.
\\  !step 1.png|align=left!\\
\\

In step 2 of 2 you will need to fill out the form and click the 'Create' button to complete. See the "Reporting Bugs" section above, for necessary information to include here.

\\  !step 2.png|align=left!
 
Column
width40%
Panel
borderColor#566b30
bgColor#fff
titleBGColor#D3E3C4
titleOn this Page
borderStylesolid
Table of Contents
minlevel2
Panel
bgColorwhite
titleBGColor#c1b7c3
titleComponents
borderStylesolid