Re: Access to Surefire test output
On 2010-09-14, sebb wrote: > However, the Gump mails don't seem to give access to this information, > unless one adds a suitable tag to the descriptor. > This is very tedious to have to do for every test. This is the same as having to add elements, isn't it? > Indeed, perhaps there should be easy read access to all of the Gump > output directories? That way we'd be publishing/distributing everything under a project's root - including stuff we may not be allowed to distribute. Stefan - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Access to Surefire test output
If a Surefire test fails, it's usually necessary to be able to read the file(s) in the surefire-reports directory to resolve the problem. However, the Gump mails don't seem to give access to this information, unless one adds a suitable tag to the descriptor. This is very tedious to have to do for every test. Is there a better way to get access to the surefire output? Indeed, perhaps there should be easy read access to all of the Gump output directories? Could that be done via suitable config of the HTTP server? - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org