- name
SKILL.md
스킬 파일은 게시자의 저장소에 그대로 있습니다.
복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add testdino-hq/playwright-skill --skill e2e-testdino -a cursor -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add testdino-hq/playwright-skill --skill e2e-testdino -a claude-code -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add testdino-hq/playwright-skill --skill e2e-testdino -a codex -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add testdino-hq/playwright-skill --skill e2e-testdino -a grok -y복사한 메시지를 Grok Bot 채팅에 보냅니다. Bot이 GitHub에서 이 SKILL.md를 가져와 모든 Bot이 공유하는 스킬에 추가합니다.
Install this skill: https://github.com/testdino-hq/playwright-skill/tree/HEAD/e2e-testdino게시자 제공
The e2e skill ends at the edge of the machine that ran the tests. This pack starts there.
8 guides for the part of an e2e suite that happens after npx e2e run exits: results from CI, evidence you can fetch from another machine, history across runs, merged shards, quarantine, verified fixes, and what agent steps cost over time.
Verified against e2e 0.23.0 and @testdino/e2e 1.1.0. Check the project with npm ls e2e @testdino/e2e.
e2e ships its own skill, and it is the reference for everything the runner does. This pack never restates it.
Three checks decide which guides can work in this project:
testdino() in the reporters of e2e.config.ts. If it is missing, start with results-and-artifacts.md.health tool. It returns the projectId every other tool needs. Not connected: claude mcp add testdino --env TESTDINO_PAT=<token> -- npx -y @testdino/mcp@latest for Claude Code, or the same command and env under mcpServers in .cursor/mcp.json. The token is a Personal Access Token from TestDino's User Settings. Ask the user before adding a server or a token.@testdino/e2e 1.1.0 or later. Trace pages, app logs and visual comparison need e2e 0.19.0 or later.agent.act or --shard goes stale the day e2e ships a release.--repeat-each 10 --no-cache send every agent step to the model ten times.TESTDINO_CI_RUN_ID.testdino-e2e run, with a reason and an end date. Under plain npx e2e run a quarantined test still fails the build.verify_fix takes that run as the baseline. Passing only after a retry is unstable, not fixed.list_testcase; never build or guess one.Say so plainly when a user asks for one of these, and use the fallback:
Screenshots and recordings leave the CI machine when the reporter uploads them. e2e masks secure fields in screenshots and redacts configured secrets in text, but a value the app shows anywhere else is in the image, and videos are not masked. The reporter itself removes only user names, passwords, query strings and fragments from page addresses (the page at failure and every address in app log lines) and credentials from the Git remote. Error text, step titles, test console output, screenshots, videos and trace pages are sent as e2e wrote them. It also sends the CI machine's hostname, OS, CPU, memory and Node version. Run uploaded suites with test accounts and throwaway data, or set artifacts: false on the reporter.
Evidence links from TestDino expire within minutes by design. Download what you need when you receive it and never paste a signed link into an issue, a pull request or a chat.
When this pack misleads you, or a guide names a tool, option or message that no longer exists, tell the user and offer to open an issue at https://github.com/testdino-hq/playwright-skill/issues with the guide name and the e2e and @testdino/e2e versions. When a TestDino tool returns something wrong for an e2e run, offer the same with the tool name and the run id, never with app content. Problems with e2e itself go to the e2e team through npx e2e feedback, as the e2e skill describes.
@testdino/e2e documentation, TestDino MCP tools referenceWhat to do after a run of e2e, the agentic test runner from e2e.com (`e2e.config.ts`, `*.e2e.ts` files, `agent.act` steps), leaves the machine it ran on. Not for Playwright runs. Use when an e2e test
---name: e2e-testdinodescription: What to do after a run of e2e, the agentic test runner from e2e.com (`e2e.config.ts`, `*.e2e.ts` files…---# e2e-testdino/SKILL.md개요
What to do after a run of e2e, the agentic test runner from e2e.com (`e2e.config.ts`, `*.e2e.ts` files, `agent.act` steps), leaves the machine it ran on. Not for Playwright runs. Use when an e2e test failed in CI and its trace page is not in the local `.e2e/` folder, when deciding from run history whether an e2e test is flaky or broken, when quarantining a failing e2e test or checking that a fix held, when sharded e2e jobs need to show as one run, when agent steps cost more than expected or stopped replaying from the cache, when a device run's recording or an explore or bug bash finding needs a shared home, or when linking e2e tests to test cases. Results reach TestDino through the `@testdino/e2e` reporter and are read back over the TestDino MCP server. To write, run or fix an e2e test locally, use the e2e skill instead.
FAQ
게시자에게서 e2e-testdino/SKILL.md를 다운로드하거나 경로를 복사해 저장소를 엽니다. PlugMCP는 스킬을 목록에 올릴 뿐 파일을 호스팅하지 않습니다.
게시자가 https://github.com/testdino-hq/playwright-skill에서 관리합니다.
Claude, Cursor, Codex, Grok Build는 게시자의 저장소에서 추가한 SKILL.md를 읽을 수 있습니다. Grok Bot은 채팅에서 스킬의 GitHub 폴더 링크를 보내면 설치합니다.