integrate-test-matcher

Claude Command: Integrate Test Matcher

This command initiates an interactive workflow to integrate a new or existing test matcher from @tevm/test-matchers into the @tevm/actions package's test suite.

Usage

To start the integration process, type:

/integrate-test-matcher

The Workflow

This command operates in three stages.

Stage 1: Discover and Select

First, I will analyze the @tevm/test-matchers package to identify all available matchers and their capabilities. I will then present you with a list.

AI Action:

1. Read the directory structure of extensions/test-matchers/src/matchers/.
2. For each category, parse the index.ts file to find exported matchers.
3. Read the JSDoc comments for each matcher to create a summary.
4. Present the list of matchers to the user.

---

(Example Interaction)

AI presents the list:

Here are the available matchers from @tevm/test-matchers:

• Value Matchers:
  • toBeAddress(opts?): Asserts a value is a valid Ethereum address.
  • toBeHex(opts?): Asserts a value is a valid hex string.
  • toEqualAddress(expected): Compares two addresses for case-insensitive equality.
  • toEqualHex(expected, opts?): Compares two hex strings with normalization.
• Event Matchers:
  • toEmit(contract, eventName): Asserts an event was emitted.
    • Chainable with: .withEventArgs(...), .withEventNamedArgs(...)
• Error Matchers:
  • toBeReverted(client?): Asserts a transaction reverted for any reason.
  • toBeRevertedWithString(client, message): Asserts a revert with a specific string message.
  • toBeRevertedWithError(client, contract, errorName): Asserts a revert with a specific custom error.
    • Chainable with: .withErrorArgs(...), .withErrorNamedArgs(...)

Please specify which matcher (and its chainable companions) you would like to integrate into the @tevm/actions test files.

---

User responds, e.g., "Please integrate toBeRevertedWithError and withErrorNamedArgs."