Re: [rest-assured] Multiple assertions' violations report

[Johan Haleby]

Use the latest version :)

/Johan

On Thu, Mar 7, 2013 at 4:07 PM, Ariel Kogan <arik...@gmail.com> wrote:

Hello,

When my ResponseSpecification doesn't match the actual received response, I get on the log something that looks like:

java.lang.AssertionError: JSON path data.firstname doesn't match.

Expected: Ariel

  Actual: Colin

Is there a way I can configure REST assured to not stop on the first field but evaluate all of them and then fail? I would like to see in my log something like to following:

JSON path data.firstname doesn't match.

Expected: Ariel

  Actual: Colin

JSON path data.city doesn't match.

Expected: London

  Actual: Manchester

Thank you,

Ariel

--
You received this message because you are subscribed to the Google Groups "REST assured" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rest-assured...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Ariel Kogan]

Thanks very much Johan. I'm a happy man. That's great functionality.

Cheers,

Ariel

[Johan Haleby]

Glad to hear it!

Ariel

--