Well, none should ever fail (I mean when committing), so reporting one only just makes de clean-up process longer if you break something.

--
Salut,

Jordi.

En/na BAZLEY, Sebastian ha escrit:
Probably both ...

The test should be split into separate testxyz() methods if the assertions
are independent, otherwise only the first failure is detected. Easy enough
in this case, I think.

However, this is tricky to do with some of the GUI tests, as they create
lists of classes.
It would mean creating loads of independent tests, which is why I cheated
and added some code to report individual errors and only fail the test at
the end. Still needs a bit of work.

There is an add-on for JUnit which might be worth considering, if the
licence is OK.
It allows tests to continue if assertions fail; a single test can have
several failures.

S.
-----Original Message-----
From: Jordi Salvat i Alabart [mailto:[EMAIL PROTECTED]
Sent: 03 December 2003 13:30
To: JMeter Developers List
Subject: Re: Unit tests totally broken


[...] the test won't continue after that first failure.


Which is wrong: the test or the components?



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to