From noreply at rubyforge.org  Mon Feb  1 13:10:01 2010
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Mon,  1 Feb 2010 13:10:01 -0500 (EST)
Subject: [test-unit-tracker] [ test-unit-Support Requests-27763 ] Can
	Test::Unit process all assertions even if some of them fail?
Message-ID: <20100201181001.94BDE158806A@rubyforge.org>

Support Requests item #27763, was opened at 2010-02-01 18:10
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21857&aid=27763&group_id=5650

Category: None
Group: None
Status: Open
Priority: 3
Submitted By: David MARCHALAND (marchaland)
Assigned to: Nobody (None)
Summary: Can Test::Unit process all assertions even if some of them fail?

Initial Comment:
Hi,

In my non-regression, I do multiple independant assertions in a test. For instance, I write:
def test_1
  # Do some stuff
  assert_equal(...) # Assertion 1
  assert_equal(...) # Assertion 2
end

Assertion 1 is not linked to assertion 2. If assertion 1 fails, assertion 2 is not executed. Hence, my non-regression is not complete.

Question : is there a way to force the execution of all assertions defined in a test even if some fail?

BR,
David

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21857&aid=27763&group_id=5650

From noreply at rubyforge.org  Mon Feb  1 13:16:09 2010
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Mon,  1 Feb 2010 13:16:09 -0500 (EST)
Subject: [test-unit-tracker] [ test-unit-Bugs-27764 ] test_order defined for
	one testcase but executed for all
Message-ID: <20100201181609.BD68A158806A@rubyforge.org>

Bugs item #27764, was opened at 2010-02-01 18:16
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21856&aid=27764&group_id=5650

Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: David MARCHALAND (marchaland)
Assigned to: Nobody (None)
Summary: test_order defined for one testcase but executed for all

Initial Comment:
Hi,

I defined 2 testcases named TC1 and TC2 in a testsuite (TC1 is executed before TC2). I want to keep default test order for TC2 but I specify a random test order for TC1 by defining TC1.test_order = :random. What I observe is that TC2 is also randomized. Is it normal?

BR,
David

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21856&aid=27764&group_id=5650

From noreply at rubyforge.org  Fri Feb  5 23:51:21 2010
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri,  5 Feb 2010 23:51:21 -0500 (EST)
Subject: [test-unit-tracker] [ test-unit-Bugs-27790 ] Omissions counted as
	failures
Message-ID: <20100206045121.830BB18582E1@rubyforge.org>

Bugs item #27790, was opened at 2010-02-05 21:51
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21856&aid=27790&group_id=5650

Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Daniel Berger (djberg96)
Assigned to: Nobody (None)
Summary: Omissions counted as failures

Initial Comment:
Hi,

test-unit 2.0.6

I noticed that in the final tally test-unit is counting omissions as failures:

16 tests, 22 assertions, 0 failures, 0 errors, 0 pendings, 9 omissions, 0 notifications
43.75% passed # => EH?

I would argue anything that isn't a failure or an error is a "pass".

Regards,

Dan

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21856&aid=27790&group_id=5650

From noreply at rubyforge.org  Sat Feb  6 05:19:48 2010
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sat,  6 Feb 2010 05:19:48 -0500 (EST)
Subject: [test-unit-tracker] [ test-unit-Bugs-27790 ] Omissions counted as
	failures
Message-ID: <20100206101948.850C318582DD@rubyforge.org>

Bugs item #27790, was opened at 2010-02-06 04:51
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21856&aid=27790&group_id=5650

Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Daniel Berger (djberg96)
Assigned to: Nobody (None)
Summary: Omissions counted as failures

Initial Comment:
Hi,

test-unit 2.0.6

I noticed that in the final tally test-unit is counting omissions as failures:

16 tests, 22 assertions, 0 failures, 0 errors, 0 pendings, 9 omissions, 0 notifications
43.75% passed # => EH?

I would argue anything that isn't a failure or an error is a "pass".

Regards,

Dan

----------------------------------------------------------------------

Comment By: David MARCHALAND (marchaland)
Date: 2010-02-06 10:19

Message:
Hi Dan,

Based on my usage of test-unit, I would not consider an omission as a "pass". For instance, if you define a testcase with all tests omitted, you will have 100% passed while you test nothing...

Why not having two metrics, one with omission counted as failure and a second one counted as pass. This can be an option to testrunner.
What's the behavior with pending and notification?

Regards,
David

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21856&aid=27790&group_id=5650

From noreply at rubyforge.org  Sat Feb  6 05:32:17 2010
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sat,  6 Feb 2010 05:32:17 -0500 (EST)
Subject: [test-unit-tracker] [ test-unit-Support Requests-27792 ]
	Test::Unit::Priority desactivation
Message-ID: <20100206103217.6136818582DC@rubyforge.org>

Support Requests item #27792, was opened at 2010-02-06 10:32
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21857&aid=27792&group_id=5650

Category: None
Group: None
Status: Open
Priority: 3
Submitted By: David MARCHALAND (marchaland)
Assigned to: Nobody (None)
Summary: Test::Unit::Priority desactivation

Initial Comment:
Hi,

I use test-unit in an embedded application and I don't support 'fileutils' and 'tmpdir' ruby libraries (I don't know why it fails...). I've seen that these two libraries are required in priority.rb file. If I don't use test-unit priority features, can I comment the following line "require 'test/unit/priority'" in testcase.rb file without affecting the overall test-unit behavior.

Thanks for your support!
David

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21857&aid=27792&group_id=5650

From noreply at rubyforge.org  Mon Feb 15 12:22:15 2010
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Mon, 15 Feb 2010 12:22:15 -0500 (EST)
Subject: [test-unit-tracker] [ test-unit-Feature Requests-27832 ] A way to
	timeout a test
Message-ID: <20100215172215.24EFE18582EE@rubyforge.org>

Feature Requests item #27832, was opened at 2010-02-15 10:22
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21859&aid=27832&group_id=5650

Category: None
Group: None
Status: Open
Priority: 3
Submitted By: Daniel Berger (djberg96)
Assigned to: Nobody (None)
Summary: A way to timeout a test

Initial Comment:
Hi,

A recent problem with a test suite made me think that there should be a way to timeout a test, and treat it as a failure if it times out.

Our problem was that the test itself was hanging indefinitely. This is not ideal behavior, and could cause problems with continuous integration software.

Personally, I would prefer that all tests be wrapped in timeout blocks, and be considered failures if they take more than, say, 20 seconds. Make this configurable. Something like:

timeout => 30
def test_something
...
end

What do you think?

Regards,

Dan

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21859&aid=27832&group_id=5650

From noreply at rubyforge.org  Mon Feb 15 12:41:42 2010
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Mon, 15 Feb 2010 12:41:42 -0500 (EST)
Subject: [test-unit-tracker] [ test-unit-Bugs-27833 ] Odd diff output with
	true & false
Message-ID: <20100215174142.2074E18582D6@rubyforge.org>

Bugs item #27833, was opened at 2010-02-15 10:41
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21856&aid=27833&group_id=5650

Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Daniel Berger (djberg96)
Assigned to: Nobody (None)
Summary: Odd diff output with true & false

Initial Comment:
I had an old test that looked like this:

assert_equal(true, @hash.method(:each_pair) == @hash.method(:each))

And it gave me this output:

 5) Failure:
test_each_pair_alias(Test_Hash_Each_InstanceMethod) [./test/core/Hash/instance/test_each.rb:35]:
<true> expected but was
<false>

diff:
? tru e
? fals

What's happening there?

Regards,

Dan

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21856&aid=27833&group_id=5650

From noreply at rubyforge.org  Mon Feb 15 12:47:46 2010
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Mon, 15 Feb 2010 12:47:46 -0500 (EST)
Subject: [test-unit-tracker] [ test-unit-Feature Requests-27832 ] A way to
	timeout a test
Message-ID: <20100215174746.264B318582D6@rubyforge.org>

Feature Requests item #27832, was opened at 2010-02-15 17:22
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21859&aid=27832&group_id=5650

Category: None
Group: None
Status: Open
Priority: 3
Submitted By: Daniel Berger (djberg96)
Assigned to: Nobody (None)
Summary: A way to timeout a test

Initial Comment:
Hi,

A recent problem with a test suite made me think that there should be a way to timeout a test, and treat it as a failure if it times out.

Our problem was that the test itself was hanging indefinitely. This is not ideal behavior, and could cause problems with continuous integration software.

Personally, I would prefer that all tests be wrapped in timeout blocks, and be considered failures if they take more than, say, 20 seconds. Make this configurable. Something like:

timeout => 30
def test_something
...
end

What do you think?

Regards,

Dan

----------------------------------------------------------------------

Comment By: James Tucker (raggi)
Date: 2010-02-15 17:47

Message:
It is not unusual in IO / complex scheduling environments to want to do this too, sometimes with a custom callback.

One example from eventmachine:

http://github.com/eventmachine/eventmachine/blob/3008ae6ea9e33abeb9c7628d9b8a72256f55e725/tests/test_basic.rb#L155-162

Timeouts are a bit of a problem in ruby as they can violate ensure, as well as have odd thread safety semantics.

SystemTimer is recommended if it's available, if not, this may be of use, although I have not tested it to any extreme yet.

class SoftTimeout
  class Error < Timeout::Error; end

  def self.timeout(t = 10)
    thread = Thread.current
    mutex = Mutex.new
    timeout = Thread.new do
      sleep t
      mutex.synchronize { thread.raise Error, "Timeout after #{t} seconds" }
    end
    v = nil
    begin
      v = yield
    ensure
      mutex.synchronize { timeout.kill }
    end
    v
  end
end

require "test/unit"

# require "soft_timeout"

class TestSoftTimeout < Test::Unit::TestCase
  def test_timeout
    start = Time.now.to_f
    assert_raise(SoftTimeout::Error) do
      SoftTimeout.timeout(0.02) do
        sleep
      end
    end
    finish = Time.now.to_f
    assert_in_delta(finish - start, 0.02, 0.005)
  end

  def test_completer
    a = false
    SoftTimeout.timeout do
      a = true
    end
    assert a
  end

  def test_threads_cleardown
    n = SoftTimeout.timeout { Thread.list.size }
    assert_equal 1, Thread.list.size
    assert_equal 2, n
  end

  def test_same_thread_running
    t = nil
    SoftTimeout.timeout {
      t = Thread.current
    }
    assert_equal Thread.current, t
  end

  def test_returns_value
    v = SoftTimeout.timeout { :value }
    assert_equal :value, v
  end

  def test_exception
    SoftTimeout.timeout do
      raise 'boom'
    end
  rescue RuntimeError
    assert_equal 'boom', $!.message
    assert_equal 1, Thread.list.size
  end

  def test_softimeout_error
    SoftTimeout.timeout(0) do
      sleep
    end
  rescue SoftTimeout::Error => e
    assert_equal "Timeout after 0 seconds", e.message
    assert_equal 1, Thread.list.size
  end
end

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21859&aid=27832&group_id=5650

From noreply at rubyforge.org  Mon Feb 15 12:58:00 2010
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Mon, 15 Feb 2010 12:58:00 -0500 (EST)
Subject: [test-unit-tracker] [ test-unit-Patches-27834 ] Add git to
	Test::Unit::Collector::Dir
Message-ID: <20100215175800.A325F18582D6@rubyforge.org>

Patches item #27834, was opened at 2010-02-15 10:58
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21858&aid=27834&group_id=5650

Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Daniel Berger (djberg96)
Assigned to: Nobody (None)
Summary: Add git to Test::Unit::Collector::Dir

Initial Comment:
Hi,

I saw this on line 63 of collector/dir.rb:

next if /\A(?:CVS|\.svn)\z/ =~ e

Let's add git to that list:

next if /\A(?:CVS|\.svn|\.git)\z/ =~ e

Look ok?

Regards,

Dan

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21858&aid=27834&group_id=5650

From noreply at rubyforge.org  Thu Feb 25 13:02:05 2010
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu, 25 Feb 2010 13:02:05 -0500 (EST)
Subject: [test-unit-tracker] [ test-unit-Bugs-27892 ] Test::Unit 2.x vs 1.x,
	remaining parameters are returned differently
Message-ID: <20100225180205.96D3D18582E9@rubyforge.org>

Bugs item #27892, was opened at 2010-02-25 13:02
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21856&aid=27892&group_id=5650

Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Bob Saveland (savelandr)
Assigned to: Nobody (None)
Summary: Test::Unit 2.x vs 1.x, remaining parameters are returned differently

Initial Comment:
With the standard Test::Unit in ruby 1.8.x, the "--" parameter delimiter is removed.  With Test::Unit 2.0.6 and ruby 1.9.1, the "--" parameter delimiter is still present when the test code starts to consume parameters.

Example:

class TCTest < Test::Unit::TestCase
  def setup
    puts "ARGV: #{ARGV}"
  end

  def test_test
  end
end


$ ruby1.8  tc_test.rb -- -whatever
Loaded suite tc_test
Started
ARGV: -whatever  <----------------------  No "--" is present
.
Finished in 0.000331 seconds.

1 tests, 0 assertions, 0 failures, 0 errors

$  ruby1.9.1 tc_test.rb -- -whatever
Loaded suite tc_test
Started
ARGV: ["--", "-whatever"]  <------------  "--" is present
.

Finished in 0.000754646 seconds.

1 tests, 0 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications
100% passed

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21856&aid=27892&group_id=5650

From noreply at rubyforge.org  Sun Feb 28 05:55:20 2010
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sun, 28 Feb 2010 05:55:20 -0500 (EST)
Subject: [test-unit-tracker] [ test-unit-Patches-27834 ] Add git to
	Test::Unit::Collector::Dir
Message-ID: <20100228105520.7917418582CE@rubyforge.org>

Patches item #27834, was opened at 2010-02-16 02:58
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21858&aid=27834&group_id=5650

Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Daniel Berger (djberg96)
Assigned to: Nobody (None)
Summary: Add git to Test::Unit::Collector::Dir

Initial Comment:
Hi,

I saw this on line 63 of collector/dir.rb:

next if /\A(?:CVS|\.svn)\z/ =~ e

Let's add git to that list:

next if /\A(?:CVS|\.svn|\.git)\z/ =~ e

Look ok?

Regards,

Dan

----------------------------------------------------------------------

>Comment By: Kouhei Sutou (kou)
Date: 2010-02-28 19:55

Message:
Thanks for your suggestion.
I've applied your suggestion in trunk.

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21858&aid=27834&group_id=5650

From noreply at rubyforge.org  Sun Feb 28 05:56:35 2010
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sun, 28 Feb 2010 05:56:35 -0500 (EST)
Subject: [test-unit-tracker] [ test-unit-Patches-27834 ] Add git to
	Test::Unit::Collector::Dir
Message-ID: <20100228105636.037BF18582CE@rubyforge.org>

Patches item #27834, was opened at 2010-02-16 02:58
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21858&aid=27834&group_id=5650

Category: None
Group: None
>Status: Closed
>Resolution: Accepted
Priority: 3
Submitted By: Daniel Berger (djberg96)
Assigned to: Nobody (None)
Summary: Add git to Test::Unit::Collector::Dir

Initial Comment:
Hi,

I saw this on line 63 of collector/dir.rb:

next if /\A(?:CVS|\.svn)\z/ =~ e

Let's add git to that list:

next if /\A(?:CVS|\.svn|\.git)\z/ =~ e

Look ok?

Regards,

Dan

----------------------------------------------------------------------

Comment By: Kouhei Sutou (kou)
Date: 2010-02-28 19:55

Message:
Thanks for your suggestion.
I've applied your suggestion in trunk.

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21858&aid=27834&group_id=5650

From noreply at rubyforge.org  Sun Feb 28 06:11:27 2010
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sun, 28 Feb 2010 06:11:27 -0500 (EST)
Subject: [test-unit-tracker] [ test-unit-Bugs-27764 ] test_order defined for
	one testcase but executed for all
Message-ID: <20100228111127.B51D418582C9@rubyforge.org>

Bugs item #27764, was opened at 2010-02-02 03:16
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21856&aid=27764&group_id=5650

Category: None
Group: None
>Status: Closed
>Resolution: Accepted
Priority: 3
Submitted By: David MARCHALAND (marchaland)
Assigned to: Nobody (None)
Summary: test_order defined for one testcase but executed for all

Initial Comment:
Hi,

I defined 2 testcases named TC1 and TC2 in a testsuite (TC1 is executed before TC2). I want to keep default test order for TC2 but I specify a random test order for TC1 by defining TC1.test_order = :random. What I observe is that TC2 is also randomized. Is it normal?

BR,
David

----------------------------------------------------------------------

>Comment By: Kouhei Sutou (kou)
Date: 2010-02-28 20:11

Message:
In trunk, test_order can be kept in each test case.
It will be a behavior what you expected.

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21856&aid=27764&group_id=5650

From noreply at rubyforge.org  Sun Feb 28 06:34:56 2010
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sun, 28 Feb 2010 06:34:56 -0500 (EST)
Subject: [test-unit-tracker] [ test-unit-Bugs-27790 ] Omissions counted as
	failures
Message-ID: <20100228113456.B57A618582D0@rubyforge.org>

Bugs item #27790, was opened at 2010-02-06 13:51
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21856&aid=27790&group_id=5650

Category: None
Group: None
>Status: Closed
>Resolution: Accepted
Priority: 3
Submitted By: Daniel Berger (djberg96)
Assigned to: Nobody (None)
Summary: Omissions counted as failures

Initial Comment:
Hi,

test-unit 2.0.6

I noticed that in the final tally test-unit is counting omissions as failures:

16 tests, 22 assertions, 0 failures, 0 errors, 0 pendings, 9 omissions, 0 notifications
43.75% passed # => EH?

I would argue anything that isn't a failure or an error is a "pass".

Regards,

Dan

----------------------------------------------------------------------

>Comment By: Kouhei Sutou (kou)
Date: 2010-02-28 20:34

Message:
Daniel and David, thanks for your comments.

Omitted tests are ignored from 'n% passed' report in trunk.

One of 'omit' use case is a platform depended test. e.g. a test that uses 'fork' never work on Windows. In the use case, we can ignore the test.


If the change isn't reasonable, more comments are welcome.

----------------------------------------------------------------------

Comment By: David MARCHALAND (marchaland)
Date: 2010-02-06 19:19

Message:
Hi Dan,

Based on my usage of test-unit, I would not consider an omission as a "pass". For instance, if you define a testcase with all tests omitted, you will have 100% passed while you test nothing...

Why not having two metrics, one with omission counted as failure and a second one counted as pass. This can be an option to testrunner.
What's the behavior with pending and notification?

Regards,
David

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21856&aid=27790&group_id=5650

From noreply at rubyforge.org  Sun Feb 28 06:37:34 2010
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sun, 28 Feb 2010 06:37:34 -0500 (EST)
Subject: [test-unit-tracker] [ test-unit-Bugs-27833 ] Odd diff output with
	true & false
Message-ID: <20100228113734.26F2918582CE@rubyforge.org>

Bugs item #27833, was opened at 2010-02-16 02:41
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21856&aid=27833&group_id=5650

Category: None
Group: None
>Status: Closed
>Resolution: Rejected
Priority: 3
Submitted By: Daniel Berger (djberg96)
Assigned to: Nobody (None)
Summary: Odd diff output with true & false

Initial Comment:
I had an old test that looked like this:

assert_equal(true, @hash.method(:each_pair) == @hash.method(:each))

And it gave me this output:

 5) Failure:
test_each_pair_alias(Test_Hash_Each_InstanceMethod) [./test/core/Hash/instance/test_each.rb:35]:
<true> expected but was
<false>

diff:
? tru e
? fals

What's happening there?

Regards,

Dan

----------------------------------------------------------------------

>Comment By: Kouhei Sutou (kou)
Date: 2010-02-28 20:37

Message:
Umm, please use assert_true or assert_false for the case.
They doesn't generate diff.

assert_equal generates diff from stringified expected value and actual value. So diff between 'true' and 'false' is outputted.

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21856&aid=27833&group_id=5650

From noreply at rubyforge.org  Sun Feb 28 06:42:49 2010
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sun, 28 Feb 2010 06:42:49 -0500 (EST)
Subject: [test-unit-tracker] [ test-unit-Bugs-27892 ] Test::Unit 2.x vs 1.x,
	remaining parameters are returned differently
Message-ID: <20100228114249.3401E18582D5@rubyforge.org>

Bugs item #27892, was opened at 2010-02-26 03:02
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21856&aid=27892&group_id=5650

Category: None
Group: None
>Status: Closed
>Resolution: Accepted
Priority: 3
Submitted By: Bob Saveland (savelandr)
Assigned to: Nobody (None)
Summary: Test::Unit 2.x vs 1.x, remaining parameters are returned differently

Initial Comment:
With the standard Test::Unit in ruby 1.8.x, the "--" parameter delimiter is removed.  With Test::Unit 2.0.6 and ruby 1.9.1, the "--" parameter delimiter is still present when the test code starts to consume parameters.

Example:

class TCTest < Test::Unit::TestCase
  def setup
    puts "ARGV: #{ARGV}"
  end

  def test_test
  end
end


$ ruby1.8  tc_test.rb -- -whatever
Loaded suite tc_test
Started
ARGV: -whatever  <----------------------  No "--" is present
.
Finished in 0.000331 seconds.

1 tests, 0 assertions, 0 failures, 0 errors

$  ruby1.9.1 tc_test.rb -- -whatever
Loaded suite tc_test
Started
ARGV: ["--", "-whatever"]  <------------  "--" is present
.

Finished in 0.000754646 seconds.

1 tests, 0 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications
100% passed

----------------------------------------------------------------------

>Comment By: Kouhei Sutou (kou)
Date: 2010-02-28 20:42

Message:
I've fixed it in trunk.


----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21856&aid=27892&group_id=5650

From noreply at rubyforge.org  Sun Feb 28 06:49:01 2010
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sun, 28 Feb 2010 06:49:01 -0500 (EST)
Subject: [test-unit-tracker] [ test-unit-Support Requests-27763 ] Can
	Test::Unit process all assertions even if some of them fail?
Message-ID: <20100228114901.B5B6618582D3@rubyforge.org>

Support Requests item #27763, was opened at 2010-02-02 03:10
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21857&aid=27763&group_id=5650

Category: None
Group: None
>Status: Closed
Priority: 3
Submitted By: David MARCHALAND (marchaland)
Assigned to: Nobody (None)
Summary: Can Test::Unit process all assertions even if some of them fail?

Initial Comment:
Hi,

In my non-regression, I do multiple independant assertions in a test. For instance, I write:
def test_1
  # Do some stuff
  assert_equal(...) # Assertion 1
  assert_equal(...) # Assertion 2
end

Assertion 1 is not linked to assertion 2. If assertion 1 fails, assertion 2 is not executed. Hence, my non-regression is not complete.

Question : is there a way to force the execution of all assertions defined in a test even if some fail?

BR,
David

----------------------------------------------------------------------

>Comment By: Kouhei Sutou (kou)
Date: 2010-02-28 20:49

Message:
It's a good way that an independant assertion (or assertions-set) in a test.
Please define two tests for "assertion 1" and "assertions 2".


----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21857&aid=27763&group_id=5650

From noreply at rubyforge.org  Sun Feb 28 06:52:42 2010
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sun, 28 Feb 2010 06:52:42 -0500 (EST)
Subject: [test-unit-tracker] [ test-unit-Support Requests-27792 ]
	Test::Unit::Priority desactivation
Message-ID: <20100228115243.1069918582D6@rubyforge.org>

Support Requests item #27792, was opened at 2010-02-06 19:32
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21857&aid=27792&group_id=5650

Category: None
Group: None
>Status: Closed
Priority: 3
Submitted By: David MARCHALAND (marchaland)
Assigned to: Nobody (None)
Summary: Test::Unit::Priority desactivation

Initial Comment:
Hi,

I use test-unit in an embedded application and I don't support 'fileutils' and 'tmpdir' ruby libraries (I don't know why it fails...). I've seen that these two libraries are required in priority.rb file. If I don't use test-unit priority features, can I comment the following line "require 'test/unit/priority'" in testcase.rb file without affecting the overall test-unit behavior.

Thanks for your support!
David

----------------------------------------------------------------------

>Comment By: Kouhei Sutou (kou)
Date: 2010-02-28 20:52

Message:
OK.
We delay to require 'fileutils' and 'tmpdir' until Test::Unit::Priority.enable.

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21857&aid=27792&group_id=5650