Comments on: Super fast JS Testing

By: Varun

Varun — Wed, 10 Feb 2010 13:49:09 +0000

Hi,

I installed the plugin in eclipse Galileo yesterday (the latest stable release) . Although, it installed without any issues and i can see it installed through the Help window. there is no js ts driver “view”. No trace of any change to eclipse. What is happening?

By: Karl O'Keeffe

Karl O'Keeffe — Tue, 25 Aug 2009 09:41:29 +0000

Nothing shows up in the Aptana error logs I’m afraid, it just doesn’t seem to know the plugin exists.

I’ve moved to using Eclipse, and the plugin works fine.

I haven’t been able to work out how to run the tests on every save. Any ideas?

By: Shyam

Shyam — Thu, 13 Aug 2009 15:27:08 +0000

Yeah, the output formatting is one thing I need to fix. The problem with click and jump to file is actually a much harder one that it seems, in that people may name their JS files and the name of the test cases differently, in which case we would actually have to parse each and every JS file to find which editor window to open. Not too hard, but will have to give it a try. Would be great if you could file these in the Issues for the Google code project page, along with an eclipse label.

And fixed the update url, thanks for that.

By: Shyam

Shyam — Thu, 13 Aug 2009 15:24:58 +0000

I haven’t tried with Aptana, I have only tried with the inbuilt text editor and the web development suite that comes with Eclipse. I can try it out. In the meantime, if you can open your error log and send me any errors that JS Test Driver might have caused, that would be great. Just email it to me.

By: Toni

Toni — Thu, 13 Aug 2009 13:06:40 +0000

Oh, and forgot to say that the update site url on the project page is wrong, there’s and extra ‘*’.

By: Toni

Toni — Thu, 13 Aug 2009 13:05:17 +0000

Thanks! I was excited to see the plugin codes in SVN earlier this week as I discovered JsTestDriver. I already have a bunch of js unit tests in qunit compatible format running on top of rhino + env.js and I’m planning on making them run on top of JsTestDriver instead, with the QUnitAdapter. Looks really promising.

The plugin looks great, but the output of failed tests looks quite garbled. Basically JSON with all the escape characters.

Would it also be possible to make the file names clickable in the stack trace, as Firefox reports the file name and line number, so you could get directly to the failed source file and line.

The message box contents could also be updated to give the proper output on single click of the tests instead of current double click. And maybe if the focus is on a module name or the line identifying the browser the output could contain all log outputs for all tests in the module/all tests.

Great stuff! I’m waiting for updates!

By: Karl O'Keeffe

Karl O'Keeffe — Thu, 13 Aug 2009 08:43:47 +0000

Do you know if this plugin will work with Aptana?

I’m currently using Aptana for my Javascript development, but I’m having trouble installing the JS Test Driver plugin.

I have installed the plugin, but it doesn’t show up in the Window > Show View > Other menu, or the Preferences pane.

Any ideas?

Thanks,

Karl