Comments on: QUnit and the Command Line: One Step Closer,

By: Simple JavaScript Testing with QUnit

Simple JavaScript Testing with QUnit — Fri, 17 May 2013 10:05:20 +0000

[…] post from 2010 about QUnit and the command line, which indicates that it’s rather difficult to do. The post mentions that the library […]

By: Simple Javascript Unit Testing with QUnit

Simple Javascript Unit Testing with QUnit — Thu, 16 May 2013 03:52:03 +0000

[…] post from 2010 about QUnit and the command line, which indicates that it’s rather difficult to do. The post mentions that the library […]

By: Simao Mata

Simao Mata — Tue, 02 Aug 2011 15:52:50 +0000

Hello,

Did you try using env.js? http://www.envjs.com/

Works fine until I need to test backbone js methods. I am using localStorage for persistance but env.js doesn’t support it.

By: Jeff Sawatzky

Jeff Sawatzky — Fri, 01 Apr 2011 21:22:59 +0000

Have you looked at PhantomJS? Since it is a headless WebKit browser, it may solve your issues with Rhino not being a full browser?

By: QUnit-CLI: Running QUnit with Rhino « Two Guys Arguing

QUnit-CLI: Running QUnit with Rhino « Two Guys Arguing — Sat, 27 Nov 2010 04:59:47 +0000

[...] on 11.26.10 Previously I talked about wanting to run QUnit outside the browser and about some issues I ran into. Finally, I have QUnit running from the command line: [...]

By: benjaminplee

benjaminplee — Mon, 08 Nov 2010 14:59:04 +0000

Thanks for catching that. The repo with my sample code is here https://github.com/benjaminplee/QUnit-CLI

Currently it is just the bare essentials of what I was doing as I tried things out. More to come soon.

By: Jörn Zaefferer

Jörn Zaefferer — Mon, 08 Nov 2010 09:33:31 +0000

PS: The link to your GitHub repo links to jquery/qunit/issues…

By: Jörn Zaefferer

Jörn Zaefferer — Mon, 08 Nov 2010 09:26:37 +0000

The browser assumptions are certainly an interesting problem to tackle. Though it looks like this is just an implementation issue, not something you really struggled with.

QUnit.done getting called too often is a bug: https://github.com/jquery/qunit/issues/issue/53

For the truthiness problem, use strictEquals(), or just === or !== with ok().

The argument order doesn’t really matter, its wrong in any case. Named arguments (ala Python) would solve that: equals(actual=whatever, expected=”my value”)
In JavaScript we’d have to use an object literal, in Java it gets even worse, so we’re stuck with having to look up the argument order each time.

By: Make JavaScript tests part of your build: QUnit & Rhino « Two Guys Arguing

Sun, 07 Nov 2010 05:08:39 +0000

[...] I have posted about some of my progress and setbacks here. Tagged with: javascript, qunit, [...]