This repository was archived by the owner on Mar 27, 2025. It is now read-only.
Use build tags to separate functional and integration tests #277
Conversation
This file contains hidden or 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
Using the build tags "integration" and "functional" we separate the two class of tests.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
The purpose of this PR is to clearly separate the two classes of tests in the project.
Integration tests requires the interaction with an aws iot mqtt broker, while functional tests relies on a mqtt broker running in a docker container.
Using the build tags "integration" and "functional", respectively, we can clearly separate the code for the tests. Besides, we can run the proper global setup code (see
TestMaininhandlers_containers_functional_test.go) for the specific class of test we want to execute.