|
|||||
|
It’s been about one year since we introduced Jasmine as our default for Javascript testing. Looking back it’s easy to declare it a success: We test all our new javascript instead of just deciding it isn’t worth the effort. Javascript is broken out into files instead of having the temptation of just leaving it [...] I’ve been running Jenkins as my CI solution for years now, but for the first 6 months at my new job I used it in an entirely new way. The typical CI pattern is you setup to run against checkins to your master branch run all the unit tests, and depending on how sophisticated you [...] Working with my pair yesterday we ran into an issue testing a view that pulled in several partials. In the interest of making progress we punted after about half an hour of trying to setup expectations on the partials and just tested the negative cases where we didn’t have to worry about the partials being [...] My first break of the CI build on a new team came about two weeks into starting the new job. We had made a small change to a dynamically created URL on a single page of the application. Normally this would fall into the category of “too simple to test” for me. My pairing [...] My default rule with mocking is to try to stick to stubs where possible. I don’t enjoy having to setup and verify interactions with mocks, but sometimes you have some code where that’s exactly what you need to do. I’ve used many frameworks in Java over the years from EasyMock to Mockito, but I was [...] |
|||||
|
Copyright © 2013 Musings of a Software Development Manager - All Rights Reserved Powered by WordPress & Atahualpa |
|||||
