Developing an application is one thing. Developing an application that actually delivers an excellent end user experience is another.

According to browser usage statistics here , there are 4.3 billion internet users today. Review42.com also says that in 2008 there were 112 different types of browsers people were using to access the internet. Thus, it’s evident that people can be accessing the same website from multiple browsers at the same time – which makes cross-browser testing very important.

Hello Katalians! Time flies when you’re busy creating awesome products! Back in May, we delivered Katalon Studio 8 , which included features to provide better scalability options and a better user experience. And because we are not in the business of keeping you waiting for the latest and greatest, today, we are excited to announce the release of Katalon Studio 8.1 (KS8.1) .

Today’s software testing trends show the growing demand for more efficient and automation-oriented API testing. Many of the current test automation solutions focus on the UI, while most API-level testing is still done manually. As a result, testers are in need of easy-to-use, intelligent automation tools for testing APIs — improving their productivity and efficiency, while also reducing time-to-market.

At SLOConf 2021 I talked about how we may use error budgets to add pass/fail criterias to reliability tests we run as part of our CI pipelines. As Site Reliability Engineers, one of our primary goals is to reduce manual labor, or toil, to a minimum while at the same time keeping the systems we manage as reliable and available as possible. To be able to do this in a safe way, it's really important that we're able to easily inspect the state of the system.

Cloud testing is expected to grow to USD 11 Billion by 2023 , and we are talking about only cloud testing here, not cloud computing. Complex testing scenarios such as cross-browser testing, parallel testing, can be made more effective when done on the cloud. The reason being – the cloud provides the required testing environment effortlessly and can be scaled up or down as needed.

Even though automated testing helps you do more software testing in less time with fewer people, maintaining your test suite can be very time-consuming. Many QA teams have a hard time keeping up with maintenance as their product grows. If they fall behind, they get more and more false positives (i.e., cases where the test fails because of a problem with the test, not a problem with the application).

One of the more challenging aspects of load testing happens very early on: getting your scripts working. When you run your scripts, you may observe unexpected error status codes (typically in the 4xx-5xx status code range). Other times, you'll run your script and see it receive the expected responses (usually HTTP 200), yet the "thing" your script is meant to create simply doesn't show up anywhere, like on the database or as a record on the site. You start wondering: why on earth is that?