Integration tests #3206
Merged
Integration tests #3206
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gustavosbarreto
force-pushed
the
topic/integration-tests
branch
4 times, most recently
from
06a6b0a
to
cee00b4
Compare
gustavosbarreto
force-pushed
the
topic/integration-tests
branch
6 times, most recently
from
d223418
to
0f41be3
Compare
gustavosbarreto
force-pushed
the
master
branch
3 times, most recently
from
c01e294
to
b2d4214
Compare
gustavosbarreto
force-pushed
the
topic/integration-tests
branch
from
0f41be3
to
24a1b6b
Compare
gustavosbarreto
force-pushed
the
topic/integration-tests
branch
2 times, most recently
from
97e8b21
to
7971af3
Compare
heiytor
force-pushed
the
topic/integration-tests
branch
3 times, most recently
from
afafba0
to
627d93f
Compare
heiytor
force-pushed
the
topic/integration-tests
branch
3 times, most recently
from
63f16b9
to
2ea57f3
Compare
The environment framework provides an easy way to create, manage and destroy ShellHub instances. with Docker Compose. Internally, it uses `testcontainers-go` to manage services. To get started, call `New`, which creates a new `DockerComposeConfigurator`. A configurator is a helper struct to manage "docker-composes". By default, a new configurator reads from `.env` to set up all environment variables. To avoid boilerplate between test cases a clone of a configurator can be made; a clone has the same data as the original configurator but is an isolated pointer. Every configurator is associated with a `testing.T`, which is used to make standard assertations. To start the instance, you can call `DockerComposeConfigurator.Up`, which returns a `DockerCompose`. A Docker Compose is a code representation of the running instance; it also has a `DockerCompose.Down` method, which stops and cleans up all allocated resources for the instance. Generally, it is passed to `testing.T.Cleanup`. The running instance provides helper methods to facilitate docker-compose manipulation and comunication. It also provides helper methods for generic pipelines (e.g., creating a user).
heiytor
force-pushed
the
topic/integration-tests
branch
from
2ea57f3
to
6a769df
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR implements the initial phase of our integration testing efforts using Testcontainers.
The approval of this PR depends on the completion of the following tasks: