failed assert_raises appear to continue execution; failing a test multiple times

[pushcx]

I just got a very odd failure that feels similar to #62 but I'm pretty sure is a different issue because it happens every run. Screenshot for line numbers:

Here's the surprising quickdraw output. The first test that errors is unrelated but I included because otherwise it would also look like the wrong total bug.

This one test fails 4 times, once with each line number of an assert_raises. I expected the first one to stop the test.

test/task.test.rb:73
  Task[] turns a block into .action
    unexpected ArgumentError
      Task action must take one argument
        /home/pushcx/code/hotcake/lib/hotcake.rb:99:in 'Task.[]'

(test/task.test.rb)
  test/task.test.rb:82
    Task action must take one arg
      test/task.test.rb:84

expected block to raise ArgumentError but nothing was raised

(test/task.test.rb)
  test/task.test.rb:82
    Task action must take one arg
      test/task.test.rb:85

expected block to raise ArgumentError but nothing was raised

(test/task.test.rb)
  test/task.test.rb:82
    Task action must take one arg
      test/task.test.rb:86

expected block to raise ArgumentError but nothing was raised

(test/task.test.rb)
  test/task.test.rb:82
    Task action must take one arg
      test/task.test.rb:87

expected block to raise ArgumentError but nothing was raised

Passed: 21 | Failed: 4 | Errors: 1

[joeldrapper]

I believe this is intended behaviour. Quickdraw reports the number of assertions that passed, not the number of test blocks. The first assertion successfully records a failure and the test continues.