after making changes, run end-to-end tests to ensure that the product still works
The 'end-to-end-tests' skill is designed to ensure that the product maintains its functionality after changes are made. It allows developers to run a suite of comprehensive tests to verify that the system still works as expected, covering the full scope of the application from start to finish. This skill helps identify regressions or broken functionality that might have been introduced during development, thereby improving code quality and maintaining product reliability.
You can run all the end-to-end tests by executing the command 'make cuke' in the terminal.
If the tests fail with exit code 1, read the error messages, fix the errors, and re-run the tests until they pass with exit code 0.
Yes, you can run a specific test by tagging the scenario with '@debug @this' and then executing 'make cukethis' to run only the tagged scenario.
This skill supports Go and uses Cucumber for Go to execute the tests.
The 'features' folder contains the Gherkin-language written end-to-end tests, which define the scenarios to be executed.
Quick Setup:
.claude/skills/Repository
git-town/git-town