# End To End Tests > after making changes, run end-to-end tests to ensure that the product still works Use when this capability is needed. - Skill: `tomevault-io/end-to-end-tests` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/end-to-end-tests` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/end-to-end-tests/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/end-to-end-tests --- # End-to-end tests ## Instructions When you are done making changes, run all end-to-end tests through this command: ```bash make cuke ``` If the exit code is 1, read the error messages and fix all errors, then re-run the end-to-end tests until they run successfully and exit with code 0. End-to-end tests are defined in the "features" folder. They are written in the Gherkin language and execute using Cucumber for Go. If an end-to-end test fails, you can re-run only this test to verify that your fix works: - Add the `@debug @this` tag to a specific scenario - Run `make cukethis` to execute only the tagged scenario - when the test passes, remove the `@debug @this` tags --- > Source: [git-town/git-town](https://github.com/git-town/git-town) — distributed by [TomeVault](https://tomevault.io).