On this page, the tester will learn how to cover requirements with tests, how to organize and execute them with TestFLO.
You can try out almost everything described below yourself on our Live Demo Environment (login/pass: testflo).
After the QA manager sets up one or more TestFLO projects, it is time to cover requirements with tests. This means you will be creating Test Case Templates and filling them with steps.
Creating Test Case Templates linked to a requirement can be done in many ways, for example:
The first method, starting from requirements, is illustrated below:
If the Test Case Template create dialog contains too many fields you do not need, then contact your Jira Administrator to configure this screen to suit your needs.
After creating Test Case Templates, you may want to organize them in the Test Repository by creating folders and using drag and drop to place Test Case Templates in the folders. This will make creating Test Plans from the folders much easier.
One Test Case Tempalte can belong to many folders, and TestFLO provides JQL functions to enable searching for Test Case Templates that belong to specified folders. It’s up to you to decide what the folders mean. Some choose to use them to represent versions of the application that they are working on. Others organize their Test Repository by test categories, f.e. integration tests, smoke tests, etc. Some use them to represent test sets. Others use a mixed approach or one customized to their specific case. Use whatever makes sense to your team and workflow.
At this point, the person responsible for creating the Test Plan should do their part. This step is covered in the Quick guide for the QA manager.
The columns in the Test Cases panel can be modified in TestFLO global settings accessible by your Jira administrator. In the future, TestFLO will enable testers to personalize the columns themselves.
You can add comments to the steps, add screenshots or upload error logs attached to particular steps or the whole Test Case.
The expanded arrows just a little above enlarge the Steps table for your convenience. If you would like the Steps table to contain a different set of columns, contact your Jira administrator.
All elements described above cover the basics, but TestFLO has many more interesting functionalities and configuration possibilities. For more information about the day-to-day use of TestFLO, read the full User’s Guide section of this documentation. To learn about all configuration possibilities that TestFLO offers, go through the Admin’s Guide section of TestFLO’s documentation.
Contact your QA manager or Jira administrator if you’d like to:
If you can’t find the answer you need in our documentation, raise a support request.