What steps will reproduce the problem?
1. Run ``mvn site'' with testability-explorer maven-testability-plugin 1.3.3
2. No explicit whiteList configuration
3.
What is the expected output? What do you see instead?
Static methods are called: Why is it bad?
I saw:
On line 391, static method String format(String, Object[]) is
called contributing 7% of total class cost
On line 143, static method String format(String, Object[]) is
called contributing 7% of total class cost
On line 422, static method String format(String, Object[]) is
called contributing 7% of total class cost
On line 355, static method String format(String, Object[]) is
called contributing 7% of total class cost
On line 291, static method String format(String, Object[]) is
called contributing 7% of total class cost
I expect that using this method (java.lang.String.format) will not contribute
to the testability cost.
What version of the product are you using? On what operating system?
I'm using the maven testability reporting plugin:
- testability-explorer maven-testability-plugin 1.3.3
- Running on ubuntu using mvn from the command-line.
Please provide any additional information below.
If this is expected, how can I whitelist this method?
I tried <configuration>
<whiteList>java.lang.String.format</whiteList>... to no avail
Thanks for your time and this is a great tool!
Original issue reported on code.google.com by timothy....@gmail.com on 7 Oct 2010 at 9:26
Original issue reported on code.google.com by
timothy....@gmail.com
on 7 Oct 2010 at 9:26