feat: use zendro-env to setup integration tests environment#158
Merged
feat: use zendro-env to setup integration tests environment#158
Conversation
- service url for service connection checks - mocha test definitions
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Issue
Closes #156
Describe
This PR addresses concerns about having two separate and independently evolving integration test environments in the
graphql-server-model-codegenandsingle-page-app-codegenrepositories.The integration test environment is now managed by the
zendro-envutility.Changes
zendro-envdev dependencytest-integrationscript inpackage.jsonto use the new tooltest-envfor more advanced usage of the tool.dockerfolder with theintegration_test_miscfolder insidetestsBlocks
None. But this branch needs to be updated with the latest
masterchanges.