Testing

When an agent changes a UI, checking a single account cannot cover every role, plan, or feature flag. Matt Rothenberg shows how values scattered across hooks, providers, and layouts can hide overlooked states — such as a Delete button shown to a view-only user.

Making display state an explicit component input lets teams render relevant combinations directly, test them, or compare them in a visual grid. Storybook and Playwright complement this approach, but they do not choose which scenarios to cover; that decision still matters.

Pour brings together a browser extension, a CLI, a VS Code extension and a contrast checker to assess accessibility against WCAG 2.2. Audits identify affected elements and explain fixes; criteria that require human judgment are marked for review.

The CLI can fail a CI step when it finds issues, generate an HTML report for a site, and expose tools to an agent through MCP. Automated checks assist with 51 of the 86 WCAG 2.2 criteria without claiming to determine compliance: a checklist accompanies the findings to support manual review.

PGX runs isolated PostgreSQL databases inside a single Rust runtime, targeting short-lived agent, CI, and test environments. On-demand creation from a sealed template and copy-on-write on ZFS reduce the cost of branching; without block cloning, the system makes a full copy.

The project is at v0.1.0 and targets disposable databases, not production data: fsync is disabled, and one runtime is a single failure domain. Its benchmarks document their measurements and conditions; the PostgreSQL regression suite reports zero result differences in the stated configuration, without claiming general compatibility.

This repository brings together tools for working with the WebMCP API: a Chrome extension inspects the tools exposed by a page, their input schemas, and connection issues, while a CLI evaluates whether LLMs call the right tools against defined test cases.

Demos also show declarative and imperative integrations in practical interfaces. The collection helps move from experimentation toward more structured testing, while remaining a project intended to support adoption of the WebMCP API.

sqlsimtools provides an open-source toolkit to test, replay, and compare SQL Server workloads without any hosted service or external telemetry. It offers four modes: a local Studio UI, a native CLI, a Python workflow, and an AI agent-driven experiment builder. The same suite applies to SQL Server 2019–2025, Azure SQL, and Microsoft Fabric, on Windows or Ubuntu, with local installation and direct execution against your chosen target.

Medula provides development tools for AI agents and documents how to connect them to Vue, React, Svelte, and Solid apps using Vite 8. The repository also includes examples and end-to-end tests for observing how an agent interacts with an application at runtime.

Superpowers provides skills for breaking down work, exploring a problem, and checking an implementation. Its repository describes a reusable method for multiple coding agents.

Bruno stores request collections in local text files. Git branches, diffs and reviews can then apply to API tests and examples alongside the rest of a project.

Vibium exposes navigation, forms, clicks and screenshots through CLI, MCP or client libraries. It uses WebDriver BiDi so agents can verify changes in a real interface.

This guide explains installing and running Dev Proxy from the command line. The tool simulates cloud API behaviors and failures to test application resilience.

Mailpit provides an SMTP server, a mail-viewing interface and an API for automated tests. Its Docker image lets developers inspect messages without sending them to real recipients.

Midscene uses a visual agent to perform actions and verify interface results. Tests can be described in YAML or integrated into an existing framework through its APIs.

This note explores composing generators to test TypeScript type predicates. It connects generated test values with checking the reliability of validation functions.

Mutation testing deliberately changes code to check whether tests catch the introduced faults. The article explains the technique as a complement to code coverage.

Microsoft introduces static instrumentation and additional report formats, including Cobertura. These changes make coverage collection easier to integrate across environments and reporting tools.

This release improves Webpack project startup through SWC and adds testing utilities. The announcement also covers integration changes and the storybook-doctor diagnostic tool.