Hi.
while you are on this, I’d also like to have fueled-out errors (this implies storing the errors in the report objects).
Also there are two unresolved issues with worker:
Maybe you will be able to uncover what is the problem while improving the worker.
Cheers.
Uko
Hi to all,
I have tried to fix the CI process to show the failures and errors in the tests in a more descriptive way, not only showing the failed test case, but also the error and the stack trace of it.
After checking the problem, I have seen that the failures (and also errors) are not registered with the Error that has produce the failure.
Of course, then I remembered that is why the TestRunner reruns the tests to allow the debugging of the error.
What do you think of adding the produced exception to the TestResult?
Do you think it can have any other consequences? If it has, what if only adding to the CI process?
Or perhaps storing a reduced version of the error (perhaps a String representation, or something a lighter than the Error)
Thanks for all.
--
Locked
