Re: [PATCH] Test::Unit shows result even if interrupted

Hi,

In <[e-mail]>
  "Re: [PATCH] Test::Unit shows result even if interrupted" on Wed, 30 Jan 2008 00:18:06 +0900,
  Phlip <[e-mail]> wrote:

> > How do you do your writing code and running test cycle?
> 
> Though I incredibly agree with the subject line (the complete test batches for 
> mature projects can be long!), I'm wondering if someone should be using 'rake 
> test:recent', autotest, or the equivalent to only run the most recently changed 
> tests. The Test Driven Development cycle completely breaks down if the One Test 
> Button takes so long to run that you hesitate to hit it!

In my approach, each test has its priority.
  http://www.cozmixng.org/repos/rwiki/trunk/test/test-unit-ext/priority.rb

class MyTest < Test::Unit::TestCase
  priority :must
  def test_xxx
    ... # is always ran
  end

  priority :normal
  def test_yyy
    ... # is ran if the previous test isn't passed
        # is ran at the probability of 50% even if the previous test is passed
  end

  def test_zzz
    ... # has normal priority
  end

  ...
end

And then, I'll add new test at the top and 'must' priority
test goes down to 'normal priority':

class MyTest < Test::Unit::TestCase
  priority :must
  def test_aaa
    ... # hot test is always ran
  end

  priority :normal
  def test_xxx
    ... # not hot test may be ran
  end

  def test_yyy
    ... # is ran if the previous test isn't passed
        # is ran at the probability of 50% even if the previous test is passed
  end

  def test_zzz
    ... # has normal priority
  end

  ...
end

In this approach, there are two points:

  * Hot tests will be in the top of source code.
    The top of source code is highly visible. It means that
    source code says which test is important.

  * Not hot tests may not be always ran but it doesn't mean
    that they NEVER run. rake test:recent and autotest will
    not run tests that aren't related with effected
    files. But some tests may effect unexpected places.

    This is not intelligence rather than them but it works
    well for me. Test time becomes shorter, important tests
    are always ran and all tests are randomly ran.


Thanks,
--
kou