- Create smoke tests to check if a release is up and running.
- Schedule a HTTP request to keep Heroku instances up.
- Send a ping request to ensure a system is reachable.
- Automate data transfer between third party tools.
- Anything you can imagine.
Although Smokex can be consider as an HTTP request tool, it's main purpose is to create smoke tests and use them in the development workflow.
During our career, we faced the same question several times: how can we ensure we don't deploy a broken release? And the quick answer is, as always, you can't be sure of that. But you can minimize the impact by checking the correctness of your application and releases by running smoke tests periodically.