Testing
We track 147 posts about Testing from 80 engineering blogs. Most active: T.J. Maher, Gleb Bahmutov, Henrik Warne. Latest post: Oct 8, 2026.
Companies writing about Testing
Recent posts
Playwright 1.64 WebMCP Testing: How to Inspect and Call Page Tools (opens on the source site)
Test pages exposing WebMCP tools using the page.webmcp API introduced in Playwright 1.64. Learn how to launch Chromium with the required flag, discover page-registered tools, execute calls, and assert results. Continue reading Playwright 1.64 WebMCP Testing: How to Inspect and Call Page Tools on SitePoint.
Can Agentic AI Find the Security Vulnerabilities Other Tests Miss? (opens on the source site)
Security teams are good at finding problems. The difficult part is finding the right problems across a growing codebase, a changing application and the connections between them. A scanner can flag a known pattern quickly. A skilled tester can follow a complicated line of enquiry. Neither has unlimited time, and there will always be a question nobody thought to ask. Could AI agents take on more of that investigative work? I think the answer is yes, provided we are precise about what “find” means. Agents can produce leads, test assumptions and uncover issues that established checks have missed.…
Use Paicku to containerize and test any app with buildpacks and Node.js (opens on the source site)
Red Hat ·
Containerizing applications is an important step in modern software development. It helps with consistency, portability, and reliability across different environments. The Paicku project helps you streamline the process of containerization and testing so you can be sure that your application works as expected during development and once it's been released.Paicku is a command-line tool, as well as a Node.js library, that lets you containerize applications with Cloud Native Buildpacks. You can run Paicku from the command-line or from Node.js. The post Use Paicku to containerize and test any app…
Beyond synthetic testing: Capturing and replaying real database workloads at Airbnb (opens on the source site)
Airbnb ·
How we capture real production database traffic at Airbnb and replay it offline to load-test, plan capacity, and de-risk upgrades.By: Zuofei Wang, Erluo LiIntroductionAt Airbnb, MySQL-compatible databases are a critical backbone of our online database infrastructure: a fleet of hundreds of clusters supporting thousands of use cases at millions of queries per second (QPS). Operating databases at scale brings hard problems, including sizing clusters for future growth, keeping behavior consistent across version upgrades and migrations, and reproducing production incidents well enough to debug…
Write End-to-End Tests in Your Backend’s Language (opens on the source site)
The browser is often the easiest part of an end-to-end test. Consider a test that verifies a user can complete an overdue task. The visible interaction is small: sign in, find the task, click Complete, and observe the new status. Before any of that can happen, the test needs a workspace, a user, a project, and […] The post Write End-to-End Tests in Your Backend’s Language appeared first on Atomic Spin.
Building and testing a config management orchestrator for Windows (opens on the source site)
The following is part of a series of posts about 2026 summer intern projects—for more, see “What the interns have wrought, special jumbo 2026 edition”
UWP and WinUI 3 apps: UI testing with MSTest (opens on the source site)
.NET ·
Learn how to test UWP and WinUI 3 apps with MSTest and Microsoft.Testing.Platform across packaged, unpackaged, and AppContainer hosts. The post UWP and WinUI 3 apps: UI testing with MSTest appeared first on .NET Blog.
Mailbox for Laravel: Preview and Test Rendered Email (opens on the source site)
Laravel ·
Mailbox for Laravel captures outgoing mail in a local dashboard and lets you test rendered HTML, recipients, and attachments with fluent assertions. The post Mailbox for Laravel: Preview and Test Rendered Email appeared first on Laravel News. Join the Laravel Newsletter to get Laravel articles like this directly in your inbox.
Representative Line: Unique Testing (opens on the source site)
Nikolai M's team had a flaky CI/CD build. About 0.5% of the time, one of their tests would fail: frequent enough to be annoying, but not so frequent that it motivated management to assign anybody to investigate. Nikolai eventually dug in, taking the initiative. Microsoft's implementation of UUIDs calls them GUIDs. The GUID is, per the docs, really just a wrapper around UUID algorithms, and supports a variety of different UUID variants. I'm sure at some historical point, this wasnt't true, and Microsoft had some weird internal algorithm. That's not really here nor there, but the test that was…
iOS 27 Glass You Can Choose, Measure, and Test (opens on the source site)
Select the iOS 27 theme independently of Xcode, see the revised glass in motion, and explore local iPhone Duo posture support.
How to Test and Fix Voice AI Agent Prompts with Twilio Conversation Relay and Cekura (opens on the source site)
Twilio ·
Build and test an AI voice agent using Twilio Conversation Relay and Cekura. Write metrics, run evaluations, and fix prompt bugs.
Prompt-Driven Development: Building with GitHub Copilot Coding Agents (opens on the source site)
We used GitHub Copilot coding agents to build an app across different time zones. The AI wrote the code, but prompts, tests, guardrails, and pull requests made it software development rather than vibe coding.
Optimizing GitHub Actions for Agent PRs: Speculative Test Slicing and AST Impact Analysis (opens on the source site)
Fix CI saturation from high-frequency agent pull requests with AST change-impact analysis and speculative test slicing in GitHub Actions. Continue reading Optimizing GitHub Actions for Agent PRs: Speculative Test Slicing and AST Impact Analysis on SitePoint.
From hours to minutes: Optimizing Red Hat Developer Hub performance testing with immutable LDAP images (opens on the source site)
Red Hat ·
At Red Hat, our CI/CD pipelines are the heartbeat of our development process. However, as we scaled the Red Hat Developer Hub performance testing framework, we hit a wall. Our environment setup time was ballooning, turning what should have been a seamless verification step into a long waiting game. For performance engineering in catalog-dependent applications, deployment and catalog population speed directly dictate your feedback loops. The post From hours to minutes: Optimizing Red Hat Developer Hub performance testing with immutable LDAP images appeared first on Red Hat Developer.
Write End-to-End Tests in Your Backend’s Language (opens on the source site)
The browser is often the easiest part of an end-to-end test. Consider a test that verifies a user can complete an overdue task. The visible interaction is small: sign in, find the task, click Complete, and observe the new status. Before any of that can happen, the test needs a workspace, a user, a project, and […] The post Write End-to-End Tests in Your Backend’s Language appeared first on Atomic Spin.
Test GitHub Actions Locally with Act (opens on the source site)
GitHub Actions are a great way to implement CI/CD into your projects, whether personal or professional. GitHub has a lot of great tools to help with CI/CD, but GitHub Actions in particular is very helpful. However, writing actions can be tedious and a little annoying, especially if you don’t know what you’re doing. On top […] The post Test GitHub Actions Locally with Act appeared first on Atomic Spin.
Python in operator: How __contains__ speeds up membership tests (opens on the source site)
How does the “in” operator work in Python? – If an object defines __contains__, then its (boolean) result is returned (coerced to bool).– If not, then Python iterates over it […] The post Python in operator: How __contains__ speeds up membership tests appeared first on LernerPython.
Moving from XCTest to Swift Testing [FREE] (opens on the source site)
Swift Testing is Apple’s replacement for the objective-C XCTest unit testing framework. Discover how to migrate your existing XCTest suites over to Swift Testing, including how to get some assistance from Xcode’s agentic AI tooling.
Making testing work better for AI driven development (opens on the source site)
AI agents can generate and modify code quickly. But when a test fails, speed is no longer enough. The agent needs enough context to understand what happened, why it happened, and whether the code or the test itself needs to change. In our latest product update, Marko Gaćeša is joined by Semaphore engineers Nick and […] The post Making testing work better for AI driven development appeared first on Semaphore.
Why Spotify Is Not Using Bayesian A/B Testing (opens on the source site)
Spotify ·
Clearing the confusion about what Bayesian A/B testing is. The post Why Spotify Is Not Using Bayesian A/B Testing appeared first on Spotify Engineering.
Testing the Swagger Petstore: Manually Testing An API Using Swagger UI (opens on the source site)
With the last post, Testing the Swagger Petstore: Reviewing API Documentation Formatted in OpenAPI 3.0 with Swagger UI we started exploring an API with Swagger UI, such as the Swagger Petstore at https://petstore3.swagger.io/Here, we will start exploring how to test an API using the Swagger UI.The tests we can run are:Happy Path Testing, checking the Positive ScenariosNegative Testing, reviewing the Invalid Inputs & Error HandlingBoundary & Edge Case Testing, checking how the API handles the extreme limits of allowed input rangesAuthentication & Authorization TestingContract and schema…
Testing the Swagger Petstore: Manually Testing An API Using Swagger UI (opens on the source site)
With the last post, Testing the Swagger Petstore: Reviewing API Documentation Formatted in OpenAPI 3.0 with Swagger UI we started exploring an API with Swagger UI, such as the Swagger Petstore at https://petstore3.swagger.io/ Here, we will start exploring how to test an API using the Swagger UI. The tests we can run are: Happy Path Testing, checking the Positive Scenarios Negative Testing, reviewing the Invalid Inputs & Error Handling Boundary & Edge Case Testing, checking how the API handles the extreme limits of allowed input ranges Authentication & Authorization Testing Contract and schema…
Find Unexpected Test Inputs with Fuzz for Pest (opens on the source site)
Laravel ·
Fuzz brings coverage-guided fuzz testing to Pest 5, generating inputs to find failures beyond the cases you write by hand. The post Find Unexpected Test Inputs with Fuzz for Pest appeared first on Laravel News. Join the Laravel Newsletter to get Laravel articles like this directly in your inbox.
How well do agents use test/verification techniques? (opens on the source site)
Dan Luu ·
We previously noted that, while it's easier than ever to hit a particular quality bar by having coding agents use effective test techniques, software quality seems to be getting worse, indicating that whatever defaults developers are using may not work very well. Here, we test if simple instructions to agents to use particular techniques or libraries improve implementation correctness. Here, we re-use the Zstd implementation eval discussed in this comparison of agentic programming language effectiveness and, instead, compare different testing techniques and testing libraries when agents are…
Testing the Swagger Petstore: Reviewing API Documentation Formatted in OpenAPI 3.0 with Swagger UI (opens on the source site)
For this next project, we will be examining the test site Swagger Petstore - OpenAPI 3.0 at https://petstore3.swagger.io/https://petstore3.swagger.io/If we wanted to really dive deep into creating API documentation, we could use:I'dRatherBeWriting's Free Documenting APIs course, showing an Introduction to REST APIs, using APIs like a developer, Documenting API endpoints, the Open API spec, Testing API docs, Publishing API docs, and more... ... But that goes too deep for this blog post. Before we begin, let's get into some background information. What is Swagger?According to OpenAPISpec.com's…
Testing the Swagger Petstore: Reviewing API Documentation Formatted in OpenAPI 3.0 with Swagger UI (opens on the source site)
For this next project, we will be examining the test site Swagger Petstore - OpenAPI 3.0 at https://petstore3.swagger.io/ https://petstore3.swagger.io/ If we wanted to really dive deep into creating API documentation, we could use: I'dRatherBeWriting's Free Documenting APIs course, showing an Introduction to REST APIs, using APIs like a developer, Documenting API endpoints, the Open API spec, Testing API docs, Publishing API docs, and more... ... But that goes too deep for this blog post. Before we begin, let's get into some background information. What is Swagger? According to…
Test what you ship: MSTest and Native AOT (opens on the source site)
.NET ·
MSTest source generation lets test projects use the same Native AOT and trimming deployment model as the applications they validate, while reducing reflection on the test execution path. The post Test what you ship: MSTest and Native AOT appeared first on .NET Blog.
Testing cookie behavior across hundreds of web surfaces with our in-house auditor (opens on the source site)
Dropbox ·
Our cookie auditor acts like a privacy-conscious user by visiting web pages and checking that they only load cookies consistent with that user’s preferences.
How Developers Can Test Their Feature Branch Against Various Playwright Configurations Before Creating a Merge Request in GitLab CI/CD (opens on the source site)
Developers need the option to test out their feature branch before merging it into main. In the last section, we set up a GitLab CI/CD Pipeline in our bun-create-playwright project to check every GitLab Merge Request. Now, we will be giving developers option to create a new pipeline where they can choose:Which feature branch to test against.Which test suite to execute (LoginPage tests? Secure Area? Or all of them?)Which Playwright browser to use: Chromium, Firefox, WebKit, or all.All these features can be set up using our .gitlab-ci.yaml file!Go to to bun-create-playwright, view the Pipelines…
How Developers Can Test Their Feature Branch Against Various Playwright Configurations Before Creating a Merge Request in GitLab CI/CD (opens on the source site)
Developers need the option to test out their feature branch before merging it into main. In the last section, we set up a GitLab CI/CD Pipeline in our bun-create-playwright project to check every GitLab Merge Request. Now, we will be giving developers option to create a new pipeline where they can choose: Which feature branch to test against. Which test suite to execute (LoginPage tests? Secure Area? Or all of them?) Which Playwright browser to use: Chromium, Firefox, WebKit, or all. All these features can be set up using our .gitlab-ci.yaml file! Go to to bun-create-playwright, view the…
Related topics
This page is generated automatically from the engineering blogs we follow. Every post links to its source, where it was published. See all sources.