[HEADS UP] - Mock endpoints now fail fast

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

[HEADS UP] - Mock endpoints now fail fast

Claus Ibsen-2
Hi

https://issues.apache.org/jira/browse/CAMEL-12003

When you use assertIsSatisifed with mock endpoints during testing then
they will now fail fast if a message arrived that would cause an
expectation to fail, and there are still more messages expected.

Before the mock endpoint would only validate expectations when the
number of expected message had arrived.

This is default enabled and you can turn it off by setting
failFast=false on the mock endpoint in your routes - to use 2.x
behaviour. But I dont expect people to want to use this (but just in
case).


--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Reply | Threaded
Open this post in threaded view
|

Re: [HEADS UP] - Mock endpoints now fail fast

Pascal Schumacher
+1

Am 02.08.2019 um 17:01 schrieb Claus Ibsen:

> Hi
>
> https://issues.apache.org/jira/browse/CAMEL-12003
>
> When you use assertIsSatisifed with mock endpoints during testing then
> they will now fail fast if a message arrived that would cause an
> expectation to fail, and there are still more messages expected.
>
> Before the mock endpoint would only validate expectations when the
> number of expected message had arrived.
>
> This is default enabled and you can turn it off by setting
> failFast=false on the mock endpoint in your routes - to use 2.x
> behaviour. But I dont expect people to want to use this (but just in
> case).
>
>

Reply | Threaded
Open this post in threaded view
|

Re: [HEADS UP] - Mock endpoints now fail fast

Andrea Cosentino-3
+1

Il ven 2 ago 2019, 17:11 Pascal Schumacher <[hidden email]> ha
scritto:

> +1
>
> Am 02.08.2019 um 17:01 schrieb Claus Ibsen:
> > Hi
> >
> > https://issues.apache.org/jira/browse/CAMEL-12003
> >
> > When you use assertIsSatisifed with mock endpoints during testing then
> > they will now fail fast if a message arrived that would cause an
> > expectation to fail, and there are still more messages expected.
> >
> > Before the mock endpoint would only validate expectations when the
> > number of expected message had arrived.
> >
> > This is default enabled and you can turn it off by setting
> > failFast=false on the mock endpoint in your routes - to use 2.x
> > behaviour. But I dont expect people to want to use this (but just in
> > case).
> >
> >
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [HEADS UP] - Mock endpoints now fail fast

Claus Ibsen-2
In reply to this post by Claus Ibsen-2
Hi

Okay so there are some unit test errors (approx 35) on CI after this
change. I will take a look over the weekend/monday.
I had a hunch that maybe something would be affected as the test
happens early now vs late.

On Fri, Aug 2, 2019 at 5:01 PM Claus Ibsen <[hidden email]> wrote:

>
> Hi
>
> https://issues.apache.org/jira/browse/CAMEL-12003
>
> When you use assertIsSatisifed with mock endpoints during testing then
> they will now fail fast if a message arrived that would cause an
> expectation to fail, and there are still more messages expected.
>
> Before the mock endpoint would only validate expectations when the
> number of expected message had arrived.
>
> This is default enabled and you can turn it off by setting
> failFast=false on the mock endpoint in your routes - to use 2.x
> behaviour. But I dont expect people to want to use this (but just in
> case).
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2



--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Reply | Threaded
Open this post in threaded view
|

Re: [HEADS UP] - Mock endpoints now fail fast

Claus Ibsen-2
Hi

Okay I think I have it fixed. So lets see next CI build

On Sat, Aug 3, 2019 at 10:00 AM Claus Ibsen <[hidden email]> wrote:

>
> Hi
>
> Okay so there are some unit test errors (approx 35) on CI after this
> change. I will take a look over the weekend/monday.
> I had a hunch that maybe something would be affected as the test
> happens early now vs late.
>
> On Fri, Aug 2, 2019 at 5:01 PM Claus Ibsen <[hidden email]> wrote:
> >
> > Hi
> >
> > https://issues.apache.org/jira/browse/CAMEL-12003
> >
> > When you use assertIsSatisifed with mock endpoints during testing then
> > they will now fail fast if a message arrived that would cause an
> > expectation to fail, and there are still more messages expected.
> >
> > Before the mock endpoint would only validate expectations when the
> > number of expected message had arrived.
> >
> > This is default enabled and you can turn it off by setting
> > failFast=false on the mock endpoint in your routes - to use 2.x
> > behaviour. But I dont expect people to want to use this (but just in
> > case).
> >
> >
> > --
> > Claus Ibsen
> > -----------------
> > http://davsclaus.com @davsclaus
> > Camel in Action 2: https://www.manning.com/ibsen2
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2



--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2