Re:Unit Testing 101: Are You Testing Your JavaScript?
by akavlie on Wednesday February 23, 2011 @01:06PM
(#2255063)
Yep, you're right!
The author works for Gitorious too.
Despite the fact that this is a Microsoft blog, the content is about the furthest you can get from MS-centric development. Everything he endorses is open source, from sources other than Microsoft. It's kind of amazing.
Re:Unit Testing 101: Are You Testing Your JavaScript?
by DanielRibeiro on Wednesday February 23, 2011 @11:44AM
(#2254720)
Jasmine is also a great framework for testing. It work headless (nodejs) and on web (for those rare times you want to debug a test): http://pivotal.github.com/jasmine/
Re:Unit Testing 101: Are You Testing Your JavaScript?
by cjohansen on Wednesday February 23, 2011 @04:37PM
(#2255920)
Test automation is about preventing bugs, sure. And TDD is about software design. I don't disagree.
However, unit testing is also a nice way to find bugs. In any case, "trapping" a bug like I did in this article is often an effective way of introducing newcomers to what a unit test is.
Re:Unit Testing 101: Are You Testing Your JavaScript?
by MartinCron on Thursday February 24, 2011 @07:39PM
(#2260511)
It was a good article. And using automated tests to trap and isolate problems is an important technique.
I didn't mean my nit-picking to come across as harsh and dismissive. I just get hung up on people talking about writing tests to find bugs, because if that's all it is about, manual testing is generally faster in the short-run.
Re:Unit Testing 101: Are You Testing Your JavaScript?
by fish2000 on Wednesday February 23, 2011 @12:00PM
(#2254788)
Relatedly: what is with MSDN bloggers always referring to themselves as 'junkies'? A "script junkie" probably won't steal their mother's VCR and pawn it so they can get more scripts to stick in their arm. It's kind of a bizarre convention.
Re:Unit Testing 101: Are You Testing Your JavaScript?
by augustl on Wednesday February 23, 2011 @12:58PM
(#2255038)
I prefer JsTestDriver to any other JS test framework out there, for two reasons: 1. You get feedback in your terminal 2. It scales better - run in multiple browsers with one command, output results in junit XML for CI tools, etc.
Despite the fact that this is a Microsoft blog, the content is about the furthest you can get from MS-centric development. Everything he endorses is open source, from sources other than Microsoft. It's kind of amazing.
Test automation is about preventing bugs.
However, unit testing is also a nice way to find bugs. In any case, "trapping" a bug like I did in this article is often an effective way of introducing newcomers to what a unit test is.
I didn't mean my nit-picking to come across as harsh and dismissive. I just get hung up on people talking about writing tests to find bugs, because if that's all it is about, manual testing is generally faster in the short-run.
since when did they develop on firebug, use open source tools, and hudson ci? and practice TDD?