Fix deprecated usage of isFalsy() / isTruthy() methods in E2E tests
#3294
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
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.
Platforms Impacted
Description of changes
Currently, some E2E test cases spit out error messages by passing them in the
.isFalsy()or.isTruthy()methods. Per webdriverio, this usage is deprecated. The correct usage is passing the error message into the.withContext(msg)method, before checking for falsiness/ truthiness. This PR removes all deprecated usages of.isFalsy()/.isTruthy(), replacing it with.withContext().Verification
Tests pass / builds locally.
Pull request checklist
This PR has considered (when applicable):