Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No progress messages when imposing sequential tests in jest 26.5.3 #10646

Closed
doberkofler opened this issue Oct 19, 2020 · 3 comments
Closed

No progress messages when imposing sequential tests in jest 26.5.3 #10646

doberkofler opened this issue Oct 19, 2020 · 3 comments

Comments

@doberkofler
Copy link

doberkofler commented Oct 19, 2020

🐛 Bug Report

I'm trying to use test in my end-to-end test suite using the selenium web driver.
For the end-to-end testing it is necessary to execute the tests sequentially and one by one.
The correct sequence is enforced by using the testSequencer: './testSequencer.js' configuration option and the maxWorkers: 1 configuration option and this works as expected.

Unfortunately jest does no longer show the progress message all and this would be extremely helpful especially when running the quite slow selenium tests.

The problem seems to be related to the maxWorkers: 1 configuration option.

To Reproduce

Use the maxWorkers: 1 configuration option.

Expected behavior

Show the progress message as usual.

Link to repl or repo (highly encouraged)

verbose.zip

envinfo

  System:
    OS: macOS 10.15.7
    CPU: (8) x64 Intel(R) Core(TM) i7-8559U CPU @ 2.70GHz
  Binaries:
    Node: 14.13.0 - ~/.nvm/versions/node/v14.13.0/bin/node
    npm: 6.14.8 - ~/.nvm/versions/node/v14.13.0/bin/npm
@julianYaman
Copy link

I'm also experiencing the same issue with using playwright and the -runInBand option.
Is there already a fix for this to show the test progress? I looked into #6616, and it didn't work out for me, sadly.

@jeysal
Copy link
Contributor

jeysal commented Nov 10, 2022

Duplicate of #9420

@jeysal jeysal marked this as a duplicate of #9420 Nov 10, 2022
@jeysal jeysal closed this as not planned Won't fix, can't repro, duplicate, stale Nov 10, 2022
@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 11, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants