Improving Development Velocity Using Ephemeral Environments

Velocity is a measurement of how many story points a software development team can finish within a sprint (usually one or two weeks). These points are set by the software development team when they review a ticket and estimate how complex the ticket is. When a team measures this output over a period of time, generally they have a consistent amount of story points they can deliver in a sprint and their velocity is known.

Improving developer velocity is directly correlated with performance. McKinsey published an article in April 2020, where they cite that companies in the top 25% on their Developer Velocity Index grow up to twice as fast as companies in their same industries. Intuitively, this makes sense since delivering more allows the development team to learn through iterating and improving.

Configure Cypress Tests to Run on Multiple Environments

One of the most common scenarios in an automation framework is to run scripts on different environments like QA, staging, production, etc. There are multiple ways to configure your Cypress framework to run on different environments. I am going to show the three most used methods

In this article, I have explained 3 different methods to run your Cypress tests on multiple environments.

Environments: The ROI of TEM

This post was written by and published with permission on behalf of Carlos Schults. Carlos is a consultant and software engineer with experience in desktop, web, and mobile development.

Let me start with a question: as a leader in tech, are you satisfied with the budget you have? If I had to guess, I'd say the answer is no. Because of that, calculating the return on investment of the many activities in software development is certainly an invaluable strategy. With ROI data in your hands, you can prove that a given process helps the bottom line of the organization. In this post, we'll offer you a guide about the ROI of TEM (test environment management).