Refactoring address-book.spec.js to use fixtures#10804
Merged
NiranjanaBinoy merged 2 commits intodevelopfrom Apr 3, 2021
Merged
Refactoring address-book.spec.js to use fixtures#10804NiranjanaBinoy merged 2 commits intodevelopfrom
NiranjanaBinoy merged 2 commits intodevelopfrom
Conversation
Contributor
|
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
Collaborator
Builds ready [e41d47c]
Page Load Metrics (550 ± 49 ms)
|
Collaborator
Builds ready [29d47dd]
Page Load Metrics (550 ± 47 ms)
|
Gudahtt
approved these changes
Apr 2, 2021
Member
Gudahtt
left a comment
There was a problem hiding this comment.
LGTM! I like where you chose to split the tests up, that worked out well
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 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.
Fixes: #10798
Explanation:
itparts first part adds a new address and second uses an existing address entry, first one is re-usingimported-accountand a new state.json is added totest/e2e/fixtures/address-entrywhich is used in the second scenario.