Refactor RPC tests #416
Merged
Refactor RPC tests #416
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
freignat91
force-pushed
the
test-in-one
branch
from
dea1fb5 to
f1b6fc9
Compare
freignat91
force-pushed
the
test-in-one
branch
from
c99acd2 to
184307c
Compare
ndegory
approved these changes
Nov 4, 2016
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.
Related to #410 and #301
This PR is a proposal (from Nicolas and me) presented in Mobilize topic: "Integration tests automation"
It groups all rpc tests in the api/rpc/tests folder and allow to execute them launching amplifier only one time.
Unitary tests and integration tests have been separated
test:
same with:
Then it's the base to be able to use them in a dedicated service (not in this PR) and so to be able to execute them in any swarm environments.
regression tests: