[Pls send halp!] Cleaning up the test output
See original GitHub issue♻️ ♻️ ♻️ Please consider the environment before printing this Github issue. ♻️ ♻️ ♻️

Currently, the test output is very noisy – even for green builds. This makes it very difficult find any actual failures, especially on small screens and on phones.
Let’s try to clean it up!
Here are the useless output I have found based on this test run. Leave a comment about what you are looking into (🔒) so others won’t duplicate the effort.
A lot of these probably have the same root cause (for example, because of how the default Ember.onError
works) and probably require some refactoring in the test infrastructure.
- Build phase
-
'container' is imported by tmp/rollup-cache_path-I6PjJI6s.tmp/run_loop.js, but could not be resolved – treating it as an external dependency
-
'ember-debug' is imported by tmp/rollup-cache_path-l0Z4sygU.tmp/index.js, but could not be resolved – treating it as an external dependency
-
'assert' is imported from external module '@glimmer/util' but never used
-
'assert' and 'SERIALIZATION_FIRST_NODE_STRING' are imported from external module '@glimmer/util' but never used
(🔒 @James-Byrne)
-
- Test phase
-
WARNING: Library "magic" is already registered with Ember.
-
console.trace
-
DEPRECATION: Should not throw [deprecation id: test]
(🔒 @Draggha ) -
(node:6689) Warning: Possible EventEmitter memory leak detected. * listeners added. Use emitter.setMaxListeners() to increase limit
(🔒 @lukecoy ) -
(node:6689) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: *): Error: Navigation Timeout Exceeded: 900ms exceeded
-
Error: Element .does-not-exist not found.
(🔒 @KamiKillertO ) -
Error: Catch me
(🔒 @KamiKillertO ) -
Error: the error
(🔒 @KamiKillertO ) -
Testing paused. Use
resumeTest()to continue.
- The library version banner on app boot (🔒 @Draggha )
DEBUG: ------------------------------- DEBUG: Ember : * DEBUG: jQuery : * DEBUG: -------------------------------
-
Error while processing route: *
(🔒 @allthesignals ) -
More context objects were passed than there are dynamic segments for the route: stink-bomb
` -
WARNING: Binding style attributes may introduce cross-site scripting vulnerabilities; please ensure that values being bound are properly escaped. For more information, including how to disable this warning, see https://emberjs.com/deprecations/v1.x/#toc_binding-style-attributes. Style affected: *
(🔒 @KamiKillertO )
-
Issue Analytics
- State:
- Created 5 years ago
- Comments:24 (23 by maintainers)
Top Results From Across the Web
Cleanup after all junit tests - java - Stack Overflow
I'm using JUnit 4.9. Will this help?: import junit.framework.TestCase; import org.junit.AfterClass; import org.junit.BeforeClass; import org.junit.runner.
Read more >afterEach(cleanup); isn't cleaning up after each test · Issue #368
The only logical conclusion to come from this, plus my original post, is that afterEach(cleanup) isn't cleaning up the DOM between tests as...
Read more >JUnit Test Cases @Before @BeforeClass Annotation - Guru99
In this tutorial we will learn, how write junit test cases, we are using annotation ... Example: to clean up once test execution...
Read more >Clean Unit Tests with Mockito - Reflectoring
In this article we will learn how to mock objects with Mockito. We'll first talk about what test doubles are and then how...
Read more >Unit Testing with JUnit 4 - Tutorial - Vogella.com
It is used to cleanup the test environment (e.g., delete temporary data, restore defaults). It can also save memory by cleaning up expensive ......
Read more >
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thanks folks, I’ve updated the issue accordingly
Looks like a lot of these are addressed, I am okay closing the tracking issue and filing new ones as needed. I opened #17016 and #17017. Looks like a few of these still have outstanding PRs waiting for reviews also.