Comments for ZeaLake http://www.zealake.com Software Consulting Sun, 07 Apr 2013 21:58:21 -0700 hourly 1 http://wordpress.org/?v=3.4 Comment on No line of your JavaScript code uncovered by Lars http://www.zealake.com/2012/12/25/no-line-of-your-javascript-code-uncovered/#comment-861 Lars Sun, 07 Apr 2013 21:58:21 +0000 http://www.zealake.com/?p=739#comment-861 I have added a new blog post that demonstrates how to use Istanbul together with Jasmine, so you can <a href="http://www.zealake.com/2013/04/07/run-all-your-javascript-jasmine-tests-on-every-commit/" rel="nofollow">run all your JavaScript Jasmine tests on every commit</a> I have added a new blog post that demonstrates how to use Istanbul together with Jasmine, so you can run all your JavaScript Jasmine tests on every commit

]]> Comment on No line of your JavaScript code uncovered by Afonso Franca http://www.zealake.com/2012/12/25/no-line-of-your-javascript-code-uncovered/#comment-827 Afonso Franca Fri, 22 Feb 2013 13:47:51 +0000 http://www.zealake.com/?p=739#comment-827 Hi, I'm the creator of grunt-qunit-cov plugin and I'm here to announce it is working with grunt 0.4. Check it out: https://npmjs.org/package/grunt-qunit-cov Hi,
I’m the creator of grunt-qunit-cov plugin and I’m here to announce it is working with grunt 0.4. Check it out: https://npmjs.org/package/grunt-qunit-cov

]]> Comment on Lightweight code reviews using TortoiseSVN by Lars http://www.zealake.com/2011/12/30/lightweight-code-reviews-using-tortoisesvn/#comment-822 Lars Wed, 06 Feb 2013 18:26:11 +0000 http://www.zealake.com/?p=240#comment-822 @MikeC, you are right, this will not work if you rely on bugtracker integration. I believe <a href="http://www.zealake.com/2010/08/22/dont-track-bugs/" rel="nofollow">bugs should be fixed, not tracked</a>. @MikeC, you are right, this will not work if you rely on bugtracker integration. I believe bugs should be fixed, not tracked.

]]> Comment on Lightweight code reviews using TortoiseSVN by Mike C http://www.zealake.com/2011/12/30/lightweight-code-reviews-using-tortoisesvn/#comment-821 Mike C Wed, 06 Feb 2013 17:32:44 +0000 http://www.zealake.com/?p=240#comment-821 It seems that what you're doing here is <em>overriding</em> the BUGID feature. By using BUGID as REVIEWER, you've lost the ability to have the actual BUGID used, e.g. as a link to the issue in the bugtracker. Maybe useful for you, but FAIL for anyone who is actually using a bugtracker and wants Tortoise to link to it. It seems that what you’re doing here is overriding the BUGID feature. By using BUGID as REVIEWER, you’ve lost the ability to have the actual BUGID used, e.g. as a link to the issue in the bugtracker. Maybe useful for you, but FAIL for anyone who is actually using a bugtracker and wants Tortoise to link to it.

]]> Comment on Lightweight code reviews using TortoiseSVN by Lars http://www.zealake.com/2011/12/30/lightweight-code-reviews-using-tortoisesvn/#comment-817 Lars Thu, 17 Jan 2013 14:00:48 +0000 http://www.zealake.com/?p=240#comment-817 I am using TSVN 1.7.10. Do you have the bugtraq:label property comitted to the SVN properties of the root folder, as shown in the final screen shot? See also my comment above. If you still cannot get it to work, email me (http://www.zealake.com/contact/) some screenshots of your setup. I am using TSVN 1.7.10. Do you have the bugtraq:label property comitted to the SVN properties of the root folder, as shown in the final screen shot? See also my comment above. If you still cannot get it to work, email me (http://www.zealake.com/contact/) some screenshots of your setup.

]]> Comment on Lightweight code reviews using TortoiseSVN by Alex http://www.zealake.com/2011/12/30/lightweight-code-reviews-using-tortoisesvn/#comment-816 Alex Thu, 17 Jan 2013 07:48:32 +0000 http://www.zealake.com/?p=240#comment-816 HI, I am using TSVN version 1.7. Yhough during checkin it is asking for reviewer name , I cannot see these feilds in the log window HI, I am using TSVN version 1.7. Yhough during checkin it is asking for reviewer name , I cannot see these feilds in the log window

]]> Comment on No line of your JavaScript code uncovered by Lars http://www.zealake.com/2012/12/25/no-line-of-your-javascript-code-uncovered/#comment-809 Lars Fri, 04 Jan 2013 19:11:27 +0000 http://www.zealake.com/?p=739#comment-809 Thanks for posting! It looks interesting. There also seems to be a <a href="https://github.com/taichi/grunt-istanbul" rel="nofollow">grunt plugin for Istanbul</a>. Thanks for posting! It looks interesting. There also seems to be a grunt plugin for Istanbul.

]]> Comment on No line of your JavaScript code uncovered by Ariya http://www.zealake.com/2012/12/25/no-line-of-your-javascript-code-uncovered/#comment-805 Ariya Thu, 03 Jan 2013 15:59:12 +0000 http://www.zealake.com/?p=739#comment-805 I also recommend looking at <a href="https://github.com/yahoo/istanbul" rel="nofollow">Istanbul</a>, a new coverage tool which can also track branch coverage and produce LCOV report. My blog post about it: <a href="http://ariya.ofilabs.com/2012/12/javascript-code-coverage-with-istanbul.html" rel="nofollow">JavaScript Code Coverage with Istanbul</a>. I also recommend looking at Istanbul, a new coverage tool which can also track branch coverage and produce LCOV report. My blog post about it: JavaScript Code Coverage with Istanbul.

]]> Comment on Automated build for your front-end JavaScript code by Kory Cunningham http://www.zealake.com/2012/12/25/automated-build-for-your-front-end-javascript-code/#comment-803 Kory Cunningham Fri, 28 Dec 2012 23:34:37 +0000 http://www.zealake.com/?p=731#comment-803 Excellent article with some very useful information, especially so with the inclusion of the Grunt watch utility. On the topic of end-to-end UI testing, one direction I have been experimenting with as of late is using a framework like QUnit, and writing unit tests that are actually closer to functional tests by emulating user interaction via JavaScript events. This is similar as far as the end goal to UI testing through tools such as Selenium, but allows the developer/tester to have full control over the UI through which it is testing. With that, I have the ability to mock any AJAX requests during test execution time, fire any DOM events, and do any sort of DOM inspection that I want, through JavaScript. I'm currently trying out this strategy with a feature that requires a user to be able to draw elements in SVG/Canvas/VML (dependent on browser support), and thus far as proven to be pretty quick and very stable. Excellent article with some very useful information, especially so with the inclusion of the Grunt watch utility.

On the topic of end-to-end UI testing, one direction I have been experimenting with as of late is using a framework like QUnit, and writing unit tests that are actually closer to functional tests by emulating user interaction via JavaScript events. This is similar as far as the end goal to UI testing through tools such as Selenium, but allows the developer/tester to have full control over the UI through which it is testing. With that, I have the ability to mock any AJAX requests during test execution time, fire any DOM events, and do any sort of DOM inspection that I want, through JavaScript. I’m currently trying out this strategy with a feature that requires a user to be able to draw elements in SVG/Canvas/VML (dependent on browser support), and thus far as proven to be pretty quick and very stable.

]]> Comment on Automated build for your front-end JavaScript code by Lars http://www.zealake.com/2012/12/25/automated-build-for-your-front-end-javascript-code/#comment-802 Lars Fri, 28 Dec 2012 01:03:07 +0000 http://www.zealake.com/?p=731#comment-802 For another project I am using Backbone where a View will populate a Template. On one hand I can unit test the view with a mock template to assert what expectations the view have about the template, see an example here: https://github.com/larsthorup/pluto/blob/master/src/test/tests/views/session.test.js On the other hand I can unit test the actual template to assert that the expectation the view have about the template is satisfied, see an example here: https://github.com/larsthorup/pluto/blob/master/src/test/tests/views/session.html.test.js And then I can do actual end-to-end UI testing, but since they will be slow and brittle I only want a few of those for smoke testing purposes. And yes: A JSCrunch plugin for WebStorm would be absolutely awesome! For another project I am using Backbone where a View will populate a Template. On one hand I can unit test the view with a mock template to assert what expectations the view have about the template, see an example here:
https://github.com/larsthorup/pluto/blob/master/src/test/tests/views/session.test.js
On the other hand I can unit test the actual template to assert that the expectation the view have about the template is satisfied, see an example here:
https://github.com/larsthorup/pluto/blob/master/src/test/tests/views/session.html.test.js

And then I can do actual end-to-end UI testing, but since they will be slow and brittle I only want a few of those for smoke testing purposes.

And yes: A JSCrunch plugin for WebStorm would be absolutely awesome!

]]>