Re: module name for test data?
hi, and sorry for the delay to answer... On 09/09/30 01:13 -0700, Ovid wrote: - Original Message From: David Nicol davidni...@gmail.com you could put the word corpus in there somewhere, since you're publishing some test data. For others to use it, who might be looking for test data, that's what a corpus is in test data jargon (i believe.) Test::Corpus::audio::mpd would set an example of publishing test data to CPAN under the Test::Corpus prefix. ++! You know, I never did like this idea of publishing test data to the CPAN, but I ever dislike even more the idea of people stretching it for legitimate uses. The Test::Corpus:: namespace is lovely. If you publish there and folks are reasonably happy with this, let us know and I'll post some stuff to my blog and Perl-QA to get others to know about this namespace (and potentially use it). i followed your advices and just pushed test::corpus::audio::md. now i need to update my other modules to use this instead of embedding the data themselves. If these corpuses (corpi?) can also guarantee a stable interface, we may even be able to guarantee common sets of test data which different *developers* can use, not just modules. To that end, how would we guarantee a stable interface which people could trust, or be able to quickly bail out or skip if there's an incompatible change? hmm, i also provide a module that configures and launches a test mpd automatically. so it's a bit more than just a corpus. anyway, i guess i can even split it further with test::corpus only shipping the data, and the logic in test::audio::mpd. but really not for today! :-) thanks, jérôme -- jque...@gmail.com
Re: module name for test data?
- Original Message From: David Nicol davidni...@gmail.com you could put the word corpus in there somewhere, since you're publishing some test data. For others to use it, who might be looking for test data, that's what a corpus is in test data jargon (i believe.) Test::Corpus::audio::mpd would set an example of publishing test data to CPAN under the Test::Corpus prefix. ++! You know, I never did like this idea of publishing test data to the CPAN, but I ever dislike even more the idea of people stretching it for legitimate uses. The Test::Corpus:: namespace is lovely. If you publish there and folks are reasonably happy with this, let us know and I'll post some stuff to my blog and Perl-QA to get others to know about this namespace (and potentially use it). If these corpuses (corpi?) can also guarantee a stable interface, we may even be able to guarantee common sets of test data which different *developers* can use, not just modules. To that end, how would we guarantee a stable interface which people could trust, or be able to quickly bail out or skip if there's an incompatible change? Cheers, Ovid -- Buy the book - http://www.oreilly.com/catalog/perlhks/ Tech blog- http://use.perl.org/~Ovid/journal/ Twitter - http://twitter.com/OvidPerl Official Perl 6 Wiki - http://www.perlfoundation.org/perl6
Re: module name for test data?
--- On Wed, 30/9/09, Ovid publiustemp-moduleautho...@yahoo.com wrote: From: Ovid publiustemp-moduleautho...@yahoo.com You know, I never did like this idea of publishing test data to the CPAN, but I ever dislike even more the idea of people stretching it for legitimate uses.. What a load of crap. Let me try that again :) You know, I never did like this idea of publishing test data to the CPAN, but I dislike even more the idea of telling people they can't stretch the CPAN for legitimate uses. jeers, Ovid -- Buy the book - http://www.oreilly.com/catalog/perlhks/ Tech blog- http://use.perl.org/~Ovid/journal/ Twitter - http://twitter.com/OvidPerl Official Perl 6 Wiki - http://www.perlfoundation.org/perl6
Re: module name for test data?
Ovid writes: If these corpuses (corpi?) Corpora (similar to opus - opera). Smylers
Re: module name for test data?
On Wednesday 30 Sep 2009 11:35:05 Smylers wrote: Ovid writes: If these corpuses (corpi?) Corpora (similar to opus - opera). For more information see: http://en.wiktionary.org/wiki/corpus Regards, Shlomi Fish -- - Shlomi Fish http://www.shlomifish.org/ The Human Hacking Field Guide - http://shlom.in/hhfg Chuck Norris read the entire English Wikipedia in 24 hours. Twice.
Re: module name for test data?
Jerome Quelin writes: On 09/09/28 20:08 +0100, Paul LeoNerd Evans wrote: ... I'd make sure to include the word Test (capitalised) ... yes, i never capitalize when i'm writing (except code, of course). so the proposed module names would be capitalized correctly, of course. That's what I guessed; apologies if it came across as overly pedantic. But in some ways module names _are_ code, and I've previously encountered users on case-insensitive file-systems writing code with module names all lower-case -- which runs for them, but not elsewhere -- so I thought it worth checking. Smylers
Re: module name for test data?
Hi, On Monday 28 September 2009 18.37.17 Smylers wrote: Jerome Quelin writes: - audio::mpd::common? (even if i don't think that's the best) - audio::mpd::test? this one is already used by a module in audio::mpd, but that's not a problem (i plan to move audio::mpd::test somewhere in t/lib/, so namespace would be free) - audio::mpd::testdata? - audio::mpd::common::test? - data::audio::mpd? - data::audio::mpd::test? - test::audio::mpd? I'd go for the latter (well, with some capital letters!) cos people are used to the idea that Test:: modules are used for testing rather than being part of the 'main function' of your program. But none of those names sound bad -- they're all pretty self- explanatory, so any of them would do. Smylers I'd desagree with Smylers. Test:: is for testing modules while your data is, well data, and very much special to Audio::Mpd. My vote would go to Audio::Mpd::Test::Data::+ whatever you want this would also allow you to keep your current test module where it is. I also believe that minimizing the need to upload the test data (even if it's not too much data) is a great idea. Now you could also delete the test data after the tests. Cheers, Nadim.
Re: module name for test data?
Howdy, - audio::mpd::testdata? - audio::mpd::common::test? - data::audio::mpd? - data::audio::mpd::test? - test::audio::mpd? - is there a namespace for bulk data? test data? If your module is useful to others for testing mpd audio in general, then I would put it in the Test::Audio::MPD namespace. If you just want to silo your module-specific test data, then it should go in Audio::MPD::TestData or similar. Cheers, -- Jonathan Leto jonat...@leto.net http://leto.net
Re: module name for test data?
you could put the word corpus in there somewhere, since you're publishing some test data. For others to use it, who might be looking for test data, that's what a corpus is in test data jargon (i believe.) Test::Corpus::audio::mpd would set an example of publishing test data to CPAN under the Test::Corpus prefix.
Re: module name for test data?
Jerome Quelin writes: - audio::mpd::common? (even if i don't think that's the best) - audio::mpd::test? this one is already used by a module in audio::mpd, but that's not a problem (i plan to move audio::mpd::test somewhere in t/lib/, so namespace would be free) - audio::mpd::testdata? - audio::mpd::common::test? - data::audio::mpd? - data::audio::mpd::test? - test::audio::mpd? I'd go for the latter (well, with some capital letters!) cos people are used to the idea that Test:: modules are used for testing rather than being part of the 'main function' of your program. But none of those names sound bad -- they're all pretty self- explanatory, so any of them would do. Smylers
Re: module name for test data?
On Mon, Sep 28, 2009 at 05:37:17PM +0100, Smylers wrote: Jerome Quelin writes: - audio::mpd::common? (even if i don't think that's the best) - audio::mpd::test? this one is already used by a module in audio::mpd, but that's not a problem (i plan to move audio::mpd::test somewhere in t/lib/, so namespace would be free) - audio::mpd::testdata? - audio::mpd::common::test? - data::audio::mpd? - data::audio::mpd::test? - test::audio::mpd? I'd go for the latter (well, with some capital letters!) cos people are used to the idea that Test:: modules are used for testing rather than being part of the 'main function' of your program. But none of those names sound bad -- they're all pretty self- explanatory, so any of them would do. If the module is for use purely during testing, and serves no other useful purpose, I'd make sure to include the word Test (capitalised) somewhere in its distribution name. The variations on common without test would imply it's some sort of shared useful code to use in production use. -- Paul LeoNerd Evans leon...@leonerd.org.uk ICQ# 4135350 | Registered Linux# 179460 http://www.leonerd.org.uk/ signature.asc Description: Digital signature
Re: module name for test data?
On 09/09/28 20:08 +0100, Paul LeoNerd Evans wrote: If the module is for use purely during testing, and serves no other useful purpose, I'd make sure to include the word Test (capitalised) somewhere in its distribution name. The variations on common without test would imply it's some sort of shared useful code to use in production use. yes, i never capitalize when i'm writing (except code, of course). so the proposed module names would be capitalized correctly, of course. currently, it seems that test::audio::mpd gtes the most votes... jérôme -- jque...@gmail.com