Hi,
I recently fell in love with Test::Base and I decided to use
it at $work. Since the 'run filter, compare output' mode
of T::B did not fit my needs, I wrote a small wrapper
(Test::XXX for now...) that
enables to check/establish preconditions, run one or
more actions and check postconditions, f
> On 2005-11-02, Luke Closs <[EMAIL PROTECTED]> wrote:
> >
> > Also, yesterday Test::WWW::Selenium was uploaded to CPAN, so Selenium
> > can now be driven by perl!
>
> Test::WWW::Selenium seems interesting, but I could use an example it
> would be useful to use, versus the standard techniques.
I
> Supposing that Fcntl and O_RDONLY are known to be available, how
> likely is it that O_ACCMODE will also be available? Are there any
> platforms that have O_RDONLY but not O_ACCMODE?
Win32: MinGW ( gcc ) has it
Bcc 5.5 has it
MS VC++ 5 has not
Regards
mattia
On Wed, 16 Jan 2002, Michael G Schwern wrote:
>On Wed, Jan 16, 2002 at 08:45:26AM +0100, Paul Johnson wrote:
>> The fundamental problem here is that BEGIN blocks have to run when they
>> are compiled. This is documented. You can try to work out whether the
>> BEGIN blocks can be rearranged and
> On Sun, Jan 13, 2002 at 10:04:58PM +0100, Mattia Barbon wrote:
> > > $ bleadperl -MO=-qq,Deparse foo.plx
> > > sub BEGIN {
> > > print "foo\n";
> > > }
> > > print "bar\n";
> > >
> > > If B::Deparse can s
> On Sun, Jan 13, 2002 at 07:39:52PM +0100, Mattia Barbon wrote:
> > > perlcc seems to be dropping BEGIN blocks entirely, that's the problem.
> >
> > No, that's correct. Explanation: if I have a module Foo
> >
> > package Foo;
> &g
Now I understand I missed to tell you this fundamental detail before,
sorry.
> perlcc seems to be dropping BEGIN blocks entirely, that's the problem.
No, that's correct. Explanation: if I have a module Foo
package Foo;
$x = 1;
print "AAA";
sub a { $x }
1;
and a main program foo.pl
--
> On Sun, Jan 06, 2002 at 03:56:24PM +0100, Mattia Barbon wrote:
> > > Could you explain again why you need test output while compiling, I'm
> > > not quite following. Assume you had the I_WANT_OUTPUT_DURING_COMPILE
> > > environment variable could you show ho
> On Sat, Jan 05, 2002 at 10:17:34PM +0100, Mattia Barbon wrote:
> > > On Wed, Jan 02, 2002 at 05:37:28PM +0100, Mattia Barbon wrote:
> > > > I don't care for the variable name, but I'd really like
> > > > to have this feature.
> > >
&g
> On Wed, Jan 02, 2002 at 05:37:28PM +0100, Mattia Barbon wrote:
> > I don't care for the variable name, but I'd really like
> > to have this feature.
>
> Would it work ok as a Test::Builder accessor method rather than an
> environment variable?
No, unfortunate
Currently Test::Builder does not print anything
( plan, use_ok results, etc ) if $^C is true. However to test
B::C I'd like to have a way to force the output.
Reason:
#!perl
BEGIN {
print "1..2\n";
print "ok 1\n";
}
print "ok 2\n";
is failing because the
1..2
ok 1
is printed
Currently P::T provides three functions:
output_is/isnt/like, which are wrappers to
Test::More::is/isnt/like.
The failure output is:
t/op/integerok 24/26# Failed test (Parrot/Test.pm at line 73)
it would be nice:
t/op/integerok 24/26# Failed test (t/op/integer.t line xyz)
To do
12 matches
Mail list logo
