Aldo Calpini wrote:
>
> if by "test harness" you mean prove, then you need to add the -b flag
> (after a successfull "make" or "./Build"), as in:
>
> prove -b t/*
---
I found the above to be very useful in testing after
I read it's manpage. Thanks! Got the twisted tests
to run as well ;-
Gabor Szabo wrote:
> Hi Linda,
>
> On Fri, Mar 1, 2013 at 10:58 AM, Linda W wrote:
>
>> I developed a few tests for a module I was trying to get on to CPAN.
>>
>
> Do you have this code in a public version control system? (I mean Git,
> Subversion, etc.)
> Could you share the link with
David,
> Umm, surely a version of ExtUtils::MakeMaker that is recent enough to
> generate those files will also know to exclude them from 'make dist'.
> Likewise Module::Build.
One would think. But mine appear to have shown up via a "make
manifest" in EUMM a little over a year ago ... I definite
Aldo Calpini wrote:
> I'm wondering how you are including the module in your test... should be
> just a plain:
>
> use My::Module;
My module had it's own tests built-in to it before I tried to put it
on CPAN.
So I'm trying to use it's built-in modules.
I.e. if you make the module runn
I can say in my case I added them manually. There didn't seem to be a
reason not to at the time, and I was just being conscientious.
You know what might be the simplest way to prevent this from happening?
Put a comment line inside the MYMETA files, clearly saying "Do not add
this file to your MANI
Hi Linda,
On Fri, Mar 1, 2013 at 10:58 AM, Linda W wrote:
> I developed a few tests for a module I was trying to get on to CPAN.
Do you have this code in a public version control system? (I mean Git,
Subversion, etc.)
Could you share the link with us so people could take a look and
provide bette
On Fri, Mar 01, 2013 at 11:40:13AM +0100, Aldo Calpini wrote:
> On Fri, March 1, 2013 11:20 am, Linda W wrote:
> > This is the one I was using...
> > But I was in the 't' dir, and my test tried to access
> > the module using ../lib/module.pm
> you should run "make test" from the distribution folder
On Fri, Mar 01, 2013 at 07:21:10AM +0200, Gabor Szabo wrote:
> Tatsuhiko Miyagawa writes:
> http://weblog.bulknews.net/post/44251476706/stop-shipping-mymeta-to-cpan
Umm, surely a version of ExtUtils::MakeMaker that is recent enough to
generate those files will also know to exclude them from 'mak
On Fri, March 1, 2013 11:20 am, Linda W wrote:
> This is the one I was using...
> But I was in the 't' dir, and my test tried to access
> the module using ../lib/module.pm
you should run "make test" from the distribution folder, not from t
(wouldn't work anyway, since the Makefile is not inside t)
Aldo Calpini wrote:
> perl Makefile.PL
> make
> make test <-- here
>
This is the one I was using...
But I was in the 't' dir, and my test tried to access
the module using ../lib/module.pm
I'm not sure, but will I a blib dir if it is a Perl-only distribution?
On Fri, March 1, 2013 9:58 am, Linda W wrote:
> I developed a few tests for a module I was trying to get on to CPAN.
>
> They worked when I ran them in the 't' directory.
>
> But under the test harness, they failed... it couldn't find
> the module files.
if by "test harness" you mean prove, then y
On 1 March 2013 09:37, Gabor Szabo wrote:
> I don't maintain my MANIFEST file manually, but have a MANIFEST.SKIP file
> and run "make manifest" before the releases.
Between this and setting license and repo data, I forsee an evening or
two of housekeeping for my cpan modules.
A
ps sorry Gabor
I don't maintain my MANIFEST file manually, but have a MANIFEST.SKIP file
and run "make manifest" before the releases.
As the MYMETA files are new, they were not matched by any of the rules
in the MANFEST.SKIP file.
I added
MYMETA.*
to the file and re-generated the MANIFEST file using "make manif
# from Aaron Trevena on Friday 01 March 2013:
>A quick google search shows it in one of my modules blush and github
>shows I added it manually and deliberately like an idjit.
Thanks for the input. I tend to `>MANIFEST; ./Build manifest` and have
a check for that in my publish script. I'm curiou
# from Linda W on Friday 01 March 2013:
>They worked when I ran them in the 't' directory.
>...
>When I ran it in 't' , the mod was in "../lib"... but not under the
>test harness?
Hi Linda,
Probably chdir .. and try the tests as t/foo.t -- this will be more like
what you'll see from `./Build tes
On 1 March 2013 08:48, Eric Wilhelm wrote:
> # from Gabor Szabo on Thursday 28 February 2013:
>>/me is releasing new version of Test::Strict to fix this issue and
>>going over the
>>other modules as well.
>
> Hi Gabor,
>
> How did they get into your MANIFEST in this case? Is there a tool which
>
I developed a few tests for a module I was trying to get on to CPAN.
They worked when I ran them in the 't' directory.
But under the test harness, they failed... it couldn't find
the module files.
The test does a chmod +x on the module and runs it as a program.
That produced the test output I lo
# from Gabor Szabo on Thursday 28 February 2013:
>/me is releasing new version of Test::Strict to fix this issue and
>going over the
>other modules as well.
Hi Gabor,
How did they get into your MANIFEST in this case? Is there a tool which
is tending to do this, or are people adding them manuall
18 matches
Mail list logo
