Systems | Development | Analytics | API | Testing

The world is entering a new age of technology: codeless applications, which are accessible to users at all levels. Popular codeless tools like Wix or Squarespace are making significant changes to the way non-dev users get involved in the product development cycle. By going codeless, teams can now fill in the gap between the accelerating demands of product delivery and the skill sets of the team members. Software testing is not an exception to the movement towards codeless practices.

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.

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.

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.

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.

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.

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.

The Swift Package Manager allows you to create standalone Swift applications both on Linux and macOS. You can build and run these apps and you have the ability to write unit tests for your codebase. Xcode ships with the XCTest framework, but you may not know that this is an open-source library. It's available on every single platform where you can install Swift.