Resources 2.4.x QA  plans

Timescales

We are hoping to complete development mid-June, with QA finishing shortly after that. Ideally, we'll be all done for 4th July, and you can celebrate independence from us in the UK with a light heart! (Of course, we don't celebrate 4th July, so I guess we'll still be hard at work that day...)

2.4x Resources Tool - Test Procedures

All resolved and unresolved issues can be found here- http://confluence.sakaiproject.org/confluence/display/RES/QA+for+2.4.x

• Resolved issues have been fixed and are waiting to be verified.

Resolved issues are allocated by default for testing by the person that reported them, in the hopes that people will be able to test their own issues quickly. A couple of people (John L?) have been nominated to test technical issues. Issues reported by Jim will be allocated to Harriet to test. However, please dive in and test issues assigned to other people!

• Test resolved issues on one of these sites (log on as admin/admin or create yourself a new account if you want to have maintainer view)

http://nightly2.sakaiproject.org:8083/portal
http://nightly2.sakaiproject.org:8082/portal

The Nightly builds are completely rebuilt 3 times a day. There will be approx 20 mins when it is not available. You will usually lose all sites, logins, data after each rebuild.

If large amounts of data is needed for any particular reason, we should let Andrew   know

• For some issues, it will be necessary to test on multiple platforms and browsers. Use your own judgement about this to some extent - for example, it's not necessary to check that 'revise' is now 'edit' cross-platform.
• Verify fix.
• If fixed, close issue
• If not fixed, reopen issue and assign to Jim.
• If fixed, but needs cross-platform testing, please note the platform / browser you tested on, don't close it, and assign it to someone with the appropriate platform. Hannah and Kathy would make a good platform pair, it seems.