I'd like to share the recent progress on JSAN::Prove.
JSAN::Prove is a perl package which provide 'jsan-prove' executable - analog of usual prove.
The package is built as a small Catalyst application. After startup, it maps current directory to development server, then launch supported on current platform browsers. Browsers are pointed to 't/index.html' (as it mapped), which contain Test.Run-based harness.
After all tests were ran, harness report the result to server - 'pass' or 'fail'
After results from all started browsers were collected, server stops and return the value to calling program.
Current implementation just return 1 if all tests were successful or 0 otherwise.
On May 13, 2009, at 5:16 AM, Nickolay Platonov wrote:
> Hello all,
> I'd like to share the recent progress on JSAN::Prove.
> JSAN::Prove is a perl package which provide 'jsan-prove' executable > - analog of usual prove.
> The package is built as a small Catalyst application. After startup, > it maps current directory to development server, > then launch supported on current platform browsers. Browsers are > pointed to 't/index.html' (as it mapped), > which contain Test.Run-based harness.
Very cool. Could it also support Test.Harness.Browser? Or have a directive (perhaps in META.json) to point it at an alterante file, such as 'test/index.html'?
> After all tests were ran, harness report the result to server - > 'pass' or 'fail'
Does it send all of the TAP data, too?
> After results from all started browsers were collected, server stops > and return the value to calling program.
> Current implementation just return 1 if all tests were successful or > 0 otherwise.
Guys, anyone is looking to hire a remote senior perl or javascript developer
?
Looking to quit my job for a remote job. A sample of my work:
http://code.google.com/p/crossxhr/wiki/CrossXhr
Thanks,
Boris Reitman
2009/5/14 David E. Wheeler <da...@justatheory.com>
> On May 13, 2009, at 5:16 AM, Nickolay Platonov wrote:
> > Hello all,
> > I'd like to share the recent progress on JSAN::Prove.
> > JSAN::Prove is a perl package which provide 'jsan-prove' executable
> > - analog of usual prove.
> > The package is built as a small Catalyst application. After startup,
> > it maps current directory to development server,
> > then launch supported on current platform browsers. Browsers are
> > pointed to 't/index.html' (as it mapped),
> > which contain Test.Run-based harness.
> Very cool. Could it also support Test.Harness.Browser? Or have a
> directive (perhaps in META.json) to point it at an alterante file,
> such as 'test/index.html'?
> > After all tests were ran, harness report the result to server -
> > 'pass' or 'fail'
> Does it send all of the TAP data, too?
> > After results from all started browsers were collected, server stops
> > and return the value to calling program.
> > Current implementation just return 1 if all tests were successful or
> > 0 otherwise.
On Thu, May 14, 2009 at 9:19 PM, David E. Wheeler <da...@justatheory.com>wrote:
> On May 13, 2009, at 5:16 AM, Nickolay Platonov wrote:
> > Hello all,
> > I'd like to share the recent progress on JSAN::Prove.
> > JSAN::Prove is a perl package which provide 'jsan-prove' executable > > - analog of usual prove.
> Very cool. Could it also support Test.Harness.Browser? Or have a > directive (perhaps in META.json) to point it at an alterante file, > such as 'test/index.html'?
Yes, sure, other harnesses can be supported too, with minimal additions. Currently the communication between 'prove' and 'harness' is very simple - harness just supposed to report, when all tests are finished, by performing a http request on the url like: "/proven/FireFox/pass" or "/proven/FireFox/fail"
