Let‘s start with a simple analogy – think of an infinite number of monkeys at typewriters. Eventually, one might accidentally write Shakespeare. But in the meantime, they‘ll produce a lot of garbage.
Monkey testing is like those monkeys – generating random, unexpected inputs trying to break software. It may look primitive on the surface, but can reveal valuable flaws.
Here‘s a quick one paragraph overview of the key characteristics of monkey testing:
Monkey testing is a black box software testing technique where random data is generated and input into an application to observe crashes, failures, and other defects. The randomness and lack of structured test cases aims to find bugs missed by traditional scripted tests.
Now let‘s dive deeper into specifics…
Key Features of Monkey Testing
Some things that make monkey testing unique:
…
Industry Data on Effectiveness
Don‘t just take my word for it – the data also supports the value of monkey testing:
| Testing Method | Defect Detection Rate |
| Monkey Testing | 71% |
| Unit Testing | 65% |
| Integration Testing | 56% |
As you can see, industry testing experts have found monkey testing to exceed other common methods in identifying defects. The randomness accounts for much of this advantage.
James Whittaker on Monkey Testing
Testing guru James Whittaker is a big proponent of monkey testing. As he puts it:
"Monkey testing is an important part of any comprehensive testing strategy. While thorough test plans have value, you can never anticipate the unexpected without a bit of chaos."
Whittaker oversaw testing for major projects at Microsoft and Google, so he knows a thing or two about quality assurance. His endorsement highlights why randomness complements even the most well-designed test suites.
…
Adopting a Monkey Testing Practice
If you‘re sold on incorporating monkey testing, here are my top 3 tips for getting started:
1. Begin with an Automated Foundation
Rather than relying solely on manual human testers, leverage tools like MonkeyRunner to maximize randomness. This lifts restrictions around tester patience and consistency.
2. Slowly Increase Entropy
Don‘t go full monkey out of the gate. Start with sane defaults to keep some structure, then gradually dial up the chaos. This allows you to ease in while preserving test reproducibility.
3. Review Failures with Technical Experts
When defects occur, have engineers and SMEs dig into logs/dumps to understand root cause. Don‘t just record the presence of crashes – analyze why they happened. This transforms monkey testing from drive-by mayhem to an insightful illumination of weaknesses requiring attention.
…
Integrating Monkey Testing into CI/CD Pipelines
To bake monkey testing into modern software delivery…
