I would really like to put my voice in on this request as well. We have desire to execute test cases not only against a certain enviornment, but for example in various operating systems. It does not make sense in our orgainzation to clone to test case to be OS specific, but rather tag the execution against the OS. Please add this field, or option for a customizable field or two :)
In a real simple sense, you could use the "Name" field of the Execution set to codify the OS/Version etc. Help me out in how you would want us to add fields. For exmaple, is this OS choice a prefilled JIRA field like component? Or is it just another text box where you type stuff in? How would you build it?
The project we are working on is for an iOS application. We currently have around 600 test cases, and that is quite enough for us to manage as is right now. If we were to use a custom JIRA field like compoent we would need to have multiple simmilar test issues which only vary for this field. So for sure we want to use execution to hold these fields/variables Build, Enviornment, Browser, OS, platform, etc.
Previously our test case management would allow us to define a complex enviornment for where the test was run. Windows7+IE9, or Mac OSx Lion+Chrome or iPad+iOS 5 etc. So we don't want to tag this information on the test case itself.
We 'could' use the Name of the Execution to help us seperate these things, but the names are getting too complicated because we are trying to jam a number of these fields into the name. Complicated by the outstanding issue of putting a ... and hiding most of the title anyways :)
Also we 'could' use the Enviornment and make this a complex field and jam in enviornment+browser+OS, but this just feels dirty. Maybe that's the prior DBA in me and the itch for data normalization.
What we envision is just like what you have in place for Enviornment now on the create or edit of the test cycle. Enviornment fits PERFECTLY, we use it a lot. Right next to that we could also use "OS" or Operating system.
Obviously need to take in some ballance here as it could start to be a drag to create cycles and it could be a pain to fill in 20 things each time.
If I were to build this, maybe I would have 4 available fields. Cycle_Data A-D for example. The label for those could be defined from the plugin admin page and given a simple tile that works for that organization. Or if possible, ideally ustomizable per project rather than the plugin which is global.
We're looking for participants for a workshop at Atlassian! We need Jira admins who have interesting custom workflows, issue views, or boards. Think you have a story to sha...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG