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.

tomevault-io Updated

File contents

End-to-end tests

Instructions

When you are done making changes, run all end-to-end tests through this command:

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 — distributed by TomeVault.

tomevault-io/skills-registry/tree/main/git-town--git-town--git-town commit 4e2279593a

Frequently asked questions

npx skillmds@latest add tomevault-io/end-to-end-tests