I’m writing a suite of tests for an sms application.
Because I want to properly test the functionality, it does try to send
real messages, but with a dummy flag attached.
This is fine, except the dummy flag is kept in the database,
(so it isn’t loaded until the fixtures load)
(otherwise I’d do a raise in my test_helper definition.)
I’ve defined an assertion called assert_not_live!,
which is fine,
it stops the TestCase that happens to be running,
but really if such a catastrophic failure occurs,
I want to stop the whole suite…
is there an exception I can raise which deliberately breaks the test
runner or perhaps rake container?
On Mon, 16 Jul 2007 09:04:30 +0900, Matthew R. wrote:
which is fine,
it stops the TestCase that happens to be running,
but really if such a catastrophic failure occurs,
I want to stop the whole suite…
I was looking for the same thing the other day, I think it would be nice
to have… I think there could be some way by sending the FINISHED
signal to the testrunner but I’m not sure. Just re-raising your request
BTW, what did you do to stop the testcase?
gabriele renzi wrote:
On Mon, 16 Jul 2007 09:04:30 +0900, Matthew R. wrote:
BTW, what did you do to stop the testcase?
I think I mis-stated that.
I think of each test as a “test case”.
Which it is.
On Tue, 17 Jul 2007 01:40:25 +0900, Matthew R. wrote:
gabriele renzi wrote:
On Mon, 16 Jul 2007 09:04:30 +0900, Matthew R. wrote:
BTW, what did you do to stop the testcase?
I think I mis-stated that.
I think of each test as a “test case”.
Which it is.
Ah, I see, and yes, I do agree with you, too bad TestCase is not named
something else 