Scroll to top
en pl

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


Boguslaw Osuch - 6 November 2017 - 0 comments

This article is a continuation of the previous part where I examined the basics of setting up and launching TestFLO.

Requirement

If you click on the requirement, you’ll get the following screen.

Tests Under Execution shows all the Test Cases that are linked to that requirement.

In Test Progress section you’ll see all your Test Plans that are linked to the requirement. The section displays the status of the Test Plan and other critical data. One glance is enough to check the general progress of testing.

Coverage shows what kinds of tests were designed for that requirement. Even if you create 10 Test Cases on the basis of one template, the coverage section will display only one item, helping test managers to quickly assess their Test Case Templates.

Test Case Template

If you head over to the Test Case Template, you’ll see a new section when scrolling down the issue screen.

That section is called Test Progress, and it displays all the executable test instances that were created on the basis of this template. The information about the number of failed and passed test cases is very valuable in this context.

 

There are also a couple of new things users can do here.

Click on the drop-down menu More to see them:

  • Link with Requirement – you don’t need to start with creating a requirement for your Test Case Templates. This functionality allows to connect a given Test Case Template with a requirement that has been previously created and added to the system.
  • Add to existing Test Plan – this options allows to create a Test Case that will be automatically added to a previously created Test Plan. If you need to quickly add a Test Case based on that template to one of your Test Plans, this functionality is for you.
  • Update Test Case – many of our clients agree that this functionality is very useful in designing their test processes. If something changes in the system and testing needs to be updated, you’ll also need to update all your Test Cases that haven’t been executed yet, but that you’ve got ready in your Test Plans. Test Cases that have been executed can’t be updated. The functionality enables users to update selected Test Cases on the basis of their status.

Test Plan

If you go back the the Test Plan, you’ll see the following screen.

The section Test Cases lists all the tests. Our Test Case ‘User can add a new client’ is now marked as Passed. The next column refers to the defects linked with that Test Case.

Note that the Test Information Section displays all essential data about the progress of your tests on the basis of the executed Test Cases. In our case, it lists one test executed and passed.

You’ll also see a different list of Actions.

 

Here’s how these actions help to boost the productivity of your test management:

  • Copy Test Plan – that’s a smart action from the business standpoint because it allows for regression testing.
  • Create Test Cases – that option allows to create new Test Cases on the basis of Test Case Templates users can pick from the list on the pop-up screen.
  • Link with Requirement – if you created the Test Plan without linking it to a requirement, you can do that here.
  • Update Test Cases – if something changes in the testing process and you need to update your Test Cases, that’s the right option. Choosing this functionality, you can be sure that all the Test Cases that are part of that Test Plan and haven’t been executed will be updated to reflect the change in the system.
  • Snapshots – this functionality is a bit more advanced and relies on a specialized post-function. Have a look at this page in TestFLO documentation to learn more about that option.

TestFLO & Jira

I hope that this guide helped you to better understand how TestFLO works and what it can do to boost test management at your organization.

If you need a tool that helps testing teams to

  • create a functional repository of test cases;
  • track test changes;
  • benefit from smart and  easy reporting;
  • and quickly create Test Cases (including ad hoc creation);

TestFLO is a perfect solution for your organization.

If you’d like to learn more about the features included in TestFLO, read this detailed article.

TestFLO offers a lot of configuration flexibility in designing your test processes directly in Jira. You can see how the plugin works in practice in this case study from Bogdan Gorka, a leading PMO consultant and Jira expert who explains how he uses TestFLO to support test management in SAP projects.

Have you got any questions about test management in Jira? Reach out to me in comments or drop me a line, I’ll be happy to help you out.

Related posts