[WG: Sakai QA] [Building Sakai] Sakai 10.3 pre-RC testing

[Neal Caidin]

Hi Alaa,

Thank you.

Yes, for right now it is one-by-one testing pre-RC.  When we get to the
Release Candidate then we will want to do Smoke Testing or more.

Neal


On Tue, Nov 11, 2014 at 4:59 PM, Alaa NIZAR <alaanizar at iihem.ac.ma> wrote:

> Hi,
>
> Is there any smoke test? Or should we test issues one-by-one?
>
> Yours,
> Alaa
> Sent from Samsung Mobile.
>
>
> -------- Original message --------
> From: Neal Caidin
> Date:11/11/2014 21:40 (GMT+00:00)
> To: Sakai-Dev ,"sakai-qa at collab.sakaiproject.org QA"
> Subject: Re: [Building Sakai] Sakai 10.3 pre-RC testing
>
> I've added in a page on the google doc
>
> http://bit.ly/1wPafZ3
>
> called "Open issues".  These are issues that someone tagged as desirable
> to get into 10.3 but has not yet been fixed.
>
> Thanks,
> Neal
>
>
> On Tue, Nov 11, 2014 at 10:32 AM, Neal Caidin <neal.caidin at apereo.org>
> wrote:
>
>> Hi all,
>>
>> Sakai 10.3 pre-RC testing is going great, but that doesn't mean we
>> couldn't use your help, we could!
>>
>> We are in the middle of testing. I am working on a Confluence page but in
>> the meantime, since this pre-RC (release candidate) testing is pretty
>> straight-forward, thought I would update you on testing status and needs
>> (and a google doc to jump in and help).
>>
>> We need testing of Jiras that have been merged into trunk [1] and need to
>> be verified before going into the 10.x branch. I've created a spreadsheet
>> [2] .
>>
>> On my spreadsheet [2], I've reflected triage I did on the issues. My
>> triage includes
>>
>> * Guessing whether a functional QA person or a Developer is necessary to
>> test.
>> * Whether I could discern that a Test Plan exists (either in Test Plan
>> field, Description or Comments (worst place to put a Test Plan! get buried
>> within other comments too easily)
>> *  Whether there is a question about merging. Several different issues
>> here including
>>         - should it be targeted for 10.3 or not
>>         - questions if the issue looks tested but has not had the Tested
>> button pressed.
>>         - other
>>
>> FYI - we just are in the middle of having a thread about Jiras that
>> relate to Assignments with Anonymous grading [3].
>>
>> Please help test some Jiras [2].
>>
>> Quick stats:
>> * 92 issues already merged for 10.3 ! (Thanks Earle!)
>> * 30 issues (approximately) in the queue for testing before being merged
>> * About 1/3 of the issues have "Test Plans"
>> * About 2/3 of the issues seem like they need a Developer (i.e. someone
>> with more advanced skills than an average QA tester)
>>
>>
>> [1] Nightly servers (trunk and trunk experimental can be used) -
>> http://nightly2.sakaiproject.org
>>
>> [2] Jira list -  http://bit.ly/1wPafZ3
>>
>> [3] Anonymous grading Jiras
>> https://jira.sakaiproject.org/browse/SAK-27824
>> https://jira.sakaiproject.org/browse/SAK-28044
>> https://jira.sakaiproject.org/browse/SAK-27865
>> https://jira.sakaiproject.org/browse/SAK-27838
>>
>> Cheers and Thanks,
>> Neal
>>
>>
>>
>
> --
> This message has been scanned for viruses and
> dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
> believed to be clean.
> --
> This message has been scanned for viruses and
> dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
> believed to be clean.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-qa/attachments/20141111/544e7c82/attachment.html