end-to-end-tests

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.

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.

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.

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.

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`.

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.