Update README.md

updated Junit to lowercase junit.
If the reporter is used as "jest-Junit" in a linux build agent, the test runner throws a `module not found` error related to Junit.
Setting `--reporters=jest-junit` solves the problem.
This commit is contained in:
Ian Moroney 2022-02-14 15:07:15 +00:00 committed by GitHub
parent 0d00bb14cb
commit d553414051
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -256,14 +256,14 @@ Some heuristic was necessary to figure out the mapping between the line in the s
</details> </details>
<details> <details>
<summary>jest-Junit</summary> <summary>jest-junit</summary>
[JEST](https://jestjs.io/) testing framework support requires the usage of [jest-Junit](https://github.com/jest-community/jest-Junit) reporter. [JEST](https://jestjs.io/) testing framework support requires the usage of [jest-junit](https://github.com/jest-community/jest-junit) reporter.
It will create test results in Junit XML format which can be then processed by this action. It will create test results in Junit XML format which can be then processed by this action.
You can use the following example configuration in `package.json`: You can use the following example configuration in `package.json`:
```json ```json
"scripts": { "scripts": {
"test": "jest --ci --reporters=default --reporters=jest-Junit" "test": "jest --ci --reporters=default --reporters=jest-junit"
}, },
"devDependencies": { "devDependencies": {
"jest": "^26.5.3", "jest": "^26.5.3",