From noreply at rubyforge.org Thu Jan 7 14:40:55 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Thu, 7 Jan 2010 14:40:55 -0500 (EST) Subject: [test-unit-tracker] [ test-unit-Feature Requests-27582 ] Reference card Message-ID: <20100107194055.7720615B802F@rubyforge.org> Feature Requests item #27582, was opened at 2009-12-16 16:17 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=21859&aid=27582&group_id=5650 Category: None Group: None Status: Open Priority: 3 Submitted By: David MARCHALAND (marchaland) Assigned to: Nobody (None) Summary: Reference card Initial Comment: Hi, Can you provide a "Reference card" with next distribution that list all assertions with corresponding prototype as well as notification, omission & pending? I ask for that but not sure you have an easy way to generate such refcard based on your source code. Thanks, David PS: For when is plan next release? ---------------------------------------------------------------------- Comment By: Daniel Berger (djberg96) Date: 2010-01-07 12:40 Message: I'd like to see a release soon as well so I can start using the declarative test syntax. :) Regards, Dan ---------------------------------------------------------------------- Comment By: Kouhei Sutou (kou) Date: 2009-12-18 04:26 Message: What about this page? http://test-unit.rubyforge.org/test-unit/Test/Unit/Assertions.html If you send a "reference card" with RDoc format, we will include it in the next release! If you want to get a new release, I will release it. Are you in a hurry? ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=21859&aid=27582&group_id=5650 From noreply at rubyforge.org Thu Jan 7 14:43:34 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Thu, 7 Jan 2010 14:43:34 -0500 (EST) Subject: [test-unit-tracker] [ test-unit-Feature Requests-26032 ] Parallel option? Message-ID: <20100107194334.5639915B8035@rubyforge.org> Feature Requests item #26032, was opened at 2009-05-26 17:05 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=21859&aid=26032&group_id=5650 Category: None Group: None Status: Open Priority: 1 Submitted By: Daniel Berger (djberg96) Assigned to: Nobody (None) Summary: Parallel option? Initial Comment: Hi, I came across this project for rspec that allows you to run tests in parallel: http://github.com/grosser/parallel_specs/tree/master Could something similar be implemented for test-unit as a way of increasing test speed? Regards, Dan ---------------------------------------------------------------------- >Comment By: Daniel Berger (djberg96) Date: 2010-01-07 12:43 Message: Using pipes sounds like a reasonable idea. I'd love to see that implemented. I'm not sure how to implement it, though. A socket pair, perhaps? Gotta think about Windows, too. Regards, Dan ---------------------------------------------------------------------- Comment By: Kouhei Sutou (kou) Date: 2009-05-29 19:51 Message: test-unit provides priority mode. The mode reduces number of tests in a test. It increases test speed. To implement multi process test feature is not difficult but messy. I implemented it in Cutter, a unit testing framework for C. I think test output is very important to debug. If we just run multiple test-unit (rspec) processes in parallel, outputs of them are mixed. It causes NO debug friendly output. In Cutter, there are master process and child processes. Child processes send their results to master process via pipe. Test result is outputed by only master process. So outputs aren't mixed. If we add multi-process test running support, we will implement the same architecture of Cutter. If priority mode isn't satisfied you, we need to consider about it. Parallel mode is one of ideas. # Patch is welcome. :) ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=21859&aid=26032&group_id=5650 From noreply at rubyforge.org Sat Jan 9 06:13:46 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Sat, 9 Jan 2010 06:13:46 -0500 (EST) Subject: [test-unit-tracker] [ test-unit-Feature Requests-27582 ] Reference card Message-ID: <20100109111346.6B03915B802C@rubyforge.org> Feature Requests item #27582, was opened at 2009-12-17 08:17 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=21859&aid=27582&group_id=5650 Category: None Group: None >Status: Closed Priority: 3 Submitted By: David MARCHALAND (marchaland) Assigned to: Nobody (None) Summary: Reference card Initial Comment: Hi, Can you provide a "Reference card" with next distribution that list all assertions with corresponding prototype as well as notification, omission & pending? I ask for that but not sure you have an easy way to generate such refcard based on your source code. Thanks, David PS: For when is plan next release? ---------------------------------------------------------------------- >Comment By: Kouhei Sutou (kou) Date: 2010-01-09 20:13 Message: I've released 2.0.6. ---------------------------------------------------------------------- Comment By: Daniel Berger (djberg96) Date: 2010-01-08 04:40 Message: I'd like to see a release soon as well so I can start using the declarative test syntax. :) Regards, Dan ---------------------------------------------------------------------- Comment By: Kouhei Sutou (kou) Date: 2009-12-18 20:26 Message: What about this page? http://test-unit.rubyforge.org/test-unit/Test/Unit/Assertions.html If you send a "reference card" with RDoc format, we will include it in the next release! If you want to get a new release, I will release it. Are you in a hurry? ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=21859&aid=27582&group_id=5650 From noreply at rubyforge.org Sat Jan 9 12:46:54 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Sat, 9 Jan 2010 12:46:54 -0500 (EST) Subject: [test-unit-tracker] [ test-unit-Feature Requests-27582 ] Reference card Message-ID: <20100109174654.D38A01858289@rubyforge.org> Feature Requests item #27582, was opened at 2009-12-16 23:17 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=21859&aid=27582&group_id=5650 Category: None Group: None Status: Closed Priority: 3 Submitted By: David MARCHALAND (marchaland) Assigned to: Nobody (None) Summary: Reference card Initial Comment: Hi, Can you provide a "Reference card" with next distribution that list all assertions with corresponding prototype as well as notification, omission & pending? I ask for that but not sure you have an easy way to generate such refcard based on your source code. Thanks, David PS: For when is plan next release? ---------------------------------------------------------------------- >Comment By: David MARCHALAND (marchaland) Date: 2010-01-09 17:46 Message: Hi, Thanks for release 2.0.6. I had a look on Assertions documentation page and this latter is well documented to use it as a reference card. BR ---------------------------------------------------------------------- Comment By: Kouhei Sutou (kou) Date: 2010-01-09 11:13 Message: I've released 2.0.6. ---------------------------------------------------------------------- Comment By: Daniel Berger (djberg96) Date: 2010-01-07 19:40 Message: I'd like to see a release soon as well so I can start using the declarative test syntax. :) Regards, Dan ---------------------------------------------------------------------- Comment By: Kouhei Sutou (kou) Date: 2009-12-18 11:26 Message: What about this page? http://test-unit.rubyforge.org/test-unit/Test/Unit/Assertions.html If you send a "reference card" with RDoc format, we will include it in the next release! If you want to get a new release, I will release it. Are you in a hurry? ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=21859&aid=27582&group_id=5650 From noreply at rubyforge.org Thu Jan 14 16:55:03 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Thu, 14 Jan 2010 16:55:03 -0500 (EST) Subject: [test-unit-tracker] [ test-unit-Bugs-27690 ] test-unit-2 presence hinders test-spec execution Message-ID: <20100114215503.A26273C8043@rubyforge.org> Bugs item #27690, was opened at 2010-01-14 22:55 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=21856&aid=27690&group_id=5650 Category: None Group: None Status: Open Resolution: None Priority: 3 Submitted By: Diego E. Petten? (flameeyes) Assigned to: Nobody (None) Summary: test-unit-2 presence hinders test-spec execution Initial Comment: I've got some problems running test-spec ( http://gemcutter.org/gems/test-spec ) when the test-unit gem is installed for any given implementation. Similar problems seem to apply to random other situations. In the case of test-spec, it seems like the default for standalone packages has been moved from :dir to the new :load? and while :dir works (sorta), :load does not seem to detect any test for indirect-descendents (which happens to be used by test-spec and other software as well). Could you please look into this problem and find a solution or a compromise? Thanks in advance, Diego ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=21856&aid=27690&group_id=5650 From noreply at rubyforge.org Fri Jan 15 21:17:40 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Fri, 15 Jan 2010 21:17:40 -0500 (EST) Subject: [test-unit-tracker] [ test-unit-Bugs-27690 ] test-unit-2 presence hinders test-spec execution Message-ID: <20100116021740.8C7C9177993D@rubyforge.org> Bugs item #27690, was opened at 2010-01-15 06:55 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=21856&aid=27690&group_id=5650 Category: None Group: None Status: Open Resolution: None Priority: 3 Submitted By: Diego E. Petten? (flameeyes) Assigned to: Nobody (None) Summary: test-unit-2 presence hinders test-spec execution Initial Comment: I've got some problems running test-spec ( http://gemcutter.org/gems/test-spec ) when the test-unit gem is installed for any given implementation. Similar problems seem to apply to random other situations. In the case of test-spec, it seems like the default for standalone packages has been moved from :dir to the new :load? and while :dir works (sorta), :load does not seem to detect any test for indirect-descendents (which happens to be used by test-spec and other software as well). Could you please look into this problem and find a solution or a compromise? Thanks in advance, Diego ---------------------------------------------------------------------- >Comment By: Kouhei Sutou (kou) Date: 2010-01-16 11:17 Message: Could you provide a sample script that shows your problem? ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=21856&aid=27690&group_id=5650