godog VS Gauge

Quick side note - this is probably the subject of a whole other blog post but my current favourite way of testing CLI tools uses godog to write tests. It can be a little complex but I've found it supremely powerful. Here are some good examples of how I've approached it with layli and wait-for.

It's complaining about a file missing in $GOPATH/pkg... but I'm not sure how do I get the packages its asking for. Things I have tried: - running go mod tidy - running go get -u github.com/cucumber/godog (hoping it would add the files to pkg/mod/... - Uninstalled and installed Go again.

I also use BDD (Gherkin with godog in particular) to verify and document the expected behaviour of a product from an end user's perspective when needed. I usually do this when the product also contains untested code that I have no control over when I'm working on a problem - this gives me peace of mind over something I can't control while doubling as documentation.

It looks like it is not possible to share steps between scenario's or features. In https://github.com/cucumber/godog it is possible to share steps.

Differences between gherkingen and godog are:

Selenium is cool but https://gauge.org/ really cuts down on the boilerplate and is a lot more lightweight, may want to give it a look too

This actually reminds me a lot of Gauge from Thoughtworks: https://github.com/getgauge/gauge

It's typically paired with Taiko for test automation, but generally speaking it's a markdown to logical instruction engine.

I dig it, but also worth taking a look at what the Thoughtworks team has done especially around the VS Code tooling and language server work that they did to bring intellisense into their Markdown templates.

Since the project also uses Postgres, Redis, and AMQP, we also write integration tests. A docker compose file is there to stack up the test suite, and before each test, the tables, the keys, and the queues are reset. We don't try to aim to test for all the cases but usually all the controllers are covered. I personally would prefer to write more test cases between multiple micro services (e2e?) using something like Gauge but these integration tests are kind of enough.

Gauge looks interesting, but reminds me heavily of BDD frameworks - it looks like it's an abstraction layer where instead of writing Gherkin/GWT, the tests are in their specific DSL that's Markdown based?

Gauge is a Behavior Driven Java testing framework launched by ThoughtWorks.Inc. This is also one of the best Java Testing Frameworks, which allows software engineers to develop automated frameworks and speed up the software development procedure.