From: jonathan gold Date: 2006-07-14T02:34:34+09:00 Subject: Re: [PATCH] --fqname option to test/unit/autorunner.rb Thanks again for getting back to me. Perhaps my original focus on the fact that I had multiple test cases in the same file was something of a red herring -- I think it's only incidental to the real issue. As I understand the current intent of AutoRunner, and of the testing libraries as a whole, the intent is to have a collector (Collector::ObjectSpace, Collector::Dir, or otherwise) gather up multiple test cases from somewhere. As it is today, the '--testcase' and the '--name' options are in place to allow the user to filter the collection, regardless of how they were collected, in some meaningful way. I believe that these two options leave a gap for what I'm proposing with '--fqname', and so it seems that the patch would be in line with the current spirit of the libraries. Again, perhaps my assumptions are incorrect about the intent of the Collector classes and of how the test suites are expected to function. If that is the case, perhaps the authors most familiar with the testing architecture could help me better understand? jon Berger, Daniel wrote: >>-----Original Message----- >>From: jonathan gold [mailto:dev@samizdatdigital.org] >>Sent: Wednesday, July 12, 2006 3:22 PM >>To: ruby-core@ruby-lang.org >>Subject: Re: [PATCH] --fqname option to test/unit/autorunner.rb >> >> >>Daniel -- >> >>One of my colleagues pointed out that maybe I mistook your initial >>response. To clarify, will this patch be applied to the ruby >>codebase at >>some point? > > > Not unless Matz or Nathaniel Talbott approve it. > > There's no reason you couldn't create your own little library, install > it, and require it separately, is there? Otherwise you'll be waiting > until mid August at the earliest. Given the lack of feedback on your > patch I suspect the general consensus is that you shouldn't put multiple > test case classes in the same file, so there's just no demand for this > patch. > > Regards, > > Dan > > > This communication is the property of Qwest and may contain confidential or > privileged information. Unauthorized use of this communication is strictly > prohibited and may be unlawful. If you have received this communication > in error, please immediately notify the sender by reply e-mail and destroy > all copies of the communication and any attachments. >