: New: Link: Testing Culture vs goto fail

Catching software bugs requires testing culture. It's a mix of technology and attitude. Technology should make running tests easy. Attitude should encourage you to write tests—hey, it's easy so it's worth it. Attitude should raise an eyebrow at code that's hard to test: maybe that difficulty should be fixed.

Mike Bland wrote an article about how testing culture could have caught the "goto fail" bug. He reduces the test down to its essence; you don't have to fight with some testing framework to set up this test. He talks about a way to structure code to make it easier to test. He talks about a culture in which that test would have arisen naturally—not in an after-the-disaster writeup.

It's Part 1 of what's going to be a multi-part article: Goto Fail, Heartbleed, and Unit Testing Culture.

Tags: link programming

blog comments powered by Disqus