Systems | Development | Analytics | API | Testing

Your testing team, from developers to testers, has put out a great amount of work to design test cases. Knowing that an error-free testing process simply does not exist, when it comes to the test execution, this one fails, while the rest passes. Or, is one of them is taking much longer to complete compared to previous runs? How do you determine if your tests have slowed down or increased their probability of failing? This requires context–historical logs from past sessions to be more specific.

Building on the promise to offer a swift testing experience to the testing community, Katalon is thrilled to announce the release of TestOps April 2021! This release adds multiple features such as integration with Pytest, Kobiton, the ability to execute Test Suites in parallel and more!

In this post, we take a look at 5 pub/sub examples that will help us understand how companies and organizations across all types of industries are leveraging this architectural design pattern to solve common engineering challenges and improve their architecture.

PHP has been one of the top (if not best) server-side scripting languages in the world for decades. However, let’s be honest – error logging in PHP is not the most straightforward or intuitive. It involves tweaking a few configuration options plus some playing around to get used to.

ISO 25010 helps you to ensure that your software is high quality. Read along or jump ahead to the section that interests you the most.

Testing in production simply means testing new code changes in production, with live traffic, in order to test the system’s reliability, resiliency, and stability. It helps teams solve bugs and other issues faster, as well as effectively analyze the performance of newly released changes. Its overall purpose is to expose problems that can’t be identified in non-production environments for reasons that may include not being able to mimic the concurrency, load, or user behavior.