Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Current »

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 to test maintainer/access view)

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

The Nightly builds are completely rebuilt six times a day (every four hours: midnight/noon EDT, 4 am/pm EDT, and 8 am/pm EDT). There will be approx 20-30 mins when it is not available during each rebuild. You will usually lose all sites, logins, data after each rebuild. If a large amount of data is needed for any particular testing, we can ask Andrew Poland to preserve the database tables during a series of rebuilds.

  • For some issues, it will be necessary to test on multiple platforms and browsers. Use your own judgment about this to some extent - for example, it's not necessary to check that 'revise' is now 'edit' cross-platform.
  • Verify fix.
  • If fixed and ready to be merged into the branch, close the ticket, add a comment documenting the extent to which the fix is verified, and assign the ticket to Mike Osterman.
  • 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.
  • When Mike has merged the fixes into the 2.4.x maintenance branch, hwe will unassign the ticket and add a comment saying "merged to 2.4.x".

 

XP + IE6

XP + IE7

XP + Firefox 2.0

Vista+ IE7

Vista+ Firefox 2.0

Mac + Safari

Mac + Firefox 2.0

Mac + Camino (not officially supported)

Mike O

yes

yes

yes

yes

yes

yes

yes

yes

Harriet

yes

yes

yes

 

 

yes

yes

 

Hannah

 

 

 

 


yes

yes

yes

Kathy

yes

yes

yes

 

 

 

 

 

  • No labels