Qase.io is growing. At the moment there are more than 1000 registered teams from 70 countries. Some of these teams are small, some of them are big. Many of them include developers, product managers, analysts. And each role should have its own rules and access rights. On the previous post, I told you about team groups and roles. They are shipped and now you are able to create new roles and define access rights for them.
Also, we have added an option to grant access for specific projects. If you want to create a secret project, available only for some of your team members, you can do it.
A feature that was announced many months ago has been delivered. Now you can change the order of your test cases in a suite or move it from one suite to another.
Previously it was a real problem for users to perform these actions. To move the case from one suite to another, you ought to:
- Go to “edit” page for a specific test case.
- Choose a proper suite from a dropdown menu.
- Click “Save” button
Now, you can do that with one single mouse move.
The main challenge was to make it work rather smooth with big test case repositories (1000+ test cases). We have tested the current solution on a project with 1700 test cases and it works well, but not perfect. We will continue improving it.
A feature that can save a lot of time. In fact, I don’t understand why haven’t we added it from the beginning. Now you can make a sketch of your test model by adding new test cases in seconds. After it is ready, you can proceed by setting up test case params like severity, priority, steps and etc.
Test suite clone feature
Previously, we have added an option to clone the test case. It helps to save time if you have a lot of similar test cases in your project. Now, you can clone the whole test suite with test cases and include children suites with its content.
A feature that became very popular extremely fast. A lot of users asked us to add PDF export along with CSV/XML/JSON/XLSX formats.
YouTrack is a very popular issue tracker and is used widely by different companies. We’ve added an integration as Jira has.
How does it work? To setup integration with YouTrack, you need to obtain an API key first with YouTrack scope.
After that, you will be able to send defects to YouTrack — new issues will be created automatically.
Here is a quick guide on how to get the permanent token: https://www.jetbrains.com/help/youtrack/standalone/Manage-Permanent-Token.html
Another feature request from our users. In some cases, you need to postpone some test case during run and check in the end. So now, you can skip any test case in a run and turn back to it after all other open test cases are done.
Test run bulk action
It was really hard to perform actions with many test cases in the run. If you wanted to assign 30 open test cases in a run to another person in your team, you should have clicked 30 times to open a menu and do 30 clicks for assignment. Now, with bulk edit, this can be done easily.
At the moment, there are three bulk operations available:
- Assign to me
It works good, so we are going to add bulk actions for other pages: bulk test case update, milestones, shared steps, defects, test plans, and test runs.
What is next?
A key feature for Behaviour-Driven Development. We are going to add a simple way to write test documentation for your product at first.
API is a must-have feature for all test case management solutions. It allows to retrieve test model with test cases, suites and test plans, start new test runs and add results for them. Development has started and we are going to show it very soon.
Qase is growing and along with users, operational costs are growing too. So now, we are focused on launching the “Business” plan and features that will be included in it. So here are our roadmap:
Custom fields for test cases
I think that it is impossible to find two identical workflows in different companies. Each team adopts the tool they use for their needs and development process. At the moment, Qase is not so flexible. We have a predefined list of fields for test cases, suites, milestones and etc.
Custom fields will allow you to add new fields, set them as required or not and use them in test runs.
Test case review
For many development teams, code review is a common process. It allows to decrease the number of mistakes and learn the best coding practices. So we have decided a similar tool in the test case management system for our users: test case review feature. You will be able to send changes made to test case for review. Your teammates will be able to review this changes, approve them, or decline. Or write comments and send it to rework. It is an option to increase the quality of your quality assurance process.
Detailed statistics and analytics
Nowadays, data is the key that helps to learn and grow. It is very important to collect information about processes, product, customer behaviour, analyze it and perform some actions.
Qase is a tool, that is used every day by people to make their work. And we should add a possibility for them to know how their processes are working and what problems with the product they have (and how often).