[cle-release-team] [Building Sakai] Jiras without Test plans

[Steve Swinsburg]

This already exists, though it is on a separate tab when you edit an issue so easy to miss. Maybe that could be brought to the main tab?

cheers,
Steve


On 22/09/2012, at 12:57 AM, Branden Visser <mrvisser at gmail.com> wrote:

> Hi Neal, if there was a custom "Test Plan" text field in JIRA, you
> could create a filter to track issues that need testing and have an
> empty test plan.
> 
> It won't get rid of the manual plumbing, but might make progress on
> that front more visible.
> 
> Hope that helps,
> Branden
> 
> On Fri, Sep 21, 2012 at 10:45 AM, Neal Caidin
> <nealcaidin at sakaifoundation.org> wrote:
>> [to Dev and CLE release team]
>> 
>> Hi All,
>> 
>> As the QA team goes through the Jiras that need verification, we often find ones for which it is not clear if functional testing is required or not. This could be because there is no test plan included, and reading through the comments may or may not help. Or it could be because there is no genuine way to perform functional testing. Or in some cases it could be that it requires a collaboration between functional and technical (e.g. have a setting changed on the server first and then test).
>> 
>> What I've been doing on these, individually, is to email the developer (or put a comment in the Jira, I haven't been consistent about this) to ask. I think I've had about 100% response rate from developers (Thank you!!!), however, I wonder if there is not a more efficient way to manage this. And I don't think all QA testers do this, most probably just give up and go to the next ticket or give up entirely.
>> 
>> The QA team is experimenting with labeling the tickets that need follow up with a "qatechreview" tag. Maybe there is a way to leverage this systematically? Any ideas?
>> 
>> Thanks and Happy Friday,
>> 
>> Neal
>> 
>> 
>> -----------------------------------------------
>> Neal Caidin
>> 
>> Sakai CLE Community Coordinator
>> nealcaidin at sakaifoundation.org
>> Skype: nealkdin
>> AIM: ncaidin at aol.com
>> 
>> 
>> 
>> 
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>> 
>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
> 
> 
> 
> -- 
> Cheers,
> Branden
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> 
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"