Systems | Development | Analytics | API | Testing

Regression testing is indeed one of the most time-consuming part of software testing: repetitive, tedious, and requiring high volume of executions. And yet, you can't ignore regression testing. It is the guardrail preventing bugs from slipping into production. But if you don't try to reduce the time it takes to do regression testing, it becomes counter-productive, very soon.

With the rapid adoption of AI-driven coding tools, software development is experiencing a seismic shift. Increasingly, developers rely on tools like GitHub Copilot and other generative AI solutions (collectively termed “vibe-coding”) that now account for roughly 30% of code output in leading organizations. This trend raises significant questions for QA teams: What happens when AI significantly contributes to the codebase, and how does this reshape the landscape of software testing?

Katalon officially signed a Memorandum of Understanding (MOU) with RMIT University Vietnam. This collaboration aims to bridge academic learning with real-world software development and software testing expertise, equipping students with an adaptive mindset, future-ready skills and AI tools. Leaders and representatives from RMIT Vietnam and Katalon at the MoU signing ceremony.

If you're still using an earlier version of Katalon Studio, you're likely missing out on major improvements that make everyday testing faster, easier, and more reliable. Studio 10.2.0 focuses on solving real-world problems, giving AI more context when writing test scripts, speeding up and clarifying test reports, and strengthening integrations and security for teams working at scale. Here are the top three reasons to upgrade today.

Automation testing begins with a test script. Its job is to command the machine to perform each test step on your behalf. A well-written test script executes those steps exactly like how a human would, with the extra consistency, standardization, and precision of a machine. However, writing test scripts means coding, and coding can sometimes be a challenge, especially for testers who are only getting started. Let us show you how to write a test script in a simple fashion.

A test suite is a collection of test cases with similar characteristics. They are created to group test cases for a specific feature. Depending on the nuances of your product, there are so many ways to categorize test suites. In this article, we'll show you: Let's dive in!

The information in this blog post is based on a real-life scenario shared by a user on our Katalon Community forum and is intended to inspire peer-to-peer discussion and collaboration. Please always test solutions thoroughly before implementing them in a production environment. Feel free to continue the discussion here.

In this article, we’ll quickly cover those core Selenium commands and then show how Katalon Studio streamlines the same process - letting you capture a dropdown with Spy Web and select options using built-in keywords like selectOptionByValue or selectOptionByIndex, so you can automate dropdown interactions without writing boilerplate code, but first...

This blog provides a quick guide to find and use XPath in Selenium. XPath uses path expressions to navigate through elements, attributes, and select nodes or node-sets. The basic syntax of an XPath expression is: Xpath=//tagname. Make sure that you have installed a Selenium library. If you haven't, you can have a look at Selenium documentation for how-to guides.

Managing software testing via spreadsheets might be adequate for small-scale projects or startups. However, as your team grows and projects become more complex, this approach quickly reaches its limits. That's why TestOps was born. As a concept, TestOps is relatively new, having existed only since 2019. However, it is the kind of concept that has changed and surely will continue to influence the QA industry.