During the last few months, we’ve been busy working on TestFLO 5.0 and finally released it on the Atlassian Marketplace. We are excited to publish this new version because we put a lot of effort into revamping it and solving some of the most problematic areas. It’s easily the biggest update of our app since some time.
What is TestFLO 5.0 really about?
It may look similar at first glance, but don’t be fooled. Here’s everything you need to know about our app – what has changed and what’s coming your way in the future!
We were always aware that TestFLO wasn’t a very straightforward app. The lack of a real onboarding functionality didn’t make it easier for users to start the journey with our solution. We decided to change that and create a completely new Getting Started page that presents three simple pathways for getting into action right away.
Starting to work with TestFLO on default settings isn’t that difficult now, and its broad customization capabilities are what makes it so amazing. That’s why we added the option to Create Sample Project and give users an idea of what their test management may look like.
Another option we hand over to you now is the possibility of creating a new Jira project with TestFLO enabled by default. You don’t need to explore your project settings to get the app working. Create a project and hop into action immediately. To achieve the same goal, you can also select the TestFLO Project project type when creating a project.
Our new onboarding pathways allow applying TestFLO to your existing project as well. We understand that you may want to extend your current projects with test management functionality – and there you have it! Just select one of your projects and start testing without wasting any time on the configuration.
New project configuration
The most significant change that comes with TestFLO 5.0 is the project configuration feature. We decided to simplify this part of our app and give it a new, modern UI. We reduced the number of options to a minimum, so you won’t need to worry about every single element individually. Enabling the Test Repository or Test Execution module will give you everything you need with one click.
Another major change can be found in the Requirements module. In TestFLO 5.0 you can define project and issue type pairs to point where your requirements for certain TestFLO project will be held. This setting affects linking test items with requirements through the Requirement field and allows to set the values defined in the Requirements module only.
Moreover, we created a new module – the Defects module. This section allows defining project and issue type pairs similarly to the Requirements module. Setting those pairs will influence the Create defect operation narrowing the project/issue type selection to valid values only.
If you’re a Jira Administrator who customizes TestFLO on their own (which is great!), you might see the inconsistency warning message in the project configuration. Don’t worry about it. It doesn’t necessarily mean that something is wrong. It simply says that your configuration is different than TestFLO defaults. The “Fix” button lets you restore the default settings, but be careful when using it!
Another very important change affects access permissions to the project configuration. From now on, you don’t have to be a Jira Administrator to run the app in your project. Project administrators can manage TestFLO at project settings level too.
Enhanced Issues Picker restrictions
Due to the changes in the Requirements module, we improved the restriction mechanism for Enhanced Issues Picker custom field.
Previously you could define project and issue type lists so that every issue type selected in every project was permitted to be set in the field. In TestFLO 5.0 you can choose project and issue type pairs to allow the selection of exact issue types in given projects. That seemingly small difference gives you better control over your Enhanced Issues Picker fields.
TestFLO projects list
When you perform testing in many different projects, it might be difficult to navigate through them all. To make this task easier, we created a list of TestFLO projects. Now you can verify which TestFLO modules are enabled and where. If you are working with multiple testing projects, this list will save a lot of your time.
TestFLO 5.0 was a huge initiative for our team, and we’re really happy to release it. However, we’re also aware that it’s only the beginning of our journey. TestFLO is bound to grow, and many important changes are still ahead of us.
Next major improvements planned for our app are the test preconditions and new test steps. We received a lot of feedback from you, and we understand how important these features are to you. Furthermore, TestFLO will be enhanced with new reporting capabilities. We want to create more dedicated reports, JQL functions and custom fields, to let users measure their testing process better. TestFLO will also have a new tree structure to help you categorize and manage your tests easily.
The features mentioned above are just a part of our roadmap, and we’re planning many more exciting features. We will work hard to get your testing experience with TestFLO to the next level. Stay tuned!
- Why requirements test coverage is key to success? - 15 October 2018
- A quick guide to smoke testing - 21 August 2018
- 6 tips for efficient bug reporting - 23 July 2018
- Panel Filter Result – flexible presentation of data - 2 July 2018
- Traceability in testing – why is it so important? - 12 June 2018
- 4 interesting ways of adapting TestFLO to your testing process - 24 May 2018
- Why great leadership is so important in testing teams - 10 May 2018
- 7 features of a great testing team - 19 April 2018
- Welcome to TestFLO 5.0! - 9 April 2018
- 6 strategies to boost your testing team productivity - 22 February 2018