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.
Last week the Rookout team, myself among them, participated in and sponsored the O’Reilly Software Architecture Conference in New York. New York is a city I personally love - the energy, the food, and the views are always top notch- there’s really just no comparison to the city that never sleeps. On top of that, I had the opportunity to mingle with some of the brightest minds in software architecture from many of the most successful companies in the world.
When you login your stacks are displayed on the dashboard. To enable alerts for a stack, choose the 'Settings' button. Next, choose 'Alerts' and then click 'Provision ElastAlert' for this stack
Consultancy firms and system integrators are starting to productize analytics. They’re creating turnkey solutions for customers and adding value to them by offering managed services. If you’re thinking of creating an analytics solution for your customers, there are three things you need to think about when choosing a BI vendor to partner with.
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.
Today, countless engineering teams have leveraged API monitoring to track infrastructure health and report when services are down or unhealthy. There are a variety of API metrics that can be tracked that are aligned with engineering goals such as uptime, average latency, requests per minute, and errors per minute. However, these metrics are not aligned with the business goals of product owners and growth teams.
In today’s post, we’ll learn how to build a Rails app that can support multiple subdomains. Let’s assume that we have a gaming website funkygames.co and we want to support multiple subdomains such as app.funkygames.co, api.funkygames.co, and dev.funkygames.co with a single Rails application. We want to ensure that proper authentication is performed for all subdomains and that there are no duplicate routes.
