Posts tagged “goto fail”
14 posts total. See Filtering and Navigation for tips on how to find the bits in which you're interested.
Subscribe to posts tagged "goto fail":
- 14 posts
- 3 posts
- »
My original "goto fail" article has been published online and in print by the Communications of the ACM, the flagship journal of the ACM.
- »
While writing the tests for the "goto fail" and Heartbleed bugs, I stumbled upon an xUnit-like pattern for writing tests without a framework.
- »
The OpenSSL team has accepted my offer to help improve its unit/automated testing, and now I'm recruiting people to help in the effort.
- 3 posts
- »
My original "goto fail" article has been published online by ACM Queue.
- »
Martin Fowler invited me to contribute an article to his website making a case for unit testing in the wake of "goto fail" and Heartbleed.
- »
The Google Testing on the Toilet team has published my episode about the Heartbleed bug, and other fronts are showing signs of progress
- 4 posts
- »
A letter to cybersecurity expert Dan Geer regarding the role of unit testing in helping to avoid errors in security-critical software
- »
The Google Testing on the Toilet team has published my episode about the Apple SSL bug, and I explain why this is for the greater social good.
- »
A Testing on the Toilet-inspired article about the Heartbleed bug and how it could have been prevented
- »
The Heartbleed bug has me seeing red just as much as Apple's SSL bug did, because it's another serious bug that could've been caught by a test
- 3 posts
- »
Turns out I couldn't let the Apple SSL bug go quite yet, as I've submitted an article to Communications of the ACM for consideration
- »
Hopefully the Apple SSL bug is out of my system, having given an AutoTest Boston lightning talk and written a Testing on the Toilet-esque article
- »
I've published a new article on AutoTest Central about the Testing Grouplet's Small, Medium, and Large test size schema, and more on the Apple bug.
- 1 post
- »
Apple's recent SSL security bug compelled me to write a blog post for AutoTest Central illustrating how unit testing could've helped prevent it