k6 Browser Checks in Grafana Cloud Synthetic Monitoring | Demo | Grafana
In this demo video, Virginia Cepeda, senior software engineer at Grafana Labs, walks through the k6 browser checks feature in Grafana Cloud Synthetic Monitoring.
Operations | Monitoring | ITSM | DevOps | Cloud
The Place Where Modern Operations & Technology Come Together
The latest News and Information on Software Testing and related technologies.
Kubernetes Load Testing: How JMeter and Speedscale Compare
At some point, your development team may be considering implementing load testing (also known as stress testing) as part of your software testing process. Load testing validates that your web app is able to withstand a large number of simultaneous users, decreasing the chance that any traffic spikes will bring down your services once deployed. These stress tests can be highly granular, giving you the opportunity to test run virtually unlimited strategies before they are set into the wild.
How to control time zones and timeouts in Playwright
Join Stefan Judis (Playwright Ambassador) as we explore advanced testing strategies for time zones and timers using Playwright. You'll learn about seamless time zone testing techniques and how to use Playwright's Clock API to manage timers effectively. What we'll cover: Time Zone Testing: Learn how to test across multiple time zones with Playwright to ensure your applications perform consistently worldwide. JavaScript Timers: Discover how to control and test JavaScript timeouts using the Clock API, enhancing the reliability of your scripts.
GoReplay vs Speedscale for Kubernetes Load Testing
GoReplay and Speedscale are two popular tools commonly used for load testing. Both share traffic shadowing as a core feature. This article compares both tools against the following criteria: For more Kubernetes load testing comparisons, check out our other posts.
Autogenerate tests and mocks from real traffic
There are many ways to bootstrap tests and mocks within Speedscale. Matt LeRay goes over various ways, eg. by using sidecars, agents, postman collections, or even request response pairs.
Postman Load Test Tutorial
Postman is highly popular in the testing tools space for verifying API requests. While its use for general API testing is widely adopted, conducting load testing with Postman is not as straightforward. In this post, we assume that you have some experience working with Postman and are familiar with the fundamentals of creating and sending requests. If you’re new to Postman, there are numerous resources available in the Postman Learning Center.
Five Playwright CLI features you should know
Thanks to Microsoft's Playwright, running end-to-end tests with real browsers is quickly done. Initialize a new Playwright project, install all the dependencies, and off you go! Then, any new headless browser test run is only one npx playwright test away. But have you checked all the test command's CLI options? playwright test includes a few real gems to help you create better tests faster. Let me share a mixed bag of my favorite CLI tricks in this post.
How to Mock HTTP APIs With MockServer| Speedscale
As the name suggests, MockServer is a powerful tool that allows developers to mock HTTP APIs, making it much easier and more efficient to run an integration test in initial development phases. It aims to solve the problem of testing APIs that are still in development or not yet available, allowing developers to make http calls on an http client without a real server.
6 Golang Testing Frameworks for Every Type of Test
What do good tests look like, and do you even need a Golang testing framework? It’s a loaded question with an open answer. Not only do tests help ensure that your code will work as intended, but good tests can also serve as documentation for your codebase, making it easier to update and maintain in the future, while accelerating and streamlining your software development process. In this article, we outline 6 Golang testing frameworks for every type of test.
Five Playwright CLI features you should know
Learn how to optimize your Playwright end-to-end testing with additional `playwright test` command line options to run only failed tests, make Playwright Git-aware, or avoid running `test.only` in CI/CD. Got questions or tips?