expect

Run adversarial browser tests against code changes to surface regressions.

4|Updated Feb 12, 2026

Search Tags:#diagnostics #browser-testing #web-app #regression-testing #test-plans #qa-automation #adversarial-testing

Ready to run

npx skills add https://github.com/rbaumier/skills --skill expect-rbaumier

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: expect
Source: https://github.com/rbaumier/skills/tree/main/expect
Command: npx skills add https://github.com/rbaumier/skills --skill expect-rbaumier

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify regressions by performing adversarial browser tests against code changes.

Core Features & Use Cases

Adversarial test plans and session recordings designed to break UI paths and surface regressions.
Cookie/auth injection and structured pass/fail output to help QA quickly identify issues.
Use Case: after a browser-facing change, run tests to stress critical flows and validate resilience.

Quick Start

Run expect-cli against your app's base URL with a defined adversarial test plan and review the pass/fail results.

Frequently Asked Questions about expect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I identify UI regressions using adversarial browser testing?▼

Adversarial browser testing identifies UI regressions by executing deterministic test plans against code changes. It stresses critical flows like forms and routes to surface edge cases, producing structured pass/fail output for QA review.

What is an adversarial test plan for web app regression testing?▼

An adversarial test plan is a deterministic set of browser tests designed to actively break UI paths. It targets pages, components, and routes after browser-facing updates to validate application resilience and surface hidden edge cases.

How do I run adversarial test plans against a base URL?▼

To run adversarial test plans, use expect-cli against your web app's base URL. Execute the defined test plans to stress critical flows, and review the structured pass/fail output to quickly identify regressions.

Do I need expect-cli to perform QA automation on UI components?▼

Yes, you need expect-cli installed to run deterministic adversarial test plans. It requires a base URL to target your web app and generates structured pass/fail output to validate UI component resilience.

Can I inject authentication cookies during browser testing?▼

Yes, the testing mechanism supports cookie and auth injection. This allows adversarial test plans to access authenticated areas of your web app, ensuring critical user flows and protected routes are fully stress-tested.

What is the best way to surface edge cases after a browser-facing update?▼

The best way to surface edge cases is running adversarial browser tests immediately after browser-facing code changes. This applies targeted stress to critical UI paths and forms, identifying regressions before deployment.