Etsy's interesting approach to managing a large test suite, annotations marking potentially troublesome integration tests: "flaky", "database", "network", "sleep" and "slow".

HBase and Haystack; all data LZO-compressed; very interesting approach to testing -- they 'shadow the real production workload into the test cluster to test before going into production'. This catches a 'high percentage' of issues before production. nice

This is the future of code review. Commit directly from your git checkout to the Gerrit code-review system; change is immediately web-visible and enters the review workflow; at the same time, Jenkins checks out the proposed change and runs the test suite; once it's approved, it automatically gets checked in. Brilliant!

some amazing details of Stuxnet's apparent background. 'By the accounts of a number of computer scientists, nuclear enrichment experts and former officials, the covert race to create Stuxnet was a joint project between the Americans and the Israelis, with some help, knowing or unknowing, from the Germans and the British.'

huh. Test-driven development is slower than traditional write-first-test-at-the-end development, but it results in less bugs. Grokcode theorise that its big win is amortising the cost of testing throughout the product iteration, hence reducing the temptation to skip testing when the crunch phase happens

continuous-integration system was accidentally run against the production db. result: the entire production database got wiped. ouuuuch

XBox style achievements for Python's 'nose' unit testing framework, eg. 'Major Letdown: all tests in a suite of at least 100 pass except the last.' genius!

we do something similar in SA