Why does Testersuite have bi-weekly release?

Why release biweekly?

Testersuite has been evolving for more than thirteen years. The world of software testing is constantly changing. So does software development, legislation, customer needs, etc.. This is why Testersuite has a release cycle of two weeks. This means that every two weeks we update our application with new functionality, performance improvements, bug fixes, security updates, and much more.

In doing so, we deliberately chose a two-week cycle at the time. In this way we remain current, flexible and do not confront Testersuite users with too many changes at once. After all, humans remain creatures of habit.

What does this really mean for our users? To answer this question, we do a small sampling of some recent releases below.

Linking to Azure DevOps

From Testersuite users, the wish to link with Azure DevOps has been expressed regularly. We have responded to this wish with a release in September. The out-of-the-box link between Testersuite and Azure DevOps makes it possible to transfer defects to Azure DevOps. This allows testers in Testersuite to capturedefects and developers in Azure Devops to resolve the defects .

Setting test cases to OK at once

‍Anotherdesire of Testersuite users is to have fewer clicks when executing test cases in test runs. When a test case has many test steps then it can be quite a lot of work to go through all the steps. This is of course best but not always necessary. In one release we made it possible to set test cases to OK at once without executing the individual test steps.

Run test run blocking until start date

It frequently happens that a test run is performed by testers, before the scheduled start date. This need not be a problem. However, often you want to prevent this as test coordinator for planning reasons, or just to keep the overview. As of this release, you can set per test run whether the test run may be executed before the start date is reached, or not.

Add text as a comment to mail defect/requirement

When you manually send a requirement or defect by email from Testersuite, it is now possible to save the message of the email as a comment to the corresponding section. This keeps any important information from the email, and keeps the history complete. The option is located in the popup that appears when manually emailing a requirement or defect.

Hiding requirements in the product tree

A much requested option for the product tree is being able to turn requirements on and off. This has been realized in this release. If only the products need to be visible within the tree, select this the option in the new menu next to the product tree.

Comment syncing between Testersuite & Azure DevOps

As of this release, 'comments' are also kept neatly in sync between a defect in Testersuite and the work item in Azure DevOps. When a defect is transferred from Testersuite to Azure DevOps, and when comments are added to either side, they are synchronized between the two systems.

Want to know more?

Of course, the above is a small sample of recent releases in recent months. As a Testersuite user, you can find all information about the latest releases in the help documentation.

Are you not yet a Testersuite user and would like to learn more about Testersuite? Feel free to schedule a no-obligation consultation or no-obligation demo with us.