From: Nazri Ramliy <ayiehere@gmail.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: jaseem abid <jaseemabid@gmail.com>, Jeff King <peff@peff.net>,
git@vger.kernel.org
Subject: Re: [GSOC] Contributing to git.
Date: Mon, 2 Apr 2012 15:32:46 +0800 [thread overview]
Message-ID: <CAEY4ZpNek5-8s6hG8qUos9TfNEn83Hf4KCyCcreY3MM5P9qAkw@mail.gmail.com> (raw)
In-Reply-To: <201203310137.59657.jnareb@gmail.com>
On Sat, Mar 31, 2012 at 7:37 AM, Jakub Narebski <jnareb@gmail.com> wrote:
> Test.Simple and Test.More (http://search.cpan.org/dist/JS-Test-Simple/)
> both output TAP (they are port of Perl's Test::Simple and Test::More);
> part of JS::Test::Simple.
>
> Node.js requires V8 JavaScript engine from Google; if we have that, we
> can as well use e.g. JavaScript::V8x::TestMoreish[2] from CPAN.
>
> Other solutions include using Test::JavaScript (uses SpiderMonkey
> JavaScript engine), or Selenium.
>
> [2] http://search.cpan.org/perldoc?JavaScript::V8x::TestMoreish
Just to add to the discussion, consider these too (descriptions copied
verbatim off their tins):
1. phantomjs[1] - headless WebKit with JavaScript API
2. casperjs[2] - navigation scripting & testing utility for PhantomJS
[1] http://www.phantomjs.org/
[2] http://casperjs.org/
nazri
next prev parent reply other threads:[~2012-04-02 7:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-30 2:49 [GSOC] Contributing to git jaseem abid
2012-03-30 5:26 ` Jeff King
2012-03-30 10:24 ` jaseem abid
2012-03-30 11:05 ` Jakub Narebski
2012-03-30 11:18 ` chaitanyaa nalla
2012-03-30 11:45 ` Jakub Narebski
2012-03-30 11:51 ` chaitanyaa nalla
2012-03-30 12:49 ` jaseem abid
2012-03-30 12:46 ` jaseem abid
2012-03-30 23:37 ` Jakub Narebski
2012-04-02 7:32 ` Nazri Ramliy [this message]
2012-04-02 16:26 ` jaseem abid
2012-04-03 1:39 ` Nazri Ramliy
2012-04-03 9:03 ` Jakub Narebski
2012-03-30 22:39 ` Andrew Sayers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAEY4ZpNek5-8s6hG8qUos9TfNEn83Hf4KCyCcreY3MM5P9qAkw@mail.gmail.com \
--to=ayiehere@gmail.com \
--cc=git@vger.kernel.org \
--cc=jaseemabid@gmail.com \
--cc=jnareb@gmail.com \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).