Skip to content
Agentmart
Submit a tool

e2e-test-engineering

Design and implement focused end-to-end tests against configured disposable environments.

Skill by MarkoArsov

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/markoarsov-e2e-test-engineering

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Design and implement focused end-to-end tests against configured disposable environments.

Use cases: design, testing

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found
Runs as
Python package

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/e2e-test-engineering

What's inside

Skill name
e2e-test-engineering
Description
Design and implement focused end-to-end tests against configured disposable environments.
License
MIT
Instructions
18 lines in SKILL.md · view on GitHub

Before installing

  • Ships executable scripts

Files (2)

  • SKILL.md
  • resolve.py · scripts/

SKILL.md (first lines)

<!-- resolver:start -->
Run this skill folder's scripts/resolve.py from the active project once. If it returns a different effective skill, follow that file instead. Otherwise continue below. Use the selected package's bin/agentflow for commands.
<!-- resolver:end -->

# e2e test engineering

1. Read the project's E2E reference, existing tests, environment lifecycle, data boundaries, and accepted behavior.

2. Choose the smallest representative flow and assertions that test externally visible behavior. Use established fixtures/selectors and explicit readiness checks.

3. Use a disposable local environment by default. Confirm any staging/production side effects and cleanup before performing them.

4. Run a named file or scenario, not an entire expensive suite by habit. Obtain meaningful red then green evidence when adding behavior tests.

5. Avoid fixed sleeps, destructive shared-data mutation, skipped assertions, and permanent environment workarounds. Record cleanup and reproducible commands.

From MarkoArsov/agent-workflow, MIT.

More from MarkoArsov/agent-workflow

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Sep 28, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from MarkoArsov

Cite this page

e2e-test-engineering skill. Agent Mart. https://agentmart.dev/skills/markoarsov-e2e-test-engineering (last updated 2026-10-24)