Add e2e testing instructions to AGENTS.md#9429
Conversation
Document the full workflow for AI agents to set up, run, debug, and write Cypress e2e tests: - Integration test script (hack/run-integration-tests.sh) usage with --setup-only and --tests-only flags - All 14 test suites and their corresponding tags - Running individual Cypress tests by tag or feature file - Debugging Cypress tests via Playwright MCP over CDP - Pulling CI failure logs and screenshots with gh CLI - CI job name to test suite mapping - Writing new e2e tests with step definition patterns Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
This is good kickoff! Some things works good (bootstrapping env, running tests), but I need to do some more testing. Some things are too vague, I'm also unable to attach debugger. Can we create feature branch out of this? Also I'm exploring how to establish this more in a form of agent(s) (or sub-agents) that have narrow scope. |
What is vague? The goal is to be able to tell your agent to 1. Debug CI issues 2. Implement e2e tests for a feature. Testing 1. Can be done by checking out this branch and telling your agent to read the |
2 participants
Describe the change
Document the full workflow for AI agents to set up, run, debug, and write Cypress e2e tests.
Steps to test the PR
Checkout changes then ask your AI of choice to read the AGENTS file and debug a cypress e2e test or write a cypress e2e test for you.
Automation testing
N/A
Issue reference
N/A