HAhardwaresofton·Apr 26, 2021
With the advent of easy to use docker containers, this is really easy to do for most backing services, right on your machine during tests (and in CI).
If all your app needs is rabbitmq (or some queue), redis, and postgres you can run all of them in the background and give out databases/exchanges to your app as you see fit. This also does something interesting -- it turns you away from tools that don't do badly in containerized environments or who are hard to set up, which is a benefit in my mind. It also turns you away from proprietary cloud solutions that you can't run yourself (which isn't always possible but meh).
I trust my E2E tests a lot more when they're not built on mocking. I'm almost tempted to say that mocking is pointless in this world -- just test the real thing.
[EDIT] Since most people will know how to run redis/postgres/ra
Read the rest
bbitmq easily, one of the high value things is smtp testing. Here are a few projectsfor that:
- https://github.com/sj26/mailcatcher (https://mailcatcher.me)
- https://github.com/mailhog/MailHog
- https://github.com/maildev/maildev (http://maildev.github.io/maildev/)
- https://github.com/remko/smtp-http-proxy (this is more for turning SMTP into HTTP but it's cool)
- https://github.com/flashmob/go-guerrilla
Remember, for a lot of these projects don't be worried if you don't see updates for years -- once you've written a reasonably working SMTP server, it may not need to change much.
I might take one of these and try to build a MailTrap[0] competitor eventually. $10/month is twice the cost of a digital ocean droplet running one of these pieces of software (and I know that I can run the instances for even cheaper).
[0]: https://mailtrap.io/pricing/