Automate testing of issue creation

[Nilan (AC3)]

I am using Automation for Jira for calling some rest services.  Can you recommend how to automate creation of issues for testing?  Can I use a UI automation tool like Selenium?  Can I create issues using the API?

[Victor Seger · Accepted solution]

Hi Nilan,

I'm Victor from Automation for JIRA Support Team.

There's some different ways of doing that, but you can use Automation for JIRA itself to make this tests.

You'd like to have a rule for creating issues that might look like this:

With this rule, you'll be able of creating a few issues whenever you click on the "Run rule" button on the upper right side of your rule screen.

Note: You might disable this rule whenever you're done with your testings to avoid it keep creating issues on a daily basis.

And, to make this trigger your other rule, you might need to enable the following checkbox on your "Rule Details" screen:

This will allow all of your "Create issue" actions to trigger the rule you want to test.

Hope it helps!

Please let me know if you got any further questions.

Cheers,

Victor (Automation for JIRA)

[Pete Dunham · Accepted solution]

in that case:

would evaluate the following options:

(1) csv import (from excel) - if you are capturing testing in flight and are only going to do it once.  If you are creating fresh -skip the excel and just do the work and create the issues 

(2) clone as a template - if you have a repeated framework of say a parent task and many sub tasks and you are doing less than a few dozens times. This is have a master template issue you clone with or without subtasks

(3) Cloud REST API - if you have parameterized methods/recipes to create testing issues and this is going to be repeated and live-on. 

I've used 3 and I have used Selenium. IMHO Selenium is going to be overkill for anything that #3 can solve. There is a more complexity in Selenium with same potential output as #3.

Some thoughts on the options

(1) This option makes sense if a one done and there.  That is, if there is just several hours of work that needs to be done for test planning (we haven't been able to automated this work away on our team)

(2) This makes sense if test setup is very repeatable with only a few small changes to the testing and only one or two people need to be trained 

(3) is nice but the upfront work means it is worthwhile only if it needed for an ongoing basis with strong processes and parameters to drive creation 

Good luck!

p.s. If this is the first testing pass it might be worth keeping in mind a data model in the future that suits your needs.  For instance if you are test a requirement your data model might be: Requirement links to Test Case (a generic test script to follow with variable inputs) that links or has subtasks of a Test Run (captures test result of Test Case).

[Pete Dunham]

I am removing my last post because my response was not related to Automation for Jira. Apologies and good luck.

[Nilan (AC3)]

I don't think the question is specific to Automation for Jira.  I just need to create issues and comments.  Those will trigger automation for Jira.