question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Spec reporter prints an incorrect summary

See original GitHub issue

Environment:

  • WebdriverIO version: 6.1.22
  • Mode: WDIO
  • If WDIO Testrunner, running sync/async: sync
  • Node.js version: 12.16.3
  • NPM version: 6.14.4
  • Browser name and version: Chrome 82
  • Platform name and version: Windows 10
  • Additional wdio packages used (if applicable): @wdio/spec reporter, @wdio/mocha-framework, wdio-chromedriver-service

Config of WebdriverIO Will provide that if below information is not sufficient.

Describe the bug Spec reporter prints an incorrect summary, e.g.: “Spec Files: 5 passed, 1 total (500% completed) in 00:01:02”

To Reproduce Given you have "scripts": {"test": "wdio"} in your package JSON and given the specs pattern matches multiple spec files and given you use a multiremote instance through chromedriver (not sure if that matters, though) then run npm test.

Expected behavior Spec reporter should print a correct summary like: “Spec Files: 5 passed, 5 total (100% completed) in 00:01:02”

Log

(Some names redacted.)

 "spec" Reporter:
------------------------------------------------------------------
[MultiremoteBrowser (unknown) #0-0] Spec: XXXXXXXXXX.spec.ts
[MultiremoteBrowser (unknown) #0-0] Running: MultiremoteBrowser on (unknown)
[MultiremoteBrowser (unknown) #0-0]
[MultiremoteBrowser (unknown) #0-0] XXXXXXXXXX
[MultiremoteBrowser (unknown) #0-0]    ✓ should XXXXXXXXXX
[MultiremoteBrowser (unknown) #0-0]    ✓ should XXXXXXXXXX
[MultiremoteBrowser (unknown) #0-0]    ✓ should XXXXXXXXXX
[MultiremoteBrowser (unknown) #0-0]    ✓ should XXXXXXXXXX
[MultiremoteBrowser (unknown) #0-0]    ✓ should XXXXXXXXXX
[MultiremoteBrowser (unknown) #0-0]
[MultiremoteBrowser (unknown) #0-0] 5 passing (4.9s)
[MultiremoteBrowser (unknown) #0-0]
[MultiremoteBrowser (unknown) #0-0] 
[MultiremoteBrowser (unknown) #0-0] 
------------------------------------------------------------------
[MultiremoteBrowser (unknown) #0-1] Spec: XXXXXXXXXX.spec.ts
[MultiremoteBrowser (unknown) #0-1] Running: MultiremoteBrowser on (unknown)
[MultiremoteBrowser (unknown) #0-1]
[MultiremoteBrowser (unknown) #0-1] XXXXXXXXXX
[MultiremoteBrowser (unknown) #0-1]    ✓ should XXXXXXXXXX
[MultiremoteBrowser (unknown) #0-1]    ✓ should XXXXXXXXXX
[MultiremoteBrowser (unknown) #0-1]
[MultiremoteBrowser (unknown) #0-1] 2 passing (2.2s)
[MultiremoteBrowser (unknown) #0-1]
[MultiremoteBrowser (unknown) #0-1] 
[MultiremoteBrowser (unknown) #0-1] 
------------------------------------------------------------------
[MultiremoteBrowser (unknown) #0-2] Spec: XXXXXXXXXX.spec.ts
[MultiremoteBrowser (unknown) #0-2] Running: MultiremoteBrowser on (unknown)
[MultiremoteBrowser (unknown) #0-2]
[MultiremoteBrowser (unknown) #0-2] XXXXXXXXXX
[MultiremoteBrowser (unknown) #0-2]    ✓ should XXXXXXXXXX
[MultiremoteBrowser (unknown) #0-2]
[MultiremoteBrowser (unknown) #0-2] 1 passing (4.2s)
[MultiremoteBrowser (unknown) #0-2]
[MultiremoteBrowser (unknown) #0-2] 
[MultiremoteBrowser (unknown) #0-2] 
------------------------------------------------------------------
[MultiremoteBrowser (unknown) #0-3] Spec: XXXXXXXXXX.spec.ts
[MultiremoteBrowser (unknown) #0-3] Running: MultiremoteBrowser on (unknown)
[MultiremoteBrowser (unknown) #0-3]
[MultiremoteBrowser (unknown) #0-3] XXXXXXXXXX
[MultiremoteBrowser (unknown) #0-3]    ✓ should XXXXXXXXXX
[MultiremoteBrowser (unknown) #0-3]    ✓ should XXXXXXXXXX
[MultiremoteBrowser (unknown) #0-3]    ✓ should XXXXXXXXXX
[MultiremoteBrowser (unknown) #0-3]
[MultiremoteBrowser (unknown) #0-3] 3 passing (29s)
[MultiremoteBrowser (unknown) #0-3]
[MultiremoteBrowser (unknown) #0-3] 
[MultiremoteBrowser (unknown) #0-3] 
------------------------------------------------------------------
[MultiremoteBrowser (unknown) #0-4] Spec: XXXXXXXXXX.spec.ts
[MultiremoteBrowser (unknown) #0-4] Running: MultiremoteBrowser on (unknown)
[MultiremoteBrowser (unknown) #0-4]
[MultiremoteBrowser (unknown) #0-4] XXXXXXXXXX
[MultiremoteBrowser (unknown) #0-4]    ✓ should XXXXXXXXXX
[MultiremoteBrowser (unknown) #0-4]
[MultiremoteBrowser (unknown) #0-4] 1 passing (4.8s)
[MultiremoteBrowser (unknown) #0-4]
[MultiremoteBrowser (unknown) #0-4] 
[MultiremoteBrowser (unknown) #0-4] 


Spec Files:	 5 passed, 1 total (500% completed) in 00:01:02 

Additional context Excerpt from package.json:

  "scripts": {
    "test": "wdio"
  },
  "devDependencies": {
    "@types/mocha": "^7.0.2",
    "@types/node": "^12.12.47",
    "@wdio/cli": "^6.1.22",
    "@wdio/local-runner": "^6.1.22",
    "@wdio/mocha-framework": "^6.1.19",
    "@wdio/spec-reporter": "^6.1.14",
    "@wdio/sync": "^6.1.14",
    "chai": "^4.2.0",
    "chromedriver": "^83.0.0",
    "ts-node": "^8.10.2",
    "tsconfig-paths": "^3.9.0",
    "typescript": "^3.9.5",
    "wdio-chromedriver-service": "^6.0.3"
  }

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:9 (9 by maintainers)

github_iconTop GitHub Comments

1reaction
cjatkinsoncommented, Jul 8, 2020

Investigating this issue.

0reactions
christian-bromanncommented, Jul 28, 2021

Ok, reviewing this issue it seems that the test uses Multiremote. This means all test have been running sequentially, not in parallel. This is why the spec reporter prints out total: 1 because there was only 1 worker active. I will close this but happy to discuss options how we can change wording to avoid such confusion.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Spec Reporter
A WebdriverIO plugin to report in spec style.
Read more >
Jasmine-spec-reporter: How to disable "Expected ...
Is it possible to configure the "jasmine-spec-reporter" to NOT display the Expected description of a failed spec. For instance, in the output below,...
Read more >
Karma-spec-reporter
Test reporter, that prints detailed results to console (similar to mocha's spec reporter). Usage. To use in your own Node.js project, just execute...
Read more >
wdio/spec-reporter - npm Package Health Analysis
Learn more about @wdio/spec-reporter: package health score, popularity, security, maintenance, versions and more.
Read more >
reporter.pdf
verbose. Whether to print in verbose form. Default is FALSE. Value. The plot spec, invisibly. See Also create_plot function to create a plot...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found