expect

Runs adversarial browser tests against code changes using the expect-cli command-line tool.

Updated Apr 30, 2026
One-click install
npx skills add https://github.com/AdityaBorkar/igbot-fork --skill expect-adityaborkar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: expect
Source: https://github.com/AdityaBorkar/igbot-fork/tree/main/.agents/skills/expect
Command: npx skills add https://github.com/AdityaBorkar/igbot-fork --skill expect-adityaborkar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires expect-cli.

What problem does it solve? Verifying browser-facing changes by hand or with raw browser tools often confirms only the happy path, letting edge-case bugs reach production. This Skill runs adversarial browser tests that actively try to break your changes and report structured pass/fail results. ## Core Features & Use Cases - Adversarial Test Plans: Generates tests targeting empty inputs, invalid data, boundary values, double-clicks, and navigation edge cases rather than simple render checks. - Structured Failure Output: Reports the exact failing step and what broke, so fixes are fast and verifiable. - Session and Auth Support: Provides session recordings, cookie/auth injection, and configurable base URLs via EXPECT_BASE_URL or --base-url. - Use Case: After changing a checkout flow, run expect-cli with instructions to submit valid data, then attempt empty-cart submission, invalid card numbers, double-click order placement, and back-button mid-payment, verifying error states and console errors. ## Quick Start Ask the AI to run expect-cli with an adversarial instruction against your local app, for example to test the login form with empty, invalid, and valid credentials and verify error messages and redirects.

Frequently Asked Questions about expect

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

FAQPage Schema
How do I run adversarial browser tests on my code changes?▼

Run expect-cli with the -m flag containing a natural-language test instruction and -y to skip interactive review. Write instructions that try to break the feature, covering empty inputs, invalid data, boundary values, and rapid repeated submissions.

What is a good browser testing instruction for expect-cli?▼

Good instructions describe adversarial user behavior, such as submitting a form empty, with invalid email, wrong password, and valid credentials, then verifying error messages and redirects. Avoid instructions that only confirm a component renders.

How do I test an app not running on localhost:3000?▼

Set the EXPECT_BASE_URL environment variable or pass the --base-url flag to point expect-cli at your app's actual URL, for example EXPECT_BASE_URL=http://localhost:5173 before the command.

Why is the expect-cli command not found?▼

The CLI is not installed globally. Install it with npm install -g expect-cli, then verify installation by running expect-cli --version before proceeding with any tests.

What should I do when an adversarial browser test fails?▼

Read the failure output, which names the exact step and what broke. Fix the underlying issue, then run expect-cli again to verify the fix and check for new regressions in nearby features.