How to run Jest tests with Yarn without any prompts?

Question

I am trying to run my Jest unit tests in Team City but I always end up getting the prompt as shown below.

No tests found related to files changed since last commit.
Press `a` to run all tests, or run Jest with `--watchAll`.

Watch Usage
 › Press a to run all tests.
 › Press f to run only failed tests.
 › Press p to filter by a filename regex pattern.
 › Press t to filter by a test name regex pattern.
 › Press q to quit watch mode.
 › Press Enter to trigger a test run.

I tried running yarn test a to run all the tests. But once the tests have completed execution, I'm still getting the same prompt. I tried yarn test a q but that doesn't work. I also tried yarn test a --forceExit and yarn test a --bail but nothing happens, I still get the prompt. How can I run all my Jest tests without getting this prompt as there will be no interaction when running through Team City? Any help would be much appreciated.

@SeniorPomidor I tried "yarn test --ci" and "yarn test a --ci". But neither of them work :( — AnOldSoul, Jul 31 '18 at 09:56
Still no luck, getting the same prompt. Guess I'll have to add the ci true thing to my package json. Because that works. — AnOldSoul, Jul 31 '18 at 10:13
oh. glad to help you. as I said changing package.json is alternative solution — Senior Pomidor, Jul 31 '18 at 10:22

score 12 · Answer 1 · edited Feb 17 '21 at 07:17

12

--ci

When this option is provided, Jest will assume it is running in a CI environment. This changes the behavior when a new snapshot is encountered. Instead of the regular behavior of storing a new snapshot automatically, it will fail the test and require Jest to be run with --updateSnapshot. link

Also, you can change package.json to:

"test": "CI=true react-scripts test --env=jsdom",

which works great.

Your other option is to set CI in the command like any variable:

CI=true yarn test

edited Feb 17 '21 at 07:17

david.muffley

15
3

answered Jul 31 '18 at 08:53

Senior Pomidor

1,823
1
14
23

5

I tried "yarn test --ci" and "yarn test a --ci". But I'm still getting the same prompt. Is there another way that'd work without making any changes to the package json? – AnOldSoul Jul 31 '18 at 09:56

somoso · Accepted Answer · 2018-11-05T15:23:00.053

In TeamCity, edit the setting for your configuration, then select Parameters on the side.

Click Add a new Parameter, and in the dialog popup that appears, under Kind: select Environment variable (env.).

Set the name to env.CI and set the value to true. Click Save.

Next time you run your build, your build should auto-run the tests and move on.

For bonus points (and if you are the administrator) go to Administration then under Projects edit the <Root project>. Click Parameters on the side and set the env.CI parameter to true so you don't have to set this for future projects.

score 2 · Answer 3 · answered Jan 27 '19 at 12:55

2

yarn test --coverage

Will run only once (with coverage) and returns 0 on success and 1 on failure.

answered Jan 27 '19 at 12:55

Edan Chetrit

4,713
2
20
20

3

This will still cause the command to hang if no files have been changed since the last commit. The difference is that it will create a `coverage` folder under the project, and print some more information. – Michael Gates Jul 15 '19 at 21:15
this does not work for me! – Hafiz Temuri Feb 16 '22 at 00:42

score 2 · Answer 4 · edited Jan 07 '22 at 14:46

2

The following command worked for me.

CI=true yarn test

edited Jan 07 '22 at 14:46

ouflak

2,458
10
44
49

answered Jan 07 '22 at 12:28

Narendar Garvandula

21
1

Please provide an explanation. See [How to answer](https://stackoverflow.com/help/how-to-answer). – tomasantunes Jan 11 '22 at 09:30

How to run Jest tests with Yarn without any prompts?

4 Answers4