|
|||||
|
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 [...] 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 [...] I came across a note of mine from last year on my baseline expectations for developers: All code is checked into source control on an hourly basis or at most daily. Every project has an automated build. (Maven, Ant) All projects are setup in continuous integration (Hudson) All code follows the current Java/Groovy coding [...] According to a Forester report the multiple IDEs for Java developers is standard practice: While Eclipse is common, it won’t become the only Java IDE in enterprise IT shops any time soon. Less than one out of five Java developers have a single primary Java IDE and no other. – Jeffery S. Hammond (Forrester Research) [...] |
|||||
|
Copyright © 2013 Musings of a Software Development Manager - All Rights Reserved Powered by WordPress & Atahualpa |
|||||
