Currently, I am involved with a lot of testing of the software product at my work. This includes trying to duplicate errors to find the source of the problem, documenting bugs and bug fixes, and adding enhancements. Enhancements don’t necessarily ‘fix’ something that is broken, but they make the user experience (UX) better. I have read about testing methodologies before, but never really developed a standard or a specific process, at least not one that I could define. My approach to testing usually includes these questions: what is it supposed to do? does it do that? Yes. OK, good. No. OK, keep testing.
As I’ve been working on a lot of testing, I felt the need to develop some processes around it, some standard questions that I would ask at certain points in the testing process, and even some key pointers. If something (a button, for instance) doesn’t produce the desired results, what is connected to that button? What is supposed to happen? What actually happens?
So, I did a quick Google search and found a wealth of information on software testing methods. I think I’ve been using some of these methods, but just haven’t had the official terms to go along with my process.
Wikipedia provides a large amount of information on software testing. And, did you know there is even an Association for Software Testing? Microsoft provides some great information too. There is also a great website dedicated to software testing – Software Testing Fundamentals. Their About page explains their mission and purpose:
“Software Testing Fundamentals is a platform to gain (or refresh) basic knowledge in the field of Software Testing. The site consists of several articles that have been collected from various resources and experiences. If we are to ‘cliche’ it, the site is of the testers, by the testers, and for the testers. Our goal is to build a resourceful repository of Quality Content on Quality.”
They also have a page devoted to jokes about software testing! I like these guys!
I think that software testing is the investigation into the quality of the software product. The result of this investigation can be used to determine if the product meets the original goals under which it was designed, responds as expected based on both correct and incorrect inputs, and produces the desired results in an appropriate amount of time. Testing involves using a program and evaluating the results. There are testing strategies for both Agile development and traditional phased development.
Oftentimes, testing is focused around finding bugs or defects. Fixing these bugs or defects ultimately improves the quality, and therefore value, of the software product. One statement that I particularly liked on Wikipedia is: “Testing cannot establish that a product functions properly under all conditions but can only establish that it does not function properly under specific conditions.“ I also think it is important to look at your target audience. Who is going to be using your software? Is it a video game or an accounting product? Knowing your audience, and programming to that end, can help make their experience better resulting in a positive review of the software product.
Besides just executing the software to observe and detect bugs, it seems helpful to examine the code also. Does the error occur as the button is pressed or after the button has been pressed? What functions are connected to the button? Are there validation scripts that run when the button is pressed or when the text field has been changed? Those subtle difference could be key in identifying the exact code that causes the bug.
Some bugs or defects occur because of coding errors, but oftentimes bugs develop because requirements for the product change during development. This causes a gap – what has been coded up to this point was based on a particular set of requirements. If the requirements change, the way the product is coded changes. Sometimes bugs are not noticed until the environment is changed. I noticed this when testing software for a product used in the U.S. and in Europe. The date format in the U.S. is mm-dd-yyyy, while the format in Europe is dd-mm-yyyy. In order for the user to experience the software seamlessly whether in Europe or the U.S., the day, month, and year had to be coded in separate fields. If the software is used in the U.S., a function combines those individual fields in the order of month, day, and year. If the software is used in Europe, another function combines those individual fields in the order of day, month, and year. During initial testing, only the U.S. date format was tested (prior to my arrival here), and it seemed to work just fine. However, when switching to European date format, the functions ended up causing infinite Ajax callbacks and some weird cursor activity between the date fields. The software was not originally designed to handle the different date formats and functions were added to try to accommodate the new requirement.
The Cost of Bugs:
There was some mention of the cost of fixing software bugs on Wikipedia, but it was a bit sketchy and not well documented. I believe there are large dollar costs involved with releasing a finished product and then identifying, testing, and fixing bugs, and releasing a patch to fix those bugs. There are also psychological or emotional costs involved – there may be negative feedback or a negative view of your organization when the user (collectively) decides that they can’t trust your product. I’m thinking about the Healthcare.gov website when it was first released. I think the news had a field day with reporting on how the government website was hacked, leading to a feeling of public distrust about the program overall, not just the website. It seems like it would be best to design and architect your software well from the beginning to avoid or reduce the number of bugs that occur. Before widespread release of your software, adequate testing would be invaluable. Knowing that you probably can’t test for every single possible error that could occur (bugs do happen), there should be some process for reporting and fixing bugs and then communicating about upgrades to your users.
Key Things I’ve Learned:
- Only change ONE thing at a time!
- Ask Why!
- Check the details!
- DOCUMENT what you tried AND what the results were!