Currently, when running unit tests there are a large amount of errors/warnings that are spit out to the console. There are two problems with this. First is that the amount of "noise" these errors/warnings produce makes it hard to find real issues. In some cases, the output is so large that it isn't reported.

The second problem is that often, these errors/warnings indicate a real problem with the test and/or the application but do not fail the test. By cleaning these errors/warnings up, these problems will be addressed.

As a reference when the output of unit tests is saved to a file (using yarn test > testResults.txt) there are 87,089 lines of error/warning code.