The Pessimistic Views Of Rapid Software Testing

5488 Words 22 Pages
Register to read the introduction… Rapid Software Testing

Copyright © 1995-2014, Satisfice, Inc.

Jerry Weinberg has suggested that “it works” may mean “We haven't tried very hard to make it fail, and we haven't been running it very long or under very diverse conditions, but so far we haven't seen any failures, though we haven't been looking too closely, either.” In this pessimistic view, you have to be on guard for people who say it works without checking even once to see if it could work.

Rapid Software Testing

Copyright © 1995-2014, Satisfice, Inc.

MIP’ping is a way of bug reporting when you aren’t confident in the value of a bug. It’s an acronym that stands for “mention in passing.” To MIP a bug is to report it in an informal and inexpensive way, such as through email or chat. That way, you don’t get in trouble for not reporting it, and you don’t get in trouble for over-reporting it.

Black flagging is the opposite of that. When you black flag a bug you put a lot of energy into the report. You may write a white paper about it, and call a meeting to discuss it. This is necessary in cases where a simple bug report won’t capture the extent of the risk, or when you feel that fixing the bug will not adequately deal with the risks related to that bug (perhaps because you feel that the product may need a comprehensive redesign. Usually we black flag a bug when it seems to represent a cluster of potentially related problems that
…show more content…
Perform a task, from start to finish, that an end-user might be expected to do. Look for anything that might confuse, delay, or irritate a reasonable person. Documentation Tour: Look in the online help or user manual and find some instructions about how to perform some interesting activity. Do those actions. Improvise from them. If your product has a tutorial, follow it. You may expose a problem in the product or in the documentation; either way, you’ve found something useful. Even if you don’t expose a problem, you’ll still be learning about the product. Sample Data Tour: Employ any sample data you can, and all that you can—the more complex or extreme the better. Use zeroes where large numbers are expected; use negative numbers where positive numbers are expected; use huge numbers where modestly-sized ones are expected; and use letters in every place that’s supposed to handle numbers. Change the units or formats in which data can be entered. Challenge the assumption that the programmers have thought to reject inappropriate data. Variables Tour: Tour a product looking for anything that is variable and vary it. Vary it as far as possible, in every dimension possible. Identifying and exploring variations is part of the basic structure of my testing when I first encounter a product. Complexity Tour: Tour a product looking for the

Related Documents