If you work in QA, you're probably accustomed to thinking of software monitoring as someone else's job. Traditionally, responsibility for monitoring applications fell to IT teams; QA's role ended with pre-deployment testing, and QA engineers did not usually touch monitoring tools. But the reality is that monitoring tools—meaning tools designed to help track application availability and performance, and also alert teams to problems—aren't just for IT teams.

Recompose is a React utility belt for function components and higher-order components that has been very useful to our frontend engineering team. After more than three years of working with it, we’ve identified a lot of pain points. In October 2018, the React team introduced Hooks which shipped with React v16.8 and provided an alternative to HOCs.

In our last post, we explored the pros and cons of Recompose and why we decided to remove it from our codebase. This post includes the strategy we used to approach the large task of implementing that refactor. It’s important to note that this strategy was created to fit our specific situation and is not a one size fits all approach to removing Recompose. Specifically, it was intended to work with our large codebase that is modified by our devs daily.

There are two different categories of tools in the load testing ecosystem. The first category is called non-scriptable tools and are usually used for load testing either a single endpoint or a set of endpoints. These tools usually generate load using a constant rate, which is measured in requests per unit of time, usually seconds. These non-scriptable tools don't apply any logic to the load testing process, other than the generation of load.

As a reconfirmation, Katalon Studio 6 and all of its previous versions will be obsolete on April 30, 2020 with a six-month grace period starting from October 2019, according to our community announcement. Here are all the details on the end-of-support or Katalon Studio 6 and what you need to know to prepare for the transition.

A bug is the most important entity in the software testing life cycle. Priority and Severity are the most important attributes assigned to a bug and yet these are the most misunderstood ones too. When properly used, these properties help in the effective execution of the bug fixing and release scheduling process. Whenever a new bug is encountered, the bug is logged by a tester or a customer.

Regression testing comprises re-running the test cases of already stable features and finding out if the new code changes attributed to the new release led to any negative impacts on the existing functionalities. With the amount of data flow across multiple modules in applications being made today, a feature addition or a fix can cause unexpected issues in the normal system operations.

Gatling is a load testing tool for measuring the performance of web applications. As such, it supports the following protocols: HTTP, WebSockets, Server-sent events. Other protocols are also supported either by Gatling itself (like JMS) or by community plugins. Gatling load testing scenarios are defined in code, more specifically using a specific DSL. This guide focuses on the basics of writing a simulation to test an HTTP application: OctoPerf’s sample PetStore.

It has been almost three years since we first published our first comparison & benchmark articles that have become very popular, and we thought an update seemed overdue as some tools have changed a lot in the past couple of years. For this update, we decided to put everything into one huge article - making it more of a guide for those trying to choose a tool.

Almost every business today runs online. The internet is one of the easiest avenues for businesses to reach users, and websites are a great way to impress your customers. So, when you’re building a web application for your business, it’s important that you make it the best version it can be. To make sure that your web application is good enough to impress customers and avoid any negative impact, you have to test your application and fix any issues.