webdriverio/webdriverio

[馃挕 Feature]: Ability to set the test status from the afterTest hook

Open

#14314 opened on Mar 24, 2025

View on GitHub
聽(2 comments)聽(1 reaction)聽(0 assignees)JavaScript聽(6,029 stars)聽(1,793 forks)batch import
Idea 馃挕help wanted

Description

Is your feature request related to a problem?

I would like to be able to set the status of a test from the afterTest hook. In some cases it makes sense to do a check at the end of a test to determine if the test failed. For instance, checking the browser console log to see if any errors happened during test execution.

Describe the solution you'd like.

An easy way to set the status of a test from the afterTest hook, possibly just by changing the result object?

Describe alternatives you've considered.

No response

Additional context

Currently this does not seem possible (at least with Mocha). You can not change the test status after the test has already finished. There seems to be an option that does somewhat what I am looking for, which is calling the context.test.callback method. This does cause the test to fail, but with the "wrong" reason that the done method is called twice. It also has the problem that when a test is retried after a failure and then passes, the test runner process will still exit with an error even though all tests are green.

Code of Conduct

  • I agree to follow this project's Code of Conduct

Contributor guide

Tech stack
javascriptnodejs
Domain
testing
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Knowledge of WebdriverIO hooksUnderstanding of Mocha test lifecycle
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Investigate how to set test status in the afterTest hook. The issue mentions using `context.test.callback` from Mocha, but it causes duplicate 'done' calls. Look at WebdriverIO's runner/reporter code (e.g., `packages/wdio runner/src/index.js`, `packages/wdio reporter/src/index.js`) and Mocha's test object to find a proper way to override or set the result status without side effects. Check if there are any existing capabilities to modify the test result object in afterTest.