Allure TestOps getting started

Where to start?

Depending on who you are in the team and on the life cycle of Allure TestOps in your infrastructure we recommend different paths for you to follow:

Deployment path

So, here is the plan:

  1. Installation
  2. Integration with 3rd parties, including…
    • Integrations to run jobs on CI
    • Integrations to gather test results from CI
    • Integrations to transfer test results to bug/issue tracking systems
  3. Configuration, including…
    • Manage users and groups
    • Manage projects
  4. Using Allure TestOps

Item #2 can be omitted at this stage or switched with #3 if you don’t need to import and export the test data.

Installation

Task: Install and commission Allure TestOps

Target audience

  • DevOps
  • savvy QA guy which will make initial setup of Allure TestOps
  • your boss told you to do it
  • all from above

Actions to be performed

On this stage of Allure TestOps deployment you need to perform the following tasks:

Expected outcome

  • You’ve assigned HW server or VM for Allure TestOps.
  • You’ve got the binaries of Allure TestOps.
  • You’ve performed the installation of Allure TestOps on designated server.
  • You’ve got Allure TestOps up and running.
  • You’ve integrated Allure TestOps with a storage of your choice, data base and/or (or not) LDAP.

Integration with 3rd parties

Say, you’ve got Allure TestOps working. Allure TestOps is not an isolated system - it allows you to managing your test data (produce, import and process and export) by communicating with the 3rd party systems such as CI and bug/issue tracking systems.

So, the whole cycle could be managed by Allure TestOps as per figure bellow:

Integrations with 3rd parties

This section covers the following information:

  • Integration of Allure TestOps with CI to manage the test runs (run the build jobs)
  • Integration of Allure TestOps with CI to import test results from CI
  • Integration of Allure TestOps with bug/issue tracking systems to export test data

Task: integration with 3rd party solutions

  • Integrate with CI systems.
  • Integrate with bug/issue tracking.

Target audience

  • DevOps
  • savvy QA guy which will make the configuration of Allure TestOps
  • your boss told you to do so
  • all from above

Actions to be performed

  • Integration of Allure TestOps with CI
    • Integrations to run tests on CIs
    • Integration to import test results from CIs
  • Integration with Issue/Bug tracking systems
    • Integration with bug tracking to export test results

Expected outcome

  • You should be able to run build jobs on CI
  • You should be able to import the test results to Allure TestOps from a CI system
  • You should be able to export the test results to bug/issue tracking system

Let’s start integrations

Please proceed to dedicated Integration section to perform all the integrations you need.

Configuration

Now, we need to allow your team to access the system to start working on projects.

Task: users and groups configuration of Allure TestOps

  • You need to add users to the system.
  • You need to create groups.
  • You need to grant projects access rights to your team
    • on individual level
    • on group level

Target audience

  • QA lead (with admin rights)
  • savvy QA guy (with admin rights)
  • your boss told you to do so (and gave you admin rights)
  • all from above

Actions to be performed

On this stage you need to perform the following steps:

Using Allure TestOps

Target audience

  • QA, TA engineers.
  • QA Leaders.
  • Administrative staff: product managers, owners, project managers
  • Executives

You are QA engineer and you need to create and run tests and build results

If you are ready to start creating your tests, test plans and so on, please refer to the following sections:

  • Test cases management
    • Test cases
    • Test plans
    • Tests grouping
    • Project settings customisations
    • Users management
    • Mapping environment variables (no one does it, but we do)
  • Tests launches
    • Manual test runs
    • Run jobs on CI systems
  • Import of test results
  • Export of test results
  • Reporting
    • Reports
    • Dashboards
    • Query language
  • Support, if nothing above helped