Unrecognised test
See original GitHub issueHello, there!
I use latest versions of webdriverio and wdio-mocha-framework and recently I started to get a nasty error:
/Users/sullenor/Documents/repo/yharnam/node_modules/webdriverio/build/lib/utils/ReporterStats.js:269
throw Error('Unrecognised test [' + title + '] for suite [' + runner.parent + ']');
^
Error: Unrecognised test [XXX] for suite [YYY]
at Error (native)
at ReporterStats.getTestStats (/Users/sullenor/Documents/repo/yharnam/node_modules/webdriverio/build/lib/utils/ReporterStats.js:269:23)
at ReporterStats.testFail (/Users/sullenor/Documents/repo/yharnam/node_modules/webdriverio/build/lib/utils/ReporterStats.js:315:34)
at BaseReporter.<anonymous> (/Users/sullenor/Documents/repo/yharnam/node_modules/webdriverio/build/lib/utils/BaseReporter.js:138:25)
at emitOne (events.js:90:13)
at BaseReporter.emit (events.js:182:7)
at BaseReporter.handleEvent (/Users/sullenor/Documents/repo/yharnam/node_modules/webdriverio/build/lib/utils/BaseReporter.js:278:27)
at Launcher.messageHandler (/Users/sullenor/Documents/repo/yharnam/node_modules/webdriverio/build/lib/launcher.js:469:28)
at emitTwo (events.js:100:13)
at ChildProcess.emit (events.js:185:7)
The error itself occurs in the before hook and wdio tries to get test stats for the suite, which doesn’t exist in the suiteStats.tests
object.
I checked manually and looks like changing const title = runner.currentTest || runner.title
to const title = runner.title || runner.currentTest
helps here (https://github.com/webdriverio/webdriverio/blob/master/lib/utils/ReporterStats.js#L165), but I am not sure, that it’s a proper solution.
I wonder if you can check this?
Issue Analytics
- State:
- Created 7 years ago
- Reactions:2
- Comments:33 (12 by maintainers)
Top Results From Across the Web
Unknown Test Status - Kaseya HelpDesk
In Traverse, tests can enter an Unknown test status for several reasons: When a new test is created, it is added to the...
Read more >Pytest - testing parser Error : Unrecognised arguments
The problem comes from the parser.parse_args call which accepts an optional args argument. If this argument is not provided, args are taken ...
Read more >Fever of Unknown Origin (FUO) - Infectious Diseases
Medical records are checked for previous test results, particularly those that effectively rule out certain disorders. Physical examination. The general ...
Read more >Pulmonary function tests reveal unrecognised lung ... - PubMed
Pulmonary function tests reveal unrecognised lung dysfunction and have independent prognostic significance in patients with systemic AL ...
Read more >[BUG] Unknown test(s) in worker #14425 - GitHub
When running parameterized tests with randomly generated names using faker library tests are failing with the error "Unknown test(s) in ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
has anyone managed to patch the ReporterStats.js file to fix this temporarily?
I’m still seeing this when, just like #2494, an error occurs in a test hook.