end-to-end-tests

Run Gherkin end-to-end tests via make and Cucumber for Go.

3.4k|161|Updated May 15, 2014

Search Tags:#testing #go #make #qa automation #end-to-end tests #cucumber

Ready to run

npx skills add https://github.com/git-town/git-town --skill end-to-end-tests

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: end-to-end-tests
Source: https://github.com/git-town/git-town/tree/main/.claude/skills/end_to_end_tests
Command: npx skills add https://github.com/git-town/git-town --skill end-to-end-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that after code changes, you can run end-to-end tests to verify the product still behaves correctly, catching regressions early and saving debugging time.

Core Features & Use Cases

Test Suite: Run the full end-to-end test suite to validate critical user flows.
Test Framework: Tests are written in Gherkin and executed using Cucumber for Go.
Targeted Debugging: If a test fails, re-run only the failing scenario with the @debug @this tag using make cukethis.

Quick Start

Run all end-to-end tests: make cuke If a test fails, use cukethis to run only a tagged scenario: make cukethis

Frequently Asked Questions about end-to-end-tests

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I run end-to-end tests on code changes?▼

End-to-end tests validate that your product behaves correctly after code changes. Run all tests with `make cuke`, which executes Gherkin-based feature files using Cucumber for Go. Exit code 0 signals success; failures indicate regressions to debug.

Can I re-run a single failing test scenario?▼

Yes. Tag the scenario with `@debug @this` and run `make cukethis` to execute only that test. This speeds up debugging by isolating the failure without running the full suite.

What do I need to set up end-to-end tests with Gherkin and Cucumber?▼

You need the make and go toolchain installed, feature files written in Gherkin syntax located in the features folder, and Cucumber for Go configured to execute them. The Skill handles running tests via make commands.

How do end-to-end tests catch regressions?▼

End-to-end tests run critical user flows after each code change, verifying the product still behaves as expected. Early detection of regressions saves debugging time and prevents broken features from reaching users.

Does this work with projects already using make and Go?▼

Yes. If your project has a make workflow and Go toolchain, you can integrate end-to-end tests by adding Gherkin feature files to the features folder and configuring Cucumber for Go to run via `make cuke`.

What happens if an end-to-end test fails?▼

A non-zero exit code signals test failure. Use `make cukethis` with `@debug @this` tags to re-run only the failing scenario and isolate the root cause without running the entire suite.