Strategy of using Jira with tools for automated testing



  • I'd like to verify my idea of setting up test architecture in projects managed by Jira.

    Jira itself does not provide tools for unit or functional testing, but it has different plugins to manage testing and some for managing automated testing, e.g. TestFLO Automation - can run autometed tests and save their results (JUnit format) as Jira issues.

    So the sequence of steps to define test automation architecture in Jira would be as follows:

    1. Define test automation frameworks/software which could be used with your product.
    2. Check their integration with Jira with usage of Jira plugins.
    3. Select sets testing frameworks/software -- Jira plugin that best suits your needs.

    Is this strategy right? Or is there any other strategy?


    UPDATE (2018.05.04):

    Actual sequence of steps was:

    Precondition: We know that we should use Jira to track bugs & manage tasks

    1. Define test-automation tools (we decided to use: + + + )
    2. Then we had to select test management tool (Jira plugin or stand-alone app) which could be integrated with Jira & autotests. We chose for some reasons, and use its API to integrate with autotest (pass results from autotests to testrail)


  • This is what I had implemented for one of my clients. Automation Framework: This was developed using QTP and HP Load Runner.

    Test Management Tool: HP QC was used for test management, test case repository, Single Point of Reporting, Release management and Defect Management.

    Integration between Jira and HP QC: There are several bridge apps/servers available but in our case we used Tasktop. You can find more details on all the tools in https://marketplace.atlassian.com. Also we integrated Bugzila

    What was achieved: The tester was able to execute a test case i.e. trigger the automated test to run from QC. The actual script used to run on QTP systems and results were directly updated on QC on completion whether it had failed or passed. Even mails were triggered on completion. On failure the tester used to analyse the logs captured and stored and log a defect on QC. We had clearly defined filters and fields on QC and depending on which fields were chosen by the tester it used to trigger a task/issue creation on Jira And OR defect on Bugzila (depending on the nature of the bug or impacted component as we were dealing in a multi vendor environment, where different vendors and teams were responsible for testing, using different defect tracking tools). We had implemented multiway communication which could be triggered either from Jira, Bugzila or QC but at the end restricted it to trigger from QC only via testers and other activities were taken care manually.

    Hope this will provide an idea and help you. All the best!



Suggested Topics

  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2