You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@roller.apache.org by Allen Gilliland <al...@sun.com> on 2006/11/15 21:09:11 UTC
test suites for unit tests
would anyone mind if I modify the business unit ant task to run a set of
the 4 junit test suites that I checked in a while ago instead of running
all of the test classes individually?
the main reasons to do this is so that we can control the order the
tests are run rather than having the junit ant task just run them
alphabetically. I have always found it really annoying that the
BookmarksTest runs first rather than having the tests setup so that each
successive test builds on the functionality of previous tests. It
obviously does no good to run the BookmarksTest when there is a problem
with creating weblogs :/
i would also prefer to set the tests to halt on error so that if a test
fails from an unexpected exception then it stops the testing. this way
it's obvious that the testing failed and you are most likely going to
have the cause of the problem near the end of the log file rather than
watching possibly dozens of tests continue to run and fail for no reason.
any objections?
-- Allen
Re: test suites for unit tests
Posted by Dave <sn...@gmail.com>.
No objection here. That all sounds very good.
- Dave
On 11/15/06, Allen Gilliland <al...@sun.com> wrote:
> would anyone mind if I modify the business unit ant task to run a set of
> the 4 junit test suites that I checked in a while ago instead of running
> all of the test classes individually?
>
> the main reasons to do this is so that we can control the order the
> tests are run rather than having the junit ant task just run them
> alphabetically. I have always found it really annoying that the
> BookmarksTest runs first rather than having the tests setup so that each
> successive test builds on the functionality of previous tests. It
> obviously does no good to run the BookmarksTest when there is a problem
> with creating weblogs :/
>
> i would also prefer to set the tests to halt on error so that if a test
> fails from an unexpected exception then it stops the testing. this way
> it's obvious that the testing failed and you are most likely going to
> have the cause of the problem near the end of the log file rather than
> watching possibly dozens of tests continue to run and fail for no reason.
>
> any objections?
>
> -- Allen
>