exactly
Tim Ellison wrote:
Mikhail Loenko wrote:
Hello
We have figured out that one of approcahes that was earlier dicussed and that
I originally opposed would work for us.
That is: get PerformanceTest class out of there and replace log() with calls
to java.util.logging.Logger.
Please let me know what you think.
What are you logging?
Nobody is going to search log files looking for success/failure messages.
If the test passes, then all is fine; if it does not pass then it should
inform the framework (i.e. a failing assertion or an explicit call to
fail()). At that point JUnit will give you a cause of failure, and if
that is not enough you debug it with a debugger not println's.
Regards,
Tim
