Today we'll be working on some pre-testing. It must be done as soon as possible today so that we can be ready for and start bug parade first thing tomorrow.
There are three things needed for pre-testing: Run unit tests in testswarm log into http://swarm.fluidproject.org/ and let it run all the unit tests in the browsers you are testing Spot test the demos run through the demos ( http://build.fluidproject.org/ ) and just make sure there are no obvious problems File jiras for any issues found Here is the set of configurations to test. Please fill in any blank spots with the configurations you'd like to volunteer to test. Win XP Win 7 Mac 10.6 Chrome [1] n/a n/a Firefox 4 n/a Firefox 3.6 Justin IE 9.0 n/a n/a IE 8.0 Justin n/a IE 7.0 n/a n/a IE 6.0 n/a n/a Safari 5 [2] n/a n/a Thanks Justin On 2011-05-13, at 2:16 PM, Justin Obara wrote: > Things have been going well and we've focussed in on what needs to be done > for the 1.4 release. At the dev meeting this week we decided that we would > push up the pre-testing and the bug parade to next week. > > On Monday May 16 we'll do a quick testing sprint. > > use testswarm to run through all the unit tests. > do spot testing on all the components > > Starting Tuesday May 17 we'll be in bug parade, with standard bug parade > rules applying. New for this time around though we will be doing pull > requests only for pushing code up to the project repo. Also you can view a > list of all the bug parade issues from this jira report (note it will be > updated after the testing sprint). > > http://issues.fluidproject.org/secure/ConfigureReport.jspa?atl_token=hLyns-VDmh&filterid=10128&mapper=components&selectedProjectId=10001&reportKey=com.atlassian.jira.plugin.system.reports%3Asinglelevelgroupby&Next=Next > > Thanks > Justin
_______________________________________________________ fluid-work mailing list - [email protected] To unsubscribe, change settings or access archives, see http://fluidproject.org/mailman/listinfo/fluid-work
