All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: chaitanyaa nalla <nallachaitu@gmail.com>
Cc: Jeff King <peff@peff.net>, jaseem abid <jaseemabid@gmail.com>,
	git@vger.kernel.org
Subject: Re: [GSOC] Contributing to git.
Date: Fri, 30 Mar 2012 12:45:58 +0100	[thread overview]
Message-ID: <201203301345.59195.jnareb@gmail.com> (raw)
In-Reply-To: <CACeyogeboKPEhsaY357+hBvVquW7kn3ygOk11ZSKvXOt4vkzvQ@mail.gmail.com>

On Fri, 30 Mar 2012, chaitanyaa nalla wrote:

> There are good Opensource tools like
> TestSwarm (jQuery), JSTestDriver(Google). Both are distributed
> javascript testing tools that supports testing on all major browsers.

We don't need _distributed_ javascript testing tool; we need automated
command-line javascript testing tool which we can integrate into git
testsuite (t/).

* TestSwarm is distributed continuous integration testing tool,
  (not necessary for us), and from what I understand it shows results
  as a web page (in a browser).

  It is written in PHP and uses MySQL.

* jsTestDriver looks like something we could use, as it is run from
  command line, and prints results to standard output.

  It requires however a web browser attached (this is not an obstacle:
  having web browser can be prerequisite for such tests)... and is
  written in Java, and as far as I understand doesn't output TAP.


Documentation/CodingGuidelines says:

 - Avoid introducing a new dependency into git. This means you
   usually should stay away from scripting languages not already
   used in the git core command set [...]

So no PHP, and no Java.

-- 
Jakub Narebski
Poland

  reply	other threads:[~2012-03-30 11:46 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 [this message]
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
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=201203301345.59195.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jaseemabid@gmail.com \
    --cc=nallachaitu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.