Hi everyone,

    I was very encouraged to hear that you all were interested in helping test the code for the gradebook.  With a group like this testing, I’m certain we can ensure that the functionality is solid pretty rapidly.  From what I’ve been told, most of you can begin participating in this effort next week.  

 

There is an updated spec with annotations at http://bugs.sakaiproject.org/confluence/display/SG2X/2.5+Release (Gradebook 2.5 Wireframes – Annotated) that I encourage everyone to review.

 

First, I want to discuss where to test!  Right now this is what we have available:

 

1) Indiana has the code deployed to our test Oncourse CL server.  For roughly a week we’ll have the generic code with out any local modifications.   You are more than welcome to test here.  I will need to create sites for you and you will also need an IU guest account.  Instructions on creating a guest account can be found at:  http://kb.iu.edu/data/alqu.html. Please let me know your username if you’d like to test here and I will create a site for you

2) The nightly servers (which rebuild every 4 hours)

3) Check the code out to local instance

 

If folks are able to bring up a server from trunk, that would be great, too.  Unfortunately Indiana doesn’t have the resources for this just now.  

 

As for the testing, I have not been able to create specific test cases for this effort and will be taking an exploratory testing approach.   IU has a pretty tight timeline so I’m not sure I’ll be able to spend a lot of time documenting test cases prior to June 2.   Given our numbers, it seems like it would be beneficial to break up testing into larger chucks and rotate (Gradebook Setup, Enter Grades, Assignment tool integration, ect).  This may also depend on test location preferences.  I’ve created a QA page at http://bugs.sakaiproject.org/confluence/display/SG2X/QA.  Right now it ispretty much has our names and a quick brainstorm of areas to test.   Are there certain areas each of you are particularly interested in?

 

Megan