Operations | Monitoring | ITSM | DevOps | Cloud

Testing

The latest News and Information on Software Testing and related technologies.

Continuous Load Testing | A Developer's Guide

Continuous load testing is a powerful way of preparing for surges in traffic, without needing real users. Imagine you’re a software engineer working on a website that’s seen a recent surge in traffic. Despite initial testing indicating that the website should be capable of handling the increased load, the website crashes during peak hours. Load Testing is the process of simulating real-world usage of a website or application.

Building a Mock Server from User Traffic in Kubernetes

A mock server can prove useful in many circumstances. Imagine you’re an engineer working on optimizing a feature inside of an existing API that relies on multiple other microservices to function properly. To fully test the optimizations, you’ll have to set up test versions of all the dependencies, which quickly proves to be quite a task in and of itself. This is where a mocks—a server that simulates the behavior of a real server—can be very beneficial.

Top Reasons Why Testing Is Crucial In Every Field

Testing is a critical component in any field and can play an important role in understanding the complexities of the products, services, or processes being examined. Testing provides robust feedback that helps to ensure accuracy and quality assurance, which are essential for businesses seeking success. Testing also allows teams to identify areas of improvement and develop strategies to rectify errors. This article will explore the top reasons why testing is such a crucial element in all fields.

Load testing Grafana k6: Peak, spike, and soak tests

With k6 Cloud, Grafana Labs is in the business of generating load — lots of load, distributed across a cluster of computers. So while our customers care about the systems they load, we care that our system can generate the load that they need and process the test metrics for them in an intuitive, explorable way.

Sponsored Post

Testing Kubernetes Ingress with Production Traffic

Testing Kubernetes Ingress resources can be tricky, and can lead to frustration when bugs pop up in production that weren't caught during testing. This can happen for a variety of reasons, but with Ingress specifically, it often has to do with a misalignment between the data used in testing and the traffic generated in production. Tools like Postman can be a great way of generating traffic, but they have the drawback of being manually created. Not only is this unlikely to create all the needed variations for a single endpoint (different headers, different request bodies, etc.), it would be almost impossible to create all the needed variations, for all possible endpoints.

Watch: How to pair Grafana Faro and Grafana k6 for frontend observability

Grafana Faro and xk6-browser are both new tools within the Grafana Labs open source ecosystem, but the pairing is already showing a lot of potential in terms of frontend monitoring and performance testing. Faro, which was announced last November, includes a highly configurable SDK that instruments web apps to capture observability signals that can then be correlated with backend and infrastructure data.

How we reduced flaky tests using Grafana, Prometheus, Grafana Loki, and Drone CI

Flaky tests are a problem that are found in almost every codebase. By definition, a flaky test is a test that both succeeds and fails without any changes to the code. For example, a flaky test may pass when someone runs it locally, but then fails on continuous integration (CI). Another example is that a flaky test may pass on CI, but when someone pushes a commit that hasn’t touched anything related to the flaky test, the test then fails.

Two sides of the same coin: Uniting testing and monitoring with Synthetic Monitoring

Historically, software development and SRE have worked in silos with different cultural perspectives and priorities. The goal of DevOps is to establish common and complementary practices across software development and operations. Sadly, in some organizations true collaboration is rare and we still have a way to go to build effective DevOps partnerships.