Geoffrey Young wrote:
However, most perl tests don't care about TAP, they use Test::More and
Test::Harness and happen to exchange data via TAP. If Test::More and
Test::Harness decied to use "YAP" (YAML Anything Protocol? :), then most
applications would probably never notice.
most _perl_ appli
Tels wrote:
My idea was to build _only_ the database, and do it right, simple and easy
to use and then get everyone else to just use the DB instead of fiddling
with their own. (simple by having the database being superior to every
other hack thats in existance now :-)
I even got so far as to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Moin Tim,
On Tuesday 11 July 2006 18:34, Tim Bunce wrote:
> I needed some code to trawl through a directory tree parsing perl
> modules and scripts to determine their dependencies.
>
> The closest existing CPAN code was Module::Dependency but it fell
Aargh! It gets annoying that the reply goes directly to the author rather than
the list.
-- If this message is a response to a question on a mailing list, please send
follow up questions to the list.
Web Programming with Perl -- http://users.easystreet.com/ovid/cgi_course/
- Forwarded Me
I needed some code to trawl through a directory tree parsing perl
modules and scripts to determine their dependencies.
The closest existing CPAN code was Module::Dependency but it fell short
of what I needed. The original author (P Kent) has passed over
maintenance to me. My latest release is:
On Jul 11, 2006, at 09:21, Ovid wrote:
Java programmers typically use jUnit. C programmers have libtap
available. PHP tests often use TAP (don't know the name) and
Javascript has Test.Simple, though it parses the test results
directly and then outputs TAP (if I recall correctly).
It bot
> However, most perl tests don't care about TAP, they use Test::More and
> Test::Harness and happen to exchange data via TAP. If Test::More and
> Test::Harness decied to use "YAP" (YAML Anything Protocol? :), then most
> applications would probably never notice.
most _perl_ applications would ne
Aside from the fact that many languages are already using the TAP protocol and
we'd create something they *don't* use, what happens when my 4,000 test lines
all of a sudden become 16,000 test lines because the format has been changed?
Do you pay for CPU time on a per-newline basis? :)
Goo
Ovid wrote:
> - Original Message From: Jonathan Rockway <[EMAIL PROTECTED]>
>
>> What else is TAP targeted to? C / C++ / Java?
>
>
> PHP tests often use TAP (don't know the name)
almost all of the php test frameworks now offer TAP support - see
http://search.cpan.org/dist/Test-Harn
- Original Message
From: Jonathan Rockway <[EMAIL PROTECTED]>
> What else is TAP targeted to? C / C++ / Java?
Java programmers typically use jUnit. C programmers have libtap available.
PHP tests often use TAP (don't know the name) and Javascript has Test.Simple,
though it parses the
if i recall correctly, syck doesn't handle utf-8/16. does/will tap
care about that?
That's true -- I think Audrey patched the perl version to work properly,
but I forgot that other languages are without that functionality. Ruby
doesn't properly support Unicode either, so Unicode support pro
- Original Message
From: Jonathan T. Rockway <[EMAIL PROTECTED]>
> However, if you wanted to make *me* happy ;), why not make the whole
> darn thing a YAML stream like this:
> ---
> test: Test whether foo + bar = baz
> result: ok
> sequence: 1
> ---
Aside from the fact that many langua
On 7/11/06, Jonathan T. Rockway <[EMAIL PROTECTED]> wrote:
Ian Langworth wrote:
> I mentioned YAML with a pretense I failed to mention -- that we
> wouldn't parse the YAML. That's already been done, and there are
> plenty of parsers.
I agree with this. YAML has been done and done again, in ev
On Tue, Jul 11, 2006 at 05:07:02PM +0300, Gabor Szabo wrote:
> From the documentation it is not clear (to me) why is the value of the
> submit
> button sent only if I specify button => button
> The doc only sais this:
>
> If button is not passed, then the "submit()" method is used instead.
Ian Langworth wrote:
I mentioned YAML with a pretense I failed to mention -- that we
wouldn't parse the YAML. That's already been done, and there are
plenty of parsers.
I agree with this. YAML has been done and done again, in every
language. It works, it's tested. I don't think we need E
On Jul 11, 2006, at 7:34 AM, Ian Langworth wrote:
Maybe we don't care. Maybe we can simply add a callback for some
diagnostic_block_analyzer() and, in my own little happy world,
$parser->diagnostic_block_analyzer( sub {
my ($block) = @_;
if ($block =~ m{ \A --- }xs) {
do something
I mentioned YAML with a pretense I failed to mention -- that we
wouldn't parse the YAML. That's already been done, and there are
plenty of parsers.
YAML has clear designations of where it starts and ends. A TAP parser
wouldn't have to look at the diagnostics and guess what it is.
If the data str
On 7/11/06, Andy Lester <[EMAIL PROTECTED]> wrote:
On Jul 11, 2006, at 9:07 AM, Gabor Szabo wrote:
> If button is not passed, then the "submit()" method is used
> instead.
Perhaps it could be clearer then: submit() does not pass any button
unless you specify it.
Yes maybe that, in addit
On Jul 11, 2006, at 9:07 AM, Gabor Szabo wrote:
If button is not passed, then the "submit()" method is used
instead.
Perhaps it could be clearer then: submit() does not pass any button
unless you specify it.
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
On 7/11/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> How can I fix this?
WWW::Mechanize(3pm)
$mech->submit_form( ... )
This method lets you select a form from the previously fetched page,
fill in its fields, and submit it. It combines the form_number/form_name,
set_
the field submit and its value Update does not seem to be sent
to web server. If I add
submit => 'Update',
That's right. It's possible to submit a form without specifying a
submit button. If you want the submit button clicked, then you have
to explicitly specify it.
Also, th
On Tue, Jul 11, 2006 at 01:47:26PM +0300, Gabor Szabo wrote:
> On a form the submit button looks like this:
>
>
>
> when this form is submitted using
>
> $w->submit_form (
>fields => {
>fname => 'Foo',
>});
>
> the field submit and its value Update does not seem to
On a form the submit button looks like this:
when this form is submitted using
$w->submit_form (
fields => {
fname => 'Foo',
});
the field submit and its value Update does not seem to be sent
to web server. If I add
submit => 'Update',
to the list of the
- Original Message
From: Adam Kennedy
> Whoa whoa whoa slow down there folks...
>
> Some people seemed to have misrecognised those keys as YAML.
>
> It was NEVER meant to be YAML.
>
> The idea was to use something more like MIME headers.
Well, regardless of what those lines a
I can see why we wouldn't want to include YAML, and won't cry for *too
long* if it doesn't go in ;), but here are some reasons why I'd like for
full YAML to be a part of the spec:
- marshaling data structures between the application being tested and
the test harness (strings are nice, but full Per
Whoa whoa whoa slow down there folks...
Some people seemed to have misrecognised those keys as YAML.
It was NEVER meant to be YAML.
The idea was to use something more like MIME headers.
We all agreed that we DIDN'T want the format to be too heavy, and going
with MIME or MIME-alike seemed the
26 matches
Mail list logo
