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.
