webdriverio / webdriverio/webdriverio
[💡 Feature]: provide a richer return interface for the launcher
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 9.8k
- Forks
- 2.7k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 69
Description
Is your feature request related to a problem?
Currently we only return the exitCode when starting the WDIO CLI Launcher programmatically.
Describe the solution you'd like.
A user might have iterest in more information, e.g.
- number of passing, failing, retried tests
- duration of test run
- what else?
Let's also update the smoke tests were we had to scan some log files to get these information.
Describe alternatives you've considered.
n/a
Additional context
This is a breaking change, so scheduling it for v9 release.
Code of Conduct
- I agree to follow this project's Code of Conduct
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the programmatic WDIO CLI Launcher return path and reviewing the smoke tests that currently scan log files for run information. Define the richer result interface and replace those log scans; done means callers can access the agreed test counts and duration directly, with the updated smoke tests passing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- cli, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100