Hello,

Starting tomorrow ( April 1 - April 6), we will be testing the 1.0 release. It is quite a lot of testing this time around so any help would be greatly appreciated.

All of the testing tasks can be found on the Release Testing Tasks page of the wiki:
http://wiki.fluidproject.org/display/fluid/Release+Testing+Tasks

If you would like to start a testing task, just drag it from the available list into your personal task list. If you do not have one, please let me know and I'll make you one.

The accompanying test plans can be found on the Testing Fluid components page of the wiki:
http://wiki.fluidproject.org/display/fluid/Testing+Fluid+Components

Please not that the quick-start-examples don't have specific test plans for them, please use related test plans to test them with.

For unit tests, you simply need to launch the page. When the page has finished completely loading, if all of the text is green, the test passed. If there are any failures, the bar at the top should turn red and the offending tests will be marked with red text.

The check shipped examples tasks just require you to make sure that all of the html files shipped in the release load without errors and try some basic functionality.

If you do find any bugs, please file them in our issue tracker
http://issues.fluidproject.org/secure/Dashboard.jspa

Please make sure to search for your issue before you file it, in case it already exists. If it does exist please comment on the issue as necessary. If it does not exist please create a new jira issue for it. Instructions for doing this are on the testing fluid components page.
http://wiki.fluidproject.org/display/fluid/Testing+Fluid+Components

If you have any questions of find any problems with the test plans please don't hesitate to mention it to me.

Thanks for all of the help
Justin



_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work

Reply via email to