-
Notifications
You must be signed in to change notification settings - Fork 156
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
Lots of warnings & errors when running unit tests #6337
Comments
@individual-it could your team take a look in the upcoming weeks? |
I added to the Test Automation Backlog project. We will put it in a test automation sprint. |
Related to this: #6130 (error messages like that should never be part of the html). |
I'd like to raise the prio on this. It's becoming quite hard meanwhile to identify actual test failures vs "noise" when running unit tests locally and having something failing. Would be good to get ahead of this again. |
added it to the current sprint and assigned myselg, could be as simple as adding |
While adding the |
Agree ^ - fix/refactor anything that is actually "dodgy" |
So I misunderstood what the task is about What I could not solve so far:
any ideas on those issues? |
some tests are completely kaput e.g.
if I run it locally with node 16 the test fails, with node 14 it spits out the error but marks the test as passed |
after #6415 those tests should not pass anymore |
wow 😍 |
reopening because seeing this in nightly builds:
|
Thanks for taking care! Closing now, since I merged your two PRs. |
reopening because seeing this in nightly builds:
|
reopening again, because log output came back, mostly share jail |
Expected behaviour
(Successful) Unit test runs provide minimal output to console
Actual behaviour
(Successful) Unit test runs spam the console with warnings & errors
Hints
Especially the tests in
packages/web-app-files/tests/unit/views/
seem to be offendersThe text was updated successfully, but these errors were encountered: