[ original gist 3 June 2013 ]
The point of agile is lost when teams fixate on roles and responsibilities. Fixed roles (“dev”, “qa”) harm you in the long run – and the long run is always up sooner than you think.
That’s a noisy prelude to my answer to the question: Should QA Write Unit Tests?
[ original gist 4 Aug 2013 ~ short reply on LinkedIn, copied for posterity… ]
TDD for integration tests? YES, but for different reasons than “maintenance” or
In testing, there is test creation and test maintenance. You have to do both if
you want tests to serve you well. Same for any product or tool.
The following joke pokes fun at developers who decouple things arbitrarily or incoherently.
[originally posted 2014-03-27]
[originally posted 2014-03-24]
Here are two quick and dirty examples showing how to preserve
/*** multiline string comments ***/ when using uglifyjs (i.e., uglify 2.0). The first uses the basic uglify cli approach, while the second example uses gulp.
[originally posted 2014-03-14]
eval function and the
Function constructor to highlight their similarities as well as their subtle differences, and how to use them without problems.
[originally posted 2014-03-04]
Getting started with tests takes time because there are many small decisions to make. If you haven’t gone through the whole setup and evolution more than once or twice, it’s easy to get lost or just plain forget.