- From: Marcos Caceres <w3c@marcosc.com>
- Date: Tue, 25 Sep 2012 15:17:45 +0100
- To: Frederick.Hirsch@nokia.com, Robin Berjon <robin@w3.org>
- Cc: spec-prod@w3.org
On Tuesday, September 25, 2012 at 11:00 AM, Robin Berjon wrote:
> On 24/09/2012 19:22 , Frederick.Hirsch@nokia.com (mailto:Frederick.Hirsch@nokia.com) wrote:
> > What is the best way to test a change to biblio.js before pulling it
> > into the main build?
>
>
> In general I only do the most cursory test of biblio.js: I check the
> syntax. For that, I just do node bibrefs/biblio.js. If it doesn't blow
> up then the syntax is fine.
By blow up, I assume Robin means (in some javascript console, like Chrome's dev tools):
var x = {"ID" : "the citation"};
x["ID"];
//returns what is expected
Throws no syntax errors. That's the easiest way to check.
I also then check that the whole bliblo.js works using the method above before doing the pull request.
Received on Tuesday, 25 September 2012 14:21:59 UTC