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

jest --verbose only prints the tests names after all tests had run #9979

Closed
evandrocoan opened this issue May 5, 2020 · 2 comments
Closed

Comments

@evandrocoan
Copy link

🐛 Bug Report

https://repl.it/@evandrocoan/GlossyLustrousFields

function sleep(ms) {
  return new Promise(resolve => setTimeout(resolve, ms));
}

describe("--verbose does not print each test run", () => {
  test('Running test 1...', async () => { await sleep(2000); expect(3).toBe(3); });
  test('Running test 2...', async () => { await sleep(2000); expect(3).toBe(3); });
  test('Running test 3...', async () => { await sleep(2000); expect(3).toBe(3); });
  test('Running test 4...', async () => { await sleep(2000); expect(3).toBe(3); });
  test('Running test 5...', async () => { await sleep(2000); expect(3).toBe(3); });
  test('Running test 6...', async () => { await sleep(2000); expect(3).toBe(3); });
  test('Running test 7...', async () => { await sleep(2000); expect(3).toBe(3); });
  test('Running test 8...', async () => { await sleep(2000); expect(3).toBe(3); });
  test('Running test 9...', async () => { await sleep(2000); expect(3).toBe(3); });
  test('Running test 10...', async () => { await sleep(2000); expect(3).toBe(3); });
  test('Running test 11...', async () => { await sleep(2000); expect(3).toBe(3); });
  test('Running test 12...', async () => { await sleep(2000); expect(3).toBe(3); });
});

Expected behavior

jest --verbose --runInBand

Print: ✓ Running test 1... after running test 1

Print: ✓ Running test 2... after running test 2

Print: ✓ Running test 3... after running test 2

...

Actual behavior

jest --verbose --runInBand

Prints at once all tests run after running all tests:

    ✓ Running test 1... (2026ms)
    ✓ Running test 2... (2015ms)
    ✓ Running test 3... (2004ms)
    ✓ Running test 4... (2003ms)
    ✓ Running test 5... (2056ms)
    ✓ Running test 6... (2095ms)
    ✓ Running test 7... (2006ms)
    ✓ Running test 8... (2006ms)
    ✓ Running test 9... (2002ms)
    ✓ Running test 10... (2005ms)
    ✓ Running test 11... (2003ms)
    ✓ Running test 12... (2008ms)

envinfo

 npx envinfo --preset jest
npx: installed 1 in 2.984s

  System:
    OS: Linux 4.15 Debian GNU/Linux 9 (stretch) 9 (stretch)
    CPU: (4) x64 Intel(R) Xeon(R) CPU @ 2.30GHz
  Binaries:
    Node: 12.16.3 - /usr/local/bin/node
    Yarn: 1.22.4 - /usr/local/bin/yarn
    npm: 6.14.4 - /usr/local/bin/npm
  npmPackages:
    jest: ^24.9.0 => 24.9.0 
@SimenB
Copy link
Member

SimenB commented May 6, 2020

Will be fixed by #6616

@SimenB SimenB closed this as completed May 6, 2020
@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 May 11, 2021
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

2 participants