(@wdio/runner): support assertion hooks#11714
Merged
christian-bromann merged 3 commits intomainfrom Nov 23, 2023
Merged
Conversation
71de4ca to
fa45094
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
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.
Proposed changes
With
v4.6.0ofexpect-webdriveriowe start to support hooks for assertions. This PR integrates this feature to the WebdriverIO test runner. It integrates it in a way that also allows reporter to use the data.Here is an example:
Given you have the following hooks in your
wdio.conf.js:and in your tests you have an assertion like this:
Then it will log the following data:
Types of changes
Checklist
Further comments
n/a
Reviewers: @webdriverio/project-committers