tt> is called contributing 99% of total class cost

Since these static methods are complex, we want to mock them out in the unit test. If they are declared in your code, refactor the methods to be non-static, and inject an instance of the class. Otherwise, you can create a wrapper object.

Cost: 573

Class org.w3._2001.xmlschema.Adapter1 is hard to test because:

These collaborators cannot be mocked, so it is impossible to unit test this class in isolation.

Static methods are called: Why is it bad?

On line 17, static method String printDateTime(Date) is called contributing 99% of total class cost

Since these static methods are complex, we want to mock them out in the unit test. If they are declared in your code, refactor the methods to be non-static, and inject an instance of the class. Otherwise, you can create a wrapper object.

http://testabilityexplorer.org