[WG: Sakai QA] [cle-release-team] Almost ready for a Sakai 10 Bug Bash / Test Fest?

[Neal Caidin]

Hi Beth (and all),

The structure I’m thinking of for the Bug Bash/Test Fest or whatever we call it is Tool-focused. I will have a Google doc with one tab per Tool. Under the Tool tab will be a link to regression scripts, if we have them. If we don’t have regression scripts (or they are too out of date), I may put in a placeholder that indicates folks should do their own testing (i.e. use their own judgment). In the same tab will be a list of all the Jiras associated with the tool, sorted with the highest priority (blockers/criticals) on down.

I’m doubtful we will get all the tools tested and even more doubtful we will get all the Jiras tested (since there is close to 600 Jiras which could use testing of some sort). Also, when I quickly peruse Jiras, quite a few do not have test plans and it is not clear if functional testing is feasible for the “average tester” on many of these. Therefore, my hope is that we can:

* Complete testing of all Blocker and Critical bugs (and some Majors too, if there is time). 
* Perform a simple “triage” to determine which Jiras cannot easily be tested as-is (from a QA tester perspective). This simple triage should help us in later rounds of testing.
* Touch as many tools as possible, so that everything gets at least a little bit of a workout.

Does that sound like the right goals?

I’m thinking we will start the testing next week, but that it will go through the week of Dec 16, at least. 

We need to get QA servers setup, and I think that the QA server managers are waiting for me to provide them with configuration information (like which features will be on by default). I’m working on that, and help and suggestions are always welcome!

I would love it if there were Selenium scripts to automate testing. There are some available for doing setup (creating user accounts, etc) to make testing go a little quicker. 

Thanks,
Neal



Neal Caidin
Sakai Community Coordinator
neal.caidin at apereo.org
Skype: nealkdin
Twitter: ncaidin









On Dec 4, 2013, at 9:38 AM, Kirschner, Beth <bkirschn at umich.edu> wrote:

> Hi Neal,
> 
> Thanks for pushing for a bug-bash in December - UM could chip in a tester or two, but the week of December 16th would be better for us. Will there be any structure to the bug bash? Does anyone know the status of the Selenium scripts and if they could be used for testing?
> 
> Thanks,
> - Beth
> 
> On Dec 2, 2013, at 1:56 PM, Neal Caidin <neal.caidin at apereo.org> wrote:
> 
>> [dev, qa, cle release team]
>> 
>> Hi all,
>> 
>> Feedback appreciated. 
>> 
>> I think it is time to schedule our first Sakai 10  bug bash (or test fest) within the next two weeks,  either the week of December 9 or the week of December 16. 
>> 
>> I believe only the following two bugs are blockers for a test fest?:
>> https://jira.sakaiproject.org/browse/SAK-23918 
>> https://jira.sakaiproject.org/browse/SAK-23917
>> 
>> Are there any other blocker bugs that need to be resolved before we should cut our first QA release off trunk?
>> 
>> Is there a difference between a bug bash and a test fest or are they more or less the same?
>> 
>> My assumption is that having some synchronous testing time is valuable, so I will schedule some Adobe Connect times to be available. I’m on U.S.A east coast (GMT -5 ) but happy to schedule sessions at times convenient for other time zones, if there is some critical mass available in your time zone. By “critical mass” , I mean at least 2 or 3 testers who will block out some time to test. In my experience a handful of dedicated testers can do quite a bit of damage ;-). 
>> 
>> Please let me know your thoughts.
>> 
>> Thanks,
>> Neal
>> 
>> 
>> 
>> Neal Caidin
>> Sakai Community Coordinator
>> neal.caidin at apereo.org
>> Skype: nealkdin
>> Twitter: ncaidin
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> _______________________________________________
>> cle-release-team mailing list
>> cle-release-team at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-qa/attachments/20131204/acd6c35d/attachment.html