# End To End Tests

> after making changes, run end-to-end tests to ensure that the product still works

- Skill: `git-town/end-to-end-tests` (Agent Skill)
- Install (CLI): `npx skillmds@latest add git-town/end-to-end-tests`
- Raw SKILL.md: https://api.skillmd.com/api/skills/git-town/end-to-end-tests/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: git-town (https://skillmd.com/u/git-town)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/git-town/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