Using Monkey test tools (3)

Using Monkey test tools (3)

Take technology

2007-11-27

Original: Using Monkey Test tools–how to find bugs cost-effectively through random testing (Noel Nyman)

Smart monkeys usually get knowledge about the product from a state table or model. By randomly traversing the state model, they select options that are valid for the current state, move from one state to another, and then verify that the next expected state is reached. If the model includes error handling status, you can also add illegal input to the "monkey" instruction table.

Stupid monkeys are not the same. ("ignorant monkeys" sound more accurate, but "dumb" sounds more common.) They do not use state tables, they do not know what the current state of the application is being tested, they do not know what input is legal, and what input is illegal. Most importantly, they don't know it's a bug when they hit a bug. Pure stupid monkeys are the best example of Beizer's "Keyboard Mania" test tool, which is not very useful for most projects. "Not so stupid monkeys" is more useful. "Not so stupid monkeys" although they are ignorant of your project, they have some environmental knowledge enough to find bugs like crashes and hangs.

Such a tool has been used for some time. In the early 80 's, the Lisa and Macintosh project team developed a stupid monkey test tool that has a certain knowledge of the Apple operating system. Some developers are asked to bear a certain amount of monkey testing time before releasing their product. Modern test monkeys know more about the operating system than early Apple's "ape" tools.

As a convenient discussion, we think stupid monkeys are ignorant of the procedure, but can understand the environment.