The Delinkcious smoke test is not an automated one. It can be, but it will require special setup to make it work in the CI/CD environment. For real-world production systems, I highly recommend that you have an automated smoke test (and other tests, too).
The code is in the cmd/smoke_test directory and consists of a single file, smoke.go. It exercises Delinkcious though the REST API that's exposed by the API gateway. We could write this test in any language because there is no client library. I chose to use Go for consistency and to highlight how to consume a raw REST API from Go, working directly with URLs, query strings, and JSON payload serialization. I also used the Delinkcious object model link as a convenient serialization ...
