Comments on: My Unified Theory of Bugs

By: Vic UA

Vic UA — Mon, 14 Feb 2011 23:56:07 +0000

Thanks. Nice post.

By: How to Flow Chart, Part 1: Principles | themanthursday.com

How to Flow Chart, Part 1: Principles | themanthursday.com — Sat, 03 Apr 2010 05:01:00 +0000

[...] approach. But as a programmer, you’ll also use flow charting to conquer the dreaded logical bug. (I guess a really smart application of flow charting would be in pre-development, allowing you [...]

By: Swiss army knife for XP PHP projects (defining code quality) | Alternate Illusion

Thu, 25 Mar 2010 17:49:51 +0000

[...] @misko.hevery.com [...]

By: misko

misko — Thu, 23 Jul 2009 11:45:48 +0000

@Mazurov,

JavaScript can be tested with JS unit test frameworks such as http://code.google.com/p/js-test-driver/, so that is a normal logical/wiring problem. CSS is definitely a rendering problem, and we do not have a good solution for that.

By: Mazurov

Mazurov — Thu, 23 Jul 2009 10:16:53 +0000

What about rendering bugs at web applications? For example your a writing code at javascript, which generates complex UI, which should be adapted for all versions of browsers, but you saw that something looks bad. The same for CSS. Are these rendering bugs? Sometimes it’s harder to fix, then logical bugs.

By: Mateusz

Mateusz — Wed, 15 Jul 2009 07:39:50 +0000

Great post and excellent points about “Testable code is better code” and “Unit-tests should HELP refactoring not PREVENT refactorings”. Everyone should understand that in first place

By: Software Testing Categorization

Software Testing Categorization — Tue, 14 Jul 2009 19:35:46 +0000

[...] ‘ifs’ and ‘loops’. This is where the majority of your bugs come from (see theory of bugs). Which is why if you do no other testing, unit tests are the best bang for your buck! Unit tests, [...]

By: Serhiy Yevtushenko

Serhiy Yevtushenko — Tue, 20 Jan 2009 12:08:18 +0000

Hi, I would add two more categories of bugs, but which are not totally code related:Of Understanding: – code does wrong thing may be the right way.Of Omission – code does right things, but not all of them. For this two categories, unfortunately, unit tests does not help.Here the communication, walkthroghs and acceptance tests are of value.

By: Interfacing with hard-to-test third-party code

Interfacing with hard-to-test third-party code — Sun, 04 Jan 2009 19:29:53 +0000

[...] is not so simple, and in most cases I just don’t bother testing it since there can only be wiring bug in that code. There should be no application logic in the LoginServlet since we have moved all of [...]

By: Parag Shah

Parag Shah — Mon, 24 Nov 2008 04:32:46 +0000

Hi Misko,

Very nice post. You have given a clear analysis of the types of bugs and the benefits of testing.