I see... Thanks. 2012/10/2 Cristiano Gavião <cvgav...@gmail.com>
> Btw, You can use any other asserting library, as the one provided by the > Hamcrest project. > > Every time an assert fails, jbehave will catch and properly report it... > > regards, > > Cristiano > > > On 02/10/12 07:51, Julien Martin wrote: > > Thank you Louis, :-) > I rather meant is there a jbehave-specific way to throwing the error? > For instance if I have an assertEqual(expected, actual) that evaluates to > false what is meant by Mauro's statement in his prior email? > Regards, > Julien. > > 2012/10/2 louis gueye <louis.gu...@gmail.com> > >> Hi Julien, >> >> It means an instance of java.lang.Throwable which is the top ancestor of >> all error notification mechanism (Error, Exception). >> >> -- >> Cordialement/Regards, >> >> Louis GUEYE >> linkedin <http://fr.linkedin.com/in/louisgueye> | >> blog<http://deepintojee.wordpress.com/> >> | twitter <http://twitter.com/#%21/lgueye> >> >> >> >> 2012/10/2 Julien Martin <bal...@gmail.com> >> >>> Mauro, >>> What do you mean by "a Throwable instance is thrown"? Can you please >>> give me a short example? >>> Regards, >>> J. >>> >>> >>> 2012/10/2 Mauro Talevi <mauro.tal...@aquilonia.org> >>> >>>> Any assertion mechanism is allowed. What matters is that in case of >>>> failures a Throwable instance is thrown. >>>> >>>> >>>> On 02/10/2012 09:21, Julien Martin wrote: >>>> >>>>> Hello, >>>>> I would like to know whether it is correct from a BDD point of view to >>>>> use JUnit's assertXX methods in my steps or selenium pages (mine is a >>>>> webapp). >>>>> Regards, >>>>> Julien. >>>>> >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe from this list, please visit: >>>> >>>> http://xircles.codehaus.org/manage_email >>>> >>>> >>>> >>> >> >> > >
