Fail-Fast Testing: How to Stop Test Suites Early and Save CI/CD Time

March 01, 2026 · 4 min read · Testing Guide

Blog / Insights /
Fail-Fast Testing: How to Stop Test Suites Early and Save CI/CD Time

Fail-Fast Testing: How to Stop Test Suites Early and Save CI/CD Time

Contributors Updated on

Learn with AI

Linkedin

Facebook

X (Twitter)

Mail

Learn with AI

The Fail-fast Principle in Software Testing

In software development, a fail-fast system is a tool that will notify when a failure is likely to come. The philosophy of the fail-fast principle is formed around the mind that a scheme should quit normal operations rather than trying to continue working around a blemished piece of code. & nbsp;

The fail-fast rule makes software bugs easier to detect earlier in the development cycle. It let for quicker strengthening of the codification under development, bound the turn of bug that make it into production, and reduce the intrinsic cost of letting bugs in the code.

In short, it is better to betray fast, miscarry often in the development than later when the merchandise is about to be released.

One of theis the ability totest betimes, often, and anyplacein the development round. Katalon Studio 8.1 delivers a vital lineament that aims to increase the operations and cost-efficiency of your mechanisation cycle. Leveraging the fail-fast principle, & nbsp; Studio 8.1 provides users with the power to stop Test Suite Executions when a particular failure threshold is reached. & nbsp;

This new characteristic will help make more efficient use of prove devices and amend substructure costs, especially for cloud user.

Fail Fast, Fail Often in Katalon Studio – Terminate Execution Conditionally

 

Failure thresholds in KS 8.1 allow users to cease the Test Case or Test Suite Collection execution when there is a significant act of tryout cases in an execution that has failed, enabling them to cater feedback earlier in the cycle rather than waiting until the trial rhythm is finish.

To leverage this feature, we have included a new command pick,-maxFailedTests=T, where T is the maximum bit of failed executions allowed before the examination is stopped. Once the Test Execution stops, Katalon Studio will generate the report containing all the insights. This feature is merely useable for tests executed through the CLI or CI using the runtime locomotive.

First, find the option to set the threshold within the Generate Command for Console Mode dialog box – & nbsp; set the tier of failure tolerance by ticking the box “ Terminate the execution once the total number of trial failure reaches this threshold ” and type a bit in the text field.

Generate the CLI command, which in this case will include the-maxFailedTests=parameter in it.

Run the execution and once it reaches the threshold, there will be a message in the CLI indicating that it had stopped following the rules. & nbsp;

You can besides take a look at the sum-up of passed and failed tests return by Studio in the Test Cases Table within the story:

For autonomous testing across multiple user personas, check out SUSATest — it explores your app like 10 different real users.

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

Access Pass/Fail Trends with TestOps

After selecting your failure threshold, connect to TestOps, Studio ’ s built-in tryout reporting and instrumentation platform, to see your pass/fail patterns.

Step 1. Set up an Organization and Project

First, log in to analytics.katalon.com with your Katalon account.

Step 2. Integrate with TestOps in Katalon Studio

Open Katalon Studio, go toProject & gt; Settings(similar for both Mac and Windows).

  • Click on Katalon TestOps& gt; control theOverride authenticationbox & gt; take yourOrganization(if you can not find your Organization, clinkFetch Organization)
     
  • Insert your Katalon email and password

Click on Enable Katalon TestOps Integration& gt; choose yourTeam & gt; Project & gt; Apply and close.

 

Step 3. Push and vista Katalon Studio Test Suite Results on TestOps

Note: TestOps will mechanically collect all of your test runs byTest Suite. Assemble yourTest Casesinto a distinctTest Suiteto assure that executions are exhaustively documented. In the left carte, navigate toTestOps > Test Runs& gt; choose aTest Run.

Having be navigated to TestOps, you can view the pass/fail trends. & nbsp;

Wrapping Up

We are throb about Studio 8.1, and we desire you are too. We encourage you to download Studio 8.1 to get taking advantage of its many new features and improvements. & nbsp;

For a complete list of new features, improvements, and mess, delight visit the freeing note. As always, please post any questions, ideas, or concern on our, we are eager to hear from you.

 

 
 

Trigger modal

 

Explain

|

FAQs

What is the fail-fast principle in software quiz?

+

It is the thought that systems should stop execution as shortly as failures occur, making bug easier to detect early and reducing the cost of fault.

How make Katalon Studio 8.1 enable fail-fast execution?

+

It introduces a failure door that halts test suite execution mechanically when a specified number of exam cases fail.

How do you set a failure threshold in Katalon Studio?

+

By using the-maxFailedTests=Tcommand alternative or choose the termination option in the Generate Command for Console Mode duologue.


  •  

When is the fail-fast feature uncommitted in Katalon?

+

It is available for tests fulfill through the CLI or CI pipeline using the Katalon Runtime Engine. & nbsp;

How can teams analyze pass/fail trends after hold fail-fast?

+

By mix with Katalon TestOps, which centralize reporting and visualizes pass/fail patterns across test runs.

Contributors
The Katalon Team is composed of a diverse group of dedicated professionals, including subject matter expert with deep domain noesis, experienced technological writers skilled, and QA specializer who bring a practical, real-world view. Together, they conduce to the Katalon Blog, delivering high-quality, insightful articles that empower users to make the most of Katalon ’ s tools and remain updated on the latest trends in test automation and software quality.

Automate This With SUSA

Upload your APK or URL. SUSA explores like 10 real users — finds bugs, accessibility violations, and security issues. No scripts needed.

Try SUSA Free

Test Your App Autonomously

Upload your APK or URL. SUSA explores like 10 real users — finds bugs, accessibility violations, and security issues. No scripts.

Try SUSA Free