There are plenty of free APIs you can use for learning - https://github.com/toddmotto/public-apis/ More on reddit.com

Not sure what language/library you're using, but I'll suggest something for Python/discord.py just in case you're using what I am using. I was also pretty surprised to find a relative lack of testing tools / information around such a well-known library. It does pretty much come down to three options AFAIK: Your strategy of making additional bots on a test server Separating the logic/working code into tests that do not rely on the discord API and testing those and trying to make the discord part as straightforward and bug-free as possible so you can test manually or with other bots There is a library called dpytest. It is in ALPHA, and lacks basically any meaningful documentation (understandably, since it is in alpha). It took me some decent chunk of time, but I eventually got it working with my bot and have been building up a test suite that is able to mock the discord API. It feels great to have the tests, not gonna lie. But it was a pain, and the library is missing features and whatnot. Or someone else might have further suggestions; this has just been my experience so far :) More on reddit.com

I'm afraid I don't know of any approach that does not involve some amount of elbow grease.

Setting up hasura and postgres instances as part of test execution pipeline is exactly how the integration test suite of Hasura itself works.

Whether it'll work for you depends on what trade-offs you're willing to make and what you want to get out of your test suite.

If you just want to run your unit tests in CI, I'd suggest you start a single hasura instance and postgres instance via e.g. docker containers and then reset their state data between each test. This doesn't let you run tests in parallel, but it does let you pay the cost of instance startup and initialization only once. This is more or less what Hasura's own test suite does.

If your test execution is more resource constrained (either in terms of computational resources or time in a dev feedback loop, etc.) and your tests are deterministic, you could try using contract testing in your test harness (https://pactflow.io/blog/what-is-contract-testing/). Then you'll only need to have a hasura instance in the loop when you introduce new tests or update existning ones.

More on reddit.com

Postman can do that with mock servers https://learning.postman.com/docs/designing-and-developing-your-api/mocking-data/setting-up-mock/ More on reddit.com