What's new in v8.1.0?
August 18th, 2021
We are excited to announce Katalon Studio version 8.1.0 is now available for download from the Katalon website.
Version 8.1.0 is a major release packed with features and enhancements aimed at more efficient and effective test maintenance. We focused on improving the Retry Immediately mechanism and allowing users to stop execution based on the maximum number of test failures permitted in a single run. While the former assists users in detecting test flakiness, the latter considerably reduces the time spent waiting for the entire execution to complete, resulting in lower testing environment costs. A better experience in mobile testing and Azure DevOps integration was also an up-and-coming improvement in this release.
Along with these significant changes, we've made adjustments to our UI on macOS Big Sur, as well as to Report and 3rd-party integration that you should check out. See our Release Notes for details on the modifications made to previous versions. Read on to find out more detailed information on the new features and improvements we've prepared for you.
Tackling test flakiness with Effective Retry Immediately mechanism
A flaky test is a test that occasionally fails but finally passes if you attempt it enough times. It lowers test confidence and, as a result, trust is eroded. It not only irritates stakeholders, developers, and testers but also causes everyone to question the process. As a consequence, flakiness becomes an outgoing problem that needs to be tackled. Addressing this issue requires testers and developers to identify which and why tests are flaky and then remedy them accordingly.
The first step to combat test flakiness is to identify it. In version 8.1.0, we've addressed this by applying a new logic to our Retry Failed Executions Immediately function. The changed function now consolidates retried test case execution logs into one report so that you can identify flaky tests at a glance. Wonder how it works? See Retry Failed Execution Immediately.
Terminating Execution Conditionally
Many users believe in a fail-fast system while running tests. In other words, the shorter your feedback loop, the faster you move forward. Furthermore, if your team uses cloud devices, computers, or cloud services, test run times have a clear cost. Cutting test runs short when a significant number of tests fail and detecting test environment issues early can mean a lot of saved time and money.
This is especially true with a mature set of tests, which can take hours to execute to completion. By creating a condition to automatically end tests early when a high number of tests fail, you can eliminate failures with a clear root cause, such as failures related to test configuration, setup, infrastructure, or network, without the wasted hours... and potential frustration.
For individuals who don't want to miss any issues discovered in a single run, this feature may not be compelling. It hinders the test execution from identifying more issues.
We are happy to announce you can kiss those hours of wasted waiting goodbye. From version 8.1.0 onwards, Katalon Studio introduced the utility to terminate execution conditionally by defining the failures threshold via the command line. See Terminate Execution Conditionally for more details.
Configure in Command Builder
Execute in Console Mode
Improving Mobile testing
Better Kobiton Integration
When it comes to mobile testing, integration between Kobiton and Katalon Studio serves as an essential chain to execute automated tests from Katalon Studio on Kobiton devices. This was made easier in version 8.1.0: you can now customize the remote server protocol and device name in Kobiton for a clearer testing experience. See Mobile testing with Kobiton devices.
New built-in keyword for conditional waiting
Conditional waiting keywords is a modern solution that goes beyond Record-and-playback. It has proven to be a reliable, must-have feature for low-code automation testing tools. Conditional waiting ensure scripts do not blindly wait x number of seconds before continuing to the next step; instead, they wait until a condition is true and proceed as soon as possible. This drastically cuts down on the execution time of the testing suite while also preventing flaky tests. In version 8.1.0, we continue to expand our keyword vocabulary with
waitForElementNotPresent for Mobile testing. See [Mobile] Wait For Element Not Present.
Newly supported browser versions
Chrome 92 and Microsoft Edge (Chromium) 92.
Azure DevOps enhancement - Submit Release Information together with Test Run
We know that teams sometimes juggle multiple pipelines for different jobs. This can make obtaining reports of an automated test that still reflect the specific job and its quality a challenge. Currently, Azure Test Plans enables users to view the quality of a build or a release, while Katalon Studio already provides build information to Azure DevOps. With version 8.1.0 onwards, users can also submit the release information with their test run, including Release Version and Release Stage. See Configure the Integration with Azure DevOps Test Plans.
New APIs for Plugin platform
- JRE location
- Running mode (IDE or Katalon Runtime Engine)
- Test Suite/ Test Suite Collection JUnit report location (via the plugin platform)
We hope you will enjoy these changes, and look forward to offering you more improvements in the next release. Test away!