Comments on: There are lots of ways to tests your JavaScript, but there is only one JsTestDriver

By: misko

misko — Wed, 06 Oct 2010 00:21:32 +0000

@geekraver, please email the mailing list js-test-driver@googlegroups.com for JSTD related questions. I am sure that someone will help you there.

By: geekraver

geekraver — Tue, 05 Oct 2010 01:04:14 +0000

Has anyone got the code coverage to work? When using the conf file like in the wiki, I get an exception with 1.2.2:

Exception in thread “main” java.lang.AbstractMethodError
at com.google.jstestdriver.ActionRunner.runActions(ActionRunner.java:62)
at com.google.jstestdriver.JsTestDriver.main(JsTestDriver.java:85)

Also, I have tried JsTestDriver with iPhone/iPad and neither worked. It seems the tests fail on the command line before they complete on the device (I’m not sure that is what is happening but superficially it appears to be).

By: @Lab « Tech Tock

@Lab « Tech Tock — Fri, 09 Jul 2010 11:31:28 +0000

[...] surface, multi hundred project VS Solutions, JavaScript unit testing (jasmine, qunit, selenium, jstestdriver) , Advanced DataGrid [...]

By: Move over Java, I have fallen in love with JavaScript

Move over Java, I have fallen in love with JavaScript — Thu, 08 Apr 2010 04:20:24 +0000

[...] be second nature to you. I run all of my JavaScript tests on every save across most browser using JSTestDriver and all my tests execute under a second. This instant feedback on every save is as good as having [...]

By: Chris

Chris — Tue, 08 Dec 2009 22:12:15 +0000

Thanks Misko. I have left a few issues there for a while now and didn’t get a response. I’ve spent quite some time trying to figure out how to solve those issues myself, and it would be great if I can get a helping hand from those who are working on it. Thanks.

By: Fonetik

Fonetik — Tue, 08 Dec 2009 20:56:50 +0000

“Continues?”

“Continuos?”

-> “Continuous.”

But I agree that’s ridiculous. Inglish shud fainli go fonetik too.

By: misko

misko — Tue, 08 Dec 2009 01:15:24 +0000

@Chirs, sorry for the trouble, but please file an issue here: http://code.google.com/p/js-test-driver/issues/list and someone will look at it. I don’t work on JsTestDriver, I am just the guy who got the project going. Also email the mailing list. js-test-driver@googlegroups.com

By: Chris

Chris — Tue, 08 Dec 2009 01:05:33 +0000

JsTestDriver slows down considerably or even kills the browser when running with JsTestCodeCoverage. The report generated by CodeCoverage is in linux format, therefore Windows users will have to find means to automate that process in order to turn the report into Windows format.

Are there any chances that those issues be looked at soon?

By: misko

misko — Fri, 04 Dec 2009 15:38:06 +0000

Sorry, no NB integration in the works, but perhaps OS community could step in?

By: Meza

Meza — Fri, 04 Dec 2009 15:33:44 +0000

Do you know anything about netbeans integration?