rickhanlonii / jest-silent-reporter Goto Github PK

If you look at the readme at https://github.com/rickhanlonii/jest-silent-reporter, none of the images load.

As part of cleaning out "cruft" in our tests, and sometimes problems in our production code, I want to NOT see:

1. Progress messages -- ✔

And want to DO see:

2. Test failures -- ✔
3. Warnings (from node or react, etc.) -- ✘

This reporter is exactly what I need for (1) and (2), however, also suppresses warning for (3).

Feature request for an option not to suppress warning messages as tests run, to only suppress the progress-style messages.

😅

newman: could not find "jest-silent-reporter" reporter
ensure that the reporter is installed in the same directory as newman
please install reporter using npm

  "devDependencies": {
    "async": "3.2.0",
    "newman": "5.2.2",
    "path": "0.12.7",
    "newman-reporter-allure": "1.0.7",
    "jest-silent-reporter": "0.4.0"
  }

command: npm install

newman command:

newman run collection.json -e env.json jest --reporters=jest-silent-reporter

Any idea?

Hey Great Repo,!!

I am trying to use CLI to set up the jest-silent-reporter, but the configuration options are not getting set.

If I try it this way
jest --config jest.config.js --reporters=jest-silent-reporter JEST_SILENT_REPORTER_SHOW_WARNINGS=true
It fails with error

Error: Could not resolve a module for a custom reporter.
Module name: JEST_SILENT_REPORTER_SHOW_WARNINGS=true

if I try it this way
jest --config jest.config.js --reporters=jest-silent-reporter --JEST_SILENT_REPORTER_SHOW_WARNINGS=true

The command works, but no warnings are shown, same behavior I have noticed for JEST_SILENT_REPORTER_SHOW_DOTS

Can you please add some more examples to your read me for usages of the env variables?

I believe it would be useful to add more information to the README about what this package does, I found out about this package through this issue, if I came here directly from a search engine I wouldn't know what it does.

Thanks for the great work, by the way!

Made debugging jestjs/jest#8665 confusing as we only saw the exit status but no errors. Temporarily using the default reporter had this output:

See e.g. https://circleci.com/gh/facebook/jest/41094

Would be nice if it included what file that error was in

After upgrading Formik in a project that doesn't use this reporter I noticed that I was getting warnings that were using console.error instead of console.warn, and so weren't outputted when showWarnings is set to true.

console.error
      Warning: An update to Formik inside a test was not wrapped in act(...).

Would it be possible to add entry.type === 'error' to the console filtering check for warnings?

You can use our renovatebot to automate your dependency updates. I can help to setup good basic configuration.

I really believe in this reporter - while coding, a developer needs a piece of mind and not tons of log entries.

Is there a way to take it a step further - avoid the terminal flashing/refreshing anytime the tests run? whenever the tests run, the terminal always updates itself with some default watcher message, can this be eliminated to make it even more quiet?

Hey there,

thanks heaps for creating this plugin, from the bottom of my heart and my eyes (crying over scrolling jest' default output).

Sadly it doesn't work for me. All I see is my regular jest output. I am on windows 10, my app uses:
"jest": "^29.7.0",
"jest-silent-reporter": "^0.5.0",

All I get is this:

❯ npx jest --reporters=jest-silent-reporter src
Error: Could not resolve a module for a custom reporter.
Module name: src

I tried to put src at the front which doesn't even mention the "could not resolve".

In both cases I get my regular jest output.

Any tips on how to fix this? Cheers

Hey all, I see that master is not a main branch here, so latest changes are not shown on the commit history.

GitHub releases are also not created for v0.3

What I suggest is to

• change default branch back to master
• cherry pick commit from master to current default branch
• setup automatic GitHub releases
• add changelog
• setup semantic releases + conventional commits

What's your thoughts on it, can contributors help with it, would maintainers help/support such initiative?

Hey, great package. Can you add an option to keep the final report (see image below)?
It will be hard to keep track of the amount of many failures and it's not that verbose.

At the moment this runner swallows all jest output.
When run with --randomize and (with or without --showSeed) the seed is not visible.
This makes it hard/impossible to rerun the test with the same seed because it is not visible.

With the default jest reporter, we can search (Cmd + F) for the failed tests through the logs by searching for "FAIL <base directory>".

This helps us instantly get an overview of how many tests have failed and is specially useful when checking test results in GitHub Actions logs.

It'd be great if this reporter printed failed file paths in a similar format.

Current behavior

File paths for failed tests are printed like this in GitHub Actions logs:

/runner/_work/project/root/src/example/__tests__/Example.test.tsx
... followed by stack trace

Expected behavior

Failed file paths printed in this format:

FAIL src/example/__tests__/Example.test.tsx
... followed by stack trace

Hey,

using JEST_SILENT_REPORTER_DOTS=true is causing something like:

......................foo@bar:~/WebstormProjects/jest$

instead of:

......................

foo@bar:~/WebstormProjects/jest$

This package is really great.

In my machine the dots are white over the black background of my terminal, is there a way to make the dots green for a passing test and red for a failing test?

Thanks