Book Shot Down, Riddled With Bugs

Recently I was reviewing (i.e., testing) a manuscript. At one point I saw this heading:

(c) Blah Blah Title

"Where's A and B?" I asked in my comments.

Later I saw it again:

(c) Some Section Title

"Huh? What, this section is copyrighted?" I wondered.

And then again:

(c) Titleist Titly Title

Now I was pretty sure there was something going on. "Oh - that heading is three levels in. Maybe the underlying markup is leaking through?"

Finally I saw it again:

(c) Some Title

But this time it was immediately followed by another heading:

(d) Some Other Title

Aha! "Yup, almost certainly markup is leaking through!"

As I continued through the manuscript I came across many more cases of this "bug", each of which further bolstered my theory that markup was leaking through.

It struck me later that this was a good example of the process I go through when I find a bug. First I notice something odd. Then I try to make the bug happen again (in this case, find it recurring in a different location). I continue testing around the bug, eventually uncovering enough information that I can develop a hypothesis regarding what might be going on. And then I do yet more testing just to make sure I really do understand what's going on. And then I report it and ruin a developer's day. <g/>

Posted by The Braidy Tester at 07:30 AM  Permalink