chore: test refactoring to use separate environments per spec#125
Open
msuperina wants to merge 4 commits intoScottLogic:masterfrom
msuperina:test-refactoring
Open
chore: test refactoring to use separate environments per spec#125msuperina wants to merge 4 commits intoScottLogic:masterfrom msuperina:test-refactoring
msuperina wants to merge 4 commits intoScottLogic:masterfrom
msuperina:test-refactoring
Conversation
ryanggrey
approved these changes
Aug 9, 2018
oriondean
force-pushed
the
master
branch
2 times, most recently
from
931604b to
1133aac
Compare
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
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.
This is a first attempt to have tests in a bdd style with an environment injected at will (like in the beforeAll / beforeEach hooks).
Some commands are tagged as "setup". At the moment it is assumed that there is only one "not setup" command per test, but this can change in the future. This will need refactoring, as a setup command will become a "setup" for the closest previous "not setup" command.