Re: designing a test suite for multiple implementations
在 2006/8/12 下午 6:15 時，Nicholas Clark 寫到： There's nothing technical stopping the Perl 6 tests being on svn.perl.org, but in a different svn repository from the current repositories, is there? Well, technically yes, except that SVK doesn't support svn:external yet. Setting a svn:external property in the right place on both Parrot and Pugs would mean that both could check out the same testsuite, and both could commit back to it. That's assuming that the new repo, say, http://svn.perl.org/ perl6tests/, can give out commit permissions to parrot and pugs committers, yes. But as Jerry's initial motivation was moving Perl 6 tests to a more official location, and that http://svn.perl.org/perl6/ is the official repo for the Perl 6 design documents, I wonder what's the advantage of hosting the tests in a separate repository. Can you elaborate on that? Thanks, Audrey PGP.sig Description: This is a digitally signed message part
Re: designing a test suite for multiple implementations
在 2006/8/12 上午 3:01 時，jerry gay 寫到： for managed, i have a few ideas. currently, the suite lives in the pugs repo. this is a fine first approximation, but i believe it will soon be time to move this suite (it doesn't make sense to keep the official tests in a non-official repo in the long term.) It's available in the official repo: http://svn.perl.org/perl6/pugs/trunk/t/ If you'd like to change the mirror point to http://svn.perl.org/perl6/t/ That's fine. However, currently the commit bit to that directory does not make it easy for people to help out, and while we can do this through a test-pumpking that reviews each patches and commit by hand, I don't think that's a wise move to take. It's true that you need an openfoundry.org account to write tests for perl 6 may make people feel this to be less official. If we can get a good invitation system to hand out commit bits to svn.perl.org, I'm all for moving everything to there. Robrt had set one up for svn.perl.org/parrot/, but that is currently not actively promoted because of the policy that new committers to that directory has to sign TPF's Contributor License Agreement. If we can relax that policy for the perl6/ or perl6/t/ directory, so we can migrate the openfoundry committers over without them having to sign the CLA by paper -- digitally clickthrough would be fine -- then I agree that we can migrate everything to svn.perl.org. the question is, should it be moved into their own repository, or into the repo of the official perl6 implementation (if such a beast will indeed exist,) Currently the svn.perl.org repo is the most official-sounding one, by the domain name alone. (But I don't understand the motivation for putting the tests with the true implementation -- I thought the idea is to decouple the tests with any implementations.) So I think svn.perl.org is the right choice, if the admins are okay with a more relaxed commit bit policy there. Thanks, Audrey PGP.sig Description: This is a digitally signed message part
Re: What is the Value of t/0-signature.t?
On 3/17/06, chromatic [EMAIL PROTECTED] wrote: Do you mean that it's valuable only for the author to run (perhaps during disttest) and rarely useful for the user to run during installation? Aye. Though I can imagine users who'd like to run them as well... This is after all not that different from the Test::Pod situation, in it that it verifies integrity of the distribution and not the module's function itself. Audrey
Re: What is the Value of t/0-signature.t?
Yuval Kogman wrote: The problem with these is that Module::Signature fails when it should warn if the key is not present in the user's keyring. If this technical issue is solved then regardless of whether or not signature tests are useless (i think they are, but then again i also think i have some modules with Test::Distribution that checks that... so I am a hypocrit ;-) the usability of these tests will be good enough. I think it should be like the standard Test::Pod's pod.t and only run when an env var is set to true. Patches... welcome to Module::Signature. :-) Audrey signature.asc Description: OpenPGP digital signature
