I’m using Dgraph as the core database within an application I’m working on but I’d like to first tinker with unit/integration tests. For the former, I’ll be constructing mocks using interfaces (since I’m using the Go client) but for the latter, I’d like to have as minimal Dgraph resources running as possible for the duration of the tests. Is there a recommended way to handle this? I wasn’t able to get a clear understanding from the running tests section of the README for the Go client.
What is the best way to check that the Dgraph instance has fully launched and stabilized programmatically? For example, I run this command from the tutorial:
After that runs in my setup script, I’d like to update the schema, load data, etc. What’s the best way to make sure that the instance has launched and is running before trying to begin updating data?