Servirtium lib: mechanism to get last error from Servirtium side

[paul-hammant]

If I have a suite that ordinarily passes, but change something in the prior recording to cause a failure:

The build fails as expected, but the root cause is obscured as the servirtium side isn't handing root cause back to the test runner side. (It cannot/should't over the socket response)

Something near to stop() time would be great:

[paul-hammant]

Project I'm playing with is https://github.com/jbehave/jbehave-servirtium-climate-tck-demo. That needs JDK11 I think (~/.mavenrc)

[paul-hammant]

Cos I might be about to pair program this with a pal - paul-hammant/servirtium-demo-kotlin-climate-tck@bb74773

Also how do you get test-failed true/false and exception in @AfterEach without boilerplate. I sure hope JUnit5 gets such additions. There's a TestInfo class that can be injected optionally into @AfterEach but it is anemic.

[daviddenton]

I try not to play with JUnit stuff beyond the absolute necessary! Good luck… :)

…

On 21 Feb 2021, 22:34 +0000, Paul Hammant ***@***.***>, wrote: Cos I might be about to pair program this with a pal - ***@***.*** Also how do you get test-failed true/false and exception in @AfterEach without boilerplate. I sure hope JUnit5 gets such additions. There's a TestInfo class that can be injected optionally into @AfterEach but it is anemic. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.