webdriverio/webdriverio

[馃挕 Feature]: provide a richer return interface for the launcher

Open

#11,909 opened on Dec 20, 2023

View on GitHubContributor guide
聽(3 comments)聽(3 reactions)聽(0 assignees)JavaScript聽(1,793 forks)batch import
Idea 馃挕help wanted

Repository metrics

Stars
聽(6,029 stars)
PR merge metrics
聽(Avg merge 15d 15h)聽(48 merged PRs in 30d)

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

Research direction
Review the current launcher implementation in the WDIO CLI, design a structured return object including test summary statistics, and update the smoke tests to verify the new output.
Tech stack
javascript
Domain
backendclitesting
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.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitNode.jsJavaScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40