测试与安全

argent-create-e2e

software-mansion/argent

Create, record, edit, replay, or repair reusable Argent e2e test YAML files. Use when the user asks to record, replay, or run an e2e test or a repeatable device path, set up profiling or an A/B comparison, or invoke the authoring engine behind argent-qa-e2e. Also use before repeating three or more interactions. For one-off UI checks, acceptance-driven regression tests, or screen video, use argent-test-ui-flow, argent-qa-e2e, or argent-screen-recording respectively.

  • 1945 次安装
  • 3100 星标

安装命令

npx skills add https://github.com/software-mansion/argent --skill argent-create-e2e

SKILL.md

Create an Argent e2e test

An Argent e2e test is a replayable sequence in .argent/e2e/<name>.yaml (.argent/flows/ is still read).

For a saved QA test case, ticket, or acceptance criterion, load argent-qa-e2e first. It adds deterministic setup, acceptance evidence, and two-pass proof.

Read the relevant reference

  • Before creating or changing an e2e test, read Live authoring completely.
  • When polishing, composing, or manually reviewing YAML, read E2E YAML. For Vega, read its platform limits before recording remote or keyboard tools.
  • E2E tests run on physical iPhones (an iOS list-devices entry with kind "device"), but replay never auto-binds one, even when no simulator is booted: pass the phone's udid as device (CLI --device), and only a connected phone can run. pinch/rotate steps fail there like the live tools. On hardware the runner tree is the describe tree: same ids and roles, no UIView hierarchy. See argent-ios-device-interact for the hardware contract.
  • On capture warnings, raw coordinates, unavailable trees, mistimed transitions, overlays, or replay failures, read Reliability and recovery.

Non-negotiable rules

Create an Argent e2e test

An Argent e2e test is a replayable sequence in .argent/e2e/<name>.yaml (.argent/flows/ is still read).

For a saved QA test case, ticket, or acceptance criterion, load argent-qa-e2e first. It adds deterministic setup, acceptance evidence, and two-pass proof.

Read the relevant reference

  • Before creating or changing an e2e test, read Live authoring completely.
  • When polishing, composing, or manually reviewing YAML, read E2E YAML. For Vega, read its platform limits before recording remote or keyboard tools.
  • E2E tests run on physical iPhones (an iOS list-devices entry with kind "device"), but replay never auto-binds one, even when no simulator is booted: pass the phone's udid as device (CLI --device), and only a connected phone can run. pinch/rotate steps fail there like the live tools. On hardware the runner tree is the describe tree: same ids and roles, no UIView hierarchy. See argent-ios-device-interact for the hardware contract.
  • On capture warnings, raw coordinates, unavailable trees, mistimed transitions, overlays, or replay failures, read Reliability and recovery.

Non-negotiable rules