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.
Platterz helps cultivate happy workplaces by creating delicious food experiences to offices across the country. To do this, the business intelligence team at Platterz is on a never-ending mission to derive important insights from the multitude of data at their fingertips. Platterz had the data and the world’s best visualization tool - Looker - but they needed a way to organize the data seamlessly in a way that was optimized for their teams.
Mall Group, the leading e-commerce group in Central Europe, recently employed Keboola to streamline operations and accelerate growth. In a matter of months, Keboola’s platform enabled Mall Group’s individual teams to become much more autonomous as well as accelerate feature development, testing, and deployment.
Platterz helps cultivate happy workplaces by creating delicious food experiences to offices across the country. To do this, the business intelligence team at Platterz is on a never-ending mission to derive important insights from the multitude of data at their fingertips. Platterz had the data and the world’s best visualization tool - Looker - but they needed a way to organize the data seamlessly in a way that was optimized for their teams.
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.
Welcome back to another one of our Community Roundups! If the flu season has got you down, don't worry — we’ve got some high-spirited tweets and articles to cheer you up. Take a look!
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.
