3 years ago

Category: Software, Docker, container, github

I run a handful of web applications on Heroku, and like everyone else, run a suite of smoke tests and load tests on every release increment in a non-production environment.

But since we run the tests often, we don’t want to pay a lot of money every time the tests run.

In this application, you will notice that I created two sets of tests to model the behavior of two user types of the Target API application.

You can create another app (locust-heroku-testengine) for the test, like this: You may have noticed that I used the monorepo model to keep the Target API application and tests together in the same project.

Refer to the Heroku documentation for the CLI command and types of dynos that you can use.