Scroll to top
en pl

Step-by-step guide to launching TestFLO – 1/2


Boguslaw Osuch - 18 October 2017 - 0 comments

TestFLO was a plugin designed to improve the powerful functionalities of Jira for test management. If you’re still not sure why your Jira instance could serve as a productive testing environment, have a look at this post I wrote about the basics of test management in Jira. If you’ve already installed our dedicated plugin TestFLO, you’re ready to make your Jira into a fantastic test management environment.

Here’s a step-by-step guide to configuring and launching TestFLO.

CONFIGURING TESTFLO

To launch TestFLO in your project, you need to head over to Jira Administration and click on Projects. Now choose your project from the list.

You’ll get this screen.

Pick Test Management in the left-hand menu. The screen displays three different modules that relate to test management in your project:

  • Test Repository
  • Test Execution
  • Requirements

If you’d like your project to contain only a test repository, you can enable just this module and assign test execution and requirements to another project.

Moreover, you can pick the individual elements in each module to be enabled in your project. Activating one element might sometimes require the activation of another one. For example, if you’d like to enable Steps / Test Scenario Field for your project, you should first activate Issue Types & Workflows.

All elements are described for your convenience so you don’t need to consult the product’s documentation.

The easiest way to configure TestFLO is to enable all three modules for a single project. If you active the entire module, you can be sure that all the required elements included in it will be automatically activated as well. Unfold every drop down list here – you’ll find optional elements that you can activate manually.

Here’s an example.

 

In the screen above, the user activated the Test Execution module. As you can see, elements such as Additional TP Issue Types or Steps Progress Field were left inactive. These elements are optional.

When activating the module Requirements, you’ll get a screen where you need to choose the issue types that will serve as requirements and defects for your testing. TestFLO doesn’t introduce any new issue types here but relies on those already available in Jira.

GLOBAL CONFIGURATION

If you’d like to change global configuration of TestFLO that will provide the plugin’s testing functionalities to all your projects, head over to the Add-ons section. You should see TestFLO in your left-hand menu. Click on Configuration and you’ll get this screen.

 

LET’S SEE TESTFLO IN ACTION!

We’ll start by creating a new issue – in our example, it’s about adding a new client.

 

Note that this issue type is Task. When configuring the plugin, we set Task issue type to serve as requirement for our testing.

Thanks to that setup, we now get the following options in the drop-down menu More.

 

Now we can create a Test Case Template.

That issue type is a template that helps to create numerous executable test instances in the future.

When creating a Test Case Template, you can include Test Steps by adding new rows to the table.

The Test Case Template looks like a regular Jira issue, but remember that it’s not executable. That’s why you shouldn’t change anything here. The only thing you can do is switch the status of this issue from active to inactive.

NOW WE’RE READY TO CREATE A TEST PLAN

Open the drop-down More menu and click on Create TP with TCs. To create a new Test Plan for a given requirement, you also need to choose the project for that Test Plan.

That’s how the Test Plan screen looks like.

 

You can see to which requirement it refers and check the complete list of all executable Test Cases that were created from the Test Case Template related to the requirement.

If you click on the one of the previously created Test Cases, you’ll see that in the Test Steps section it now includes a new column – Status. That’s where users can easily change the status of every step included in the test plan to In Progress, Passed, or Failed.
Have a look here for a detailed step-by-step guide to creating a Test Plan in TestFLO.

Now look to the right side of the column. The section Test Information displays everything users need to know about the progress of their tests: the number of waiting test steps, executed test steps, as well as passed and failed test steps.

 

You’ll find that panel on several issue types in TestFLO. In Test Cases, the section shows testing information and allows users to take some actions:

  • Create defect for TT-1 – picking this option allows to create a bug related to the Test Case. The bug will be displayed on the Test Case screen, but also below the Test Information Section, in a sub-section called Bugs where you’ll see the name of the bug together with its status. That defect will be automatically connected with the requirement TT-1.
  • Link with Requirement – thanks to this option, you can link your Test Case to an existing requirement.

How will this Test Case be displayed now in other areas of our testing?
Read the second part of the article to find out more about the functionalities of TestFLO for test management.

Related posts