Today, we are happy to announce the start of open beta testing of Qase.io. From now, registration is open and available for everyone. Try Qase for free.
A lot of things were changed since our previous update and we have made a good progress to make our product usable and useful.
After several attempts to solve some UX problems (like navigation, blocks placement and etc.) we’ve decided to start from scratch and completely rework the layout of the application.
We’ve moved top menu and submenu to the sidebar. That allowed us to make work area fluid (instead of fixed width in previous versions).
Another significant visual change is layers. They help you to focus on the specific elements on the page.
All other components were adjusted to fit new design:
We hope, that all these changes will help you to stay focused on work you do using Qase.io.
Test case revisions
As we’ve mentioned in the previous post, there is an important feature, that should be done as soon as possible: test case version control system.
How does it work?
- Open test case edit page
- Change some value (i.e. Preconditions).
- The system will calculate diff between current test case state and new state and save only modified fields.
- This diff will be saved as a revision to the database.
Why do we need revisions? For several reasons:
- Show change history for any suite and test case
- Easily revert any harmful changes
- Bind test case state for a test run
- Avoid overwriting test case field values during simultaneous editing by several people
The most popular request from alpha testers: make import feature to migrate test cases from other systems.
Test plans & runs
Composing test plans and test run wizard.
This feature, that is an industry standard. This integration should allow creating issues based on defects found during the test run and link them.