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.

The default "yarn test" command runs ALL tests 3 times

See original GitHub issue


On my machine, when I run yarn test, or yarn test --silent, all tests execute 3 times. The desired behavior, since this actually executes ember exam --split=3 --weighted --parallel would be that 3 partitions would run, each running a fraction of the tests. In addition to that, the 3 partitions run consecutively, not in parallel.

This seems to be related to and, following the conversations there and adding parallel: -1 to testem.js seems to cause the partitions to execute in paralel, but each partition still runs all of the tests in the suite.

Issue Analytics

  • State:open
  • Created 6 years ago
  • Comments:5 (5 by maintainers)

github_iconTop GitHub Comments

joshsmithcommented, Sep 14, 2017

Then we can just amend ember-try.json to use ember exam only. No need for docs IMO.

begedincommented, Sep 14, 2017

It’s not a matter of speeding up for me, since I use ember exam anyway.

It’s a matter of there being a “default” command (yarn test) which runs 3x slower than it should, due to a bug that doesn’t originate from us.

I’m thinking something like

  • yarn test should just execute ember exam instead of ember exam --split=3 --weighted --parallel
  • add some docs pointing the user on how they might try to speed it up by enabling parallelism, with a note that it may be buggy
Read more comments on GitHub >

github_iconTop Results From Across the Web

Fix CLI test failure — always fails on first test run #894 - GitHub
The cli tests are always failing on the first test run. ... lerna info Executing command in 3 packages: "yarn run test" @blitzjs/cli:...
Read more >
yarn test: all tests passed but returned "error Command failed ...
Answer: the error code was due to line coverage being below the value that I defined (90%). It already told me line coverage...
Read more >
Jest CLI Options
Run all tests (default):. jest. Run only the tests that were specified with a pattern or filename: jest my-test #or jest path/to/my-test.js.
Read more >
yarn test
Runs the test script defined by the package. ... If you have defined a scripts object in your package, this command will run...
Read more >
Make Your Jest Tests up to 20% Faster by Changing a Single ...
By default, Jest will run on all available CPU threads, ... 5.861 s 3 runs Benchmark #4: npm test -- --maxWorkers=50% Time (mean...
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 Post

No results found

github_iconTop Related Hashnode Post

No results found