### A very biased list of tests that could enjoy some non-trivial refactoring 1. Make test compliant with [the test writing guide](https://github.com/nodejs/node/blob/master/doc/guides/writing-tests.md) 2. Make sure the test has a general description (PR or issue references most welcome) 3. Make sure test cases are well separated (IIFE, functions, or just scopes) and documented 4. Refactor away non-trivial micro-test-harnesses — example [sequential/test-debugger-debug-brk.js](https://github.com/nodejs/node/blob/c24a73d23c098e5cde7e55ce0c97f6daa11facc9/test/sequential/test-debugger-debug-brk.js) 5. Proper use of [`test/common`](https://github.com/nodejs/node/tree/master/test/common) utilities - [ ] [parallel/test-domain-abort-on-uncaught.js](https://github.com/nodejs/node/blob/master/test/parallel/test-domain-abort-on-uncaught.js) - [ ] [sequential/test-debugger-debug-brk.js](https://github.com/nodejs/node/blob/c24a73d23c098e5cde7e55ce0c97f6daa11facc9/test/sequential/test-debugger-debug-brk.js) ### new entries - [ ] [parallel/test-console.js](https://github.com/nodejs/node/blob/bb294059040def8e8c0b1719cc17f6537ab5cb39/test/parallel/test-console.js) - after https://github.com/nodejs/node/pull/14643 lands this test should assert the expected outputs. Currently it only checks that values are written to `stdout` and don't throw.
A very biased list of tests that could enjoy some non-trivial refactoring
test/commonutilitiesnew entries
stdoutand don't throw.