Hello Katalians! Time flies when you ’ re busy creating awing products! Back in May, we present, which included features to provide best scalability options and a better user experience. & nbsp;

And because we are not in the business of keeping you waiting for the up-to-the-minute and superlative, today, we are excited to denote the release ofKatalon Studio 8.1 (KS8.1). This release comes jam-packed with a all-encompassing set of new features as well as scads of improvements and fixes to continue providing you with a top-notch testing experience. Read on to memorize more about what ’ s included in this release.

What ’ s New?

Studio 8.1 delivers features that aim to increase the resource and cost-efficiency of your mechanisation cycle, provide best integration with Azure Test Plans, and enhance mechanisms to tackle test flakiness. & nbsp;

Improved retry failed executions immediately to spot flaky tests & nbsp;

A flakey test is a test that will pass or fail regardless of the changes done to the fundamental code. Test flakiness is get by matter with new code, extraneous element like incorrect substructure setup or network glitch, or an issue with the examination itself. The treacherous nature of test results give by flaky tests is a never-ending war and it represents one of the most important challenges in the exam automation manufacture because, without accurate answer, DevOps teams can ’ t make accurate decisions about their product freeing.

To harness test daftness, developers rely on the following steps:

1. Identify the off-the-wall Test Case
2. Troubleshoot the cause
3. Edit and improve the Test Case accordingly

Katalon Studio users have multiple options to tackle exam flakiness: they can retry all Test Cases when the Test Suite finishes; rehear merely failed Test Cases when the Test Suite finishes, or rehear a failed Test Case immediately after its first failure. The latter is by far the most democratic option among Katalon Studio Enterprise users. & nbsp;

At Katalon we understand how important it is for developers to be able to create data-driven decisions. In this liberation of Katalon Studio, we have improved the logic of our reportage mechanisms so they are more levelheaded and intuitive to provide better insights on test results. Studio 8.1 groups all executions into one story and makes it much easier to find discrepant effect or mistaken positives. & nbsp;

Additionally, we have raise our test result third-party integrations with tools like TestOps and qTest so the report shows only one last set of results rather than multiple sets of result for each test case. This feature allows users to well place failed or passed examination results faster.

To hear more about the reporting enhancements included in this release, check out thefor Katalon Studio.

Less execution wait-time with Terminate Execution Conditionally & nbsp;

SUSA automates exploratory testing with persona-driven behavior, catching bugs that scripted automation misses.

One of the benefits of test mechanisation is the ability to test early, often, and anywhere in the development cycle. In Studio 8.1 we leveled up these benefits by allowing exploiter to stop Test Cases when they find an issue betimes in the cycle by establishing a failure tolerance threshold. & nbsp;

This new feature permit users to terminate the Test Case or Test Suite Collection execution when there is a substantial bit of test suit in an executing that has failed, enabling them to provide feedback originally in the cycle rather than waiting until the test rhythm is completed. Failure limen will help make more efficient use of testing device and amend savings on infrastructure costs, especially for cloud user.

To leverage this feature we receive included a new command pick,-maxFailedTests= & lt; T & gt;, where T is the maximum number of failed executions allowed before the examination is stopped. Once the Test Execution block, Katalon Studio will generate the report control all the insights. This feature is only uncommitted for test accomplish through the CLI or CI using the runtime engine.

To learn more about how to leverage this feature in your examination environment, check out the Katalon Studio 8.1.

Azure Test Plans desegregation

Building on the promise to always supply the best integration with your existing testing platform, Studio 8.1 delivers a better way for user to map Studio exam results to release views in Azure Test Plans.

In Azure DevOps users have the ability to get a full position of the quality of a release, include passed and failed tests as well as the number of runs. Studio ’ s enhanced desegregation with Azure Test Plans include a new parameter, “ Release Definition ID, ” which can be habituate to map test results with releases in Azure DevOps. & nbsp;

Starting in Studio 8.1, users can enable this feature from the Project Settings menu and add a numerical ID to the “ Release Definition ID ” parameter. Alternatively, testers can use the new command option “ –info-adoReleaseDefID= & lt; DefinitionID & gt; ” and based on the specify Definition ID and its point, pass them to the Test Run property on Azure DevOps.

Tidbits & nbsp;

• Enhanced Kobiton integration:Mobile test mechanisation keeps getting better! Starting in Studio 8.1, users will be able to customize the remote host protocol and device gens in Kobiton to amend their testing experience. See ourto learn more. & nbsp;
• New built-in keyword for conditional waiting: Studio 8.1 introduces a new keyword “ waitForElementNotPresent ” for mobile testing, allowing users to set conditional waiting when fulfill the test script. This feature drastically cuts down on the execution clip of the mechanisation suite while also preventing flaky tests. Seefor more item.
• New APIs for plug-in development:In this release, Katalon Studio providesto offer imagination for. These APIs are apportion to plugins that have access to the JRE location, Running mode (IDE or Katalon Runtime Engine), Test Suite/Test Suite Collection, and JUnit report localization via the plugin platform. & nbsp;

Wrapping Up

We are thrilled about Studio 8.1 and we hope you are too. We promote you to download Studio 8.1 to start lead advantage of its many new feature and improvements. & nbsp;

For a complete listing of new feature, improvements, and fixes, please visit the. As always, please post any questions, ideas or concern on our, we are eager to hear from you.

Trigger modal