Attempting to call report() from setupSpec() yields:
java.lang.NullPointerException: Cannot get property 'methodName' on null
As to the use-case: I think reports are a very powerful feature. Indeed,
the manual states that the reporting mechanism "*can be used to snapshot
the state of the browser at any point in time.*" I have specs that interact
with the browser in setupSpec(), and reporting over those interactions is
as-valuable in my view as reporting done in the actual features.
Example of interactions that I am inclined to push-into setupSpec when
doing blaxbox testing is recreating any entities that are required by the
spec, but are not directly part of the FUT. If setupSpec doesn't work
correctly, it can fail the test, so reporting on setupSpec can be very
On Wednesday, March 7, 2018 at 7:03:06 AM UTC+11, Marcin Erdmann wrote:
> Hi Samuel,
> Can you please elaborate on why you believe it's not supported in
> setupSpec/cleanupSpec? Also, can you explain why you have a requirement for
> On Sun, Feb 18, 2018 at 11:05 PM, Samuel Rossinovic <samuel.r...@gmail.com
>> Seems that calling GebReportingSpec.report() from the specification
>> setup/teardown methods is unsupported ATM. Was wondering if there are any
>> plans for supporting it?
>> You received this message because you are subscribed to the Google Groups
>> "Geb User Mailing List" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> To post to this group, send email to geb-...@googlegroups.com
>> To view this discussion on the web visit
>> For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups "Geb
User Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email
To post to this group, send email to email@example.com.
To view this discussion on the web visit
For more options, visit https://groups.google.com/d/optout.