For several years now, I’ve maintained one iTunes database even when I buy a new computer or reformat. It’s been important to me to have things like play count, last played, date added, etc. because it helps me create dynamic playlists for work. So I was stoked when I found out about Last.fm because it does more tracking of that kind of thing and throws a social networking edge in there to boot. (more…)
Archive for the ‘Development’ Category
Well, it’s time to say farewell to the old theme. I liked it while I had it, but I needed a three column theme so I have room for all the widgets I keep adding. Also, I’ve recently decided that my favorite color is red, so this seemed fitting. I like this theme because it’s simple, clean, and easy to tweak.
So you’ve found the bug and know exactly (hopefully) how to reproduce it. Now you’ve got to tell someone, and that someone is likely the developer. So how do you go about documenting and submitting the bug? Here are some helpful tips for the end of the process:
It’s great to find bugs, but if you can’t or don’t explain them properly to the person responsible for fixing the bug, at best you’ll confuse/frustrate him while wasting his time, and at worst you could prevent the bug from being fixed at all. There are two key principles in documenting a bug. Specificity and perspicuity (or being clear).
Methods for Bug Discovery
There are two primary methods for discovering bugs and. The first method is natural testing, and the second is systematic testing.
There are two perspectives we usually test from. The customer and the back end user. Both of these perspectives need to be tested extensively so we can be sure orders can be placed and all normal functions performed. So when you start testing, pick a perspective and test from it. Don’t meander around, aimlessly pushing buttons and links. While you may find bugs this way, it’s generally a waste of your time. We need to target the important processes and move down from there.
For the first installment of this series, I’d like to set some parameters. So here are some basic definitions:
Beta Testing – For the purpose of this series, this will refer to testing a website to find bugs (see definition 2) and document them.
Bug – Anything that deviates from the standard or normal function. It’s anything that is not how it’s supposed to be, not just something that generates an error. (more…)