A friend of mine, Justin Searls, recently released a project that he and his team have been working on for a while, to replace both sinon.js and the built-in jasminebdd mock / spy tooling. The project, TestDouble.js (apparently named after his company, TestDouble?) aims to provide a simplified, clean, yet powerful mock / stub / […]
I was all set to npm publish the next version of my Rabbus library. All my tests were passing, and everything was good to go. Then I decided to write just one more test… just in case. I mean, the code works fine. I don’t need to write this test. I know I don’t need […]
Over the weekend, I attended and spoke at the Nodevember conference in Nashville, TN. At this conference, I spoke on the subject of destroying your IDE in favor of using smaller, light-weight, flexible and composable tooling like Grunt, Grunt-Contrib-Watch and others. I had a strongly positive amount of feedback from the session, which is always […]
I found myself needing to run a debugger on my Jasmine specs. The really fun part is that I am running these specs through the grunt-jasmine-node plugin for grunt. This means what I really need to do is run a debugger on top of grunt, and have it hit my Jasmine specs when they get around to being executed.
In a previous post, I showed how to run browserified unit tests in a headless browser using PhantomJS and grunt-contrib-jasmine. Shortly after posting that, I found myself needing to run a debugger on my tests (because console.log debugging is not sufficient). What to do? How do I get a debugger attached to my grunt-contrib-jasmine specs? […]
I’ve had a number of people ask about testing browserify modules, after I posted about how I’m using browserify with Backbone and Marionette. The truth was, I had not yet looked in to this and I wanted to remedy that. But, when i first started thinking about this, I wasn’t quite sure what to do. […]