Increasing Code Coverage Metrics--without testing trivial methods :-)
In this screencast I'm discussing the quality of a lean and reasonable Java EE project with low code coverage. To satisfy the QA metrics I'm using the chrome developer tools to increase the code coverage metrics persistently, without writing useless unit tests for getters / setters, default constructors or other trivial methods.
See you at: http://workshops.adam-bien.com, http://airhacks.io or at least at: http://airhacks.tv.