[Building Sakai] Test plans in Jira

Adam Marshall adam.marshall at it.ox.ac.uk
Thu Jul 11 05:57:14 PDT 2013


I agree that there should be a separate test plan field, we do this at Oxford and it's a boon. Putting the reproducibility info in the description also sounds good.

Adam

Sent from my iPad

On 11 Jul 2013, at 13:41, "Neal Caidin" <neal.caidin at apereo.org> wrote:

> [qa and dev]
> 
> Hi All,
> 
> I wanted to get some feedback on Jira. For at least some of the projects (SAK and KNL, maybe others) we have a Test Plan field, but it gets used sporadically. Unfortunately, Test Plans themselves are often not included for issues needing testing. But this conversation is based on the idea that if we did add Test Plans consistently, what is the best way to do that.
> 
> Also, it seems to me that we also need steps to reproduce an issue. I find that I often try reproducing an issue before testing a fix, at least in part to make sure I have a proper understanding of the problem. Steps to reproduce an issue should be included in the Jira.
> 
> If you are not familiar with the Test Plan field in Jira, I've enclosed a couple of screenshots. One shows where the Test Plan field is located, which is in the Edit Issue dialog. The other screen shot (from a different issue) shows the display of the Test Plan field, once it has content filled in from the Edit Issue dialog. The Test Plan field displays two tabs, General (for some general fields like Merge flag), and Test Plan itself. It appears above the Description field.
> 
> My questions:
> 
> * Does everyone agree that it would be helpful to include both the steps to reproduce an issue (on initial Jira submission) and the Test Plan (at least by the time the issue has been resolved) ?
> 
> * Does everyone agree that the steps to reproduce an issue should be in the Description field?
> 
> * Should we use the Test Plan field? Or should the Test Plan go into the Description field?
> 
> Pros of Test Plan field
> ---------------------------------
> * Nice organization. Easy to find the Test Plan separately. More readable.
> 
> Cons of Test Plan field
> ------------------------------------
> * May be harder to find initially to fill in. Requires extra clicks (not on the main issue screen until after field filled in)
> * Not consistently available across all projects (this can be fixed)
> 
> 
> Cheers,
> Neal Caidin
> 
> Sakai CLE Community Coordinator
> Apereo Foundation
> 
> Skype id: nealkdin
> 
> 
> 
> 
> <add_test_plan.png><test_plan_display.png>
> _______________________________________________
> 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"
-------------- next part --------------
A non-text attachment was scrubbed...
Name: add_test_plan.png
Type: image/png
Size: 186343 bytes
Desc: add_test_plan.png
Url : http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130711/907b986e/attachment.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: test_plan_display.png
Type: image/png
Size: 100264 bytes
Desc: test_plan_display.png
Url : http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130711/907b986e/attachment-0001.png 


More information about the sakai-dev mailing list