Michael BoltonDevelopSense (Canada)
Michael is a world leader in the context driven school of software testing. Along with James Bach, he co-authors, teaches and practices Rapid Software Testing. He writes a regular column for Better Software Magazine and was the top rated speaker at STANZ 2005. During 2005 he also co-founded (with Fiona Charles) the Toronto Workshop on Software Testing and also tested almost full-time for a large Canadian financial services organisation. He is the Program Chair of TASSQ, The Toronto Association of System and Software Quality and founded DevelopSense (in 1988) to provide services in program management, testing, configuration management, and professional and personal coaching. Numbers and NarrativesKeynote: Michael Bolton 3:30-4:30 Wellington 12 August and Sydney 15 August On Monday, the testers ran 30 test cases, and found six bugs. On Tuesday, the testers ran 25 test cases, and found five bugs. On Wednesday, they ran 30 test cases, and found three bugs. On Thursday, they ran 50 test cases, and found two bugs. On Friday, they ran 100 test cases, and found no bugs. What inferences or decisions would you make about the project based on this information? Most expert test managers would ask questions, rather than drawing conclusions. The problem, of course, is that the numbers alone don’t tell the story; they don’t tell whether Monday’s tests were significant, whether Thursday’s bugs were trivial, or whether Friday’s tests were relevant. Despite all this, the software business seems to emphasize numbers over narratives. In this presentation, Michael argues that the project team’s stories - with numbers or without them - are the things that make good decisions possible. If we wish to get better at producing software - produced by humans, for humans - we need to get better at thinking critically about numbers, what they appear to measure, and how they can be distorted. More importantly, we need to refocus our priorities on stories, getting better at telling them and listening to them. Two Plus Two and Other Testing Exercises: Setting Context and Identifying OraclesWorkshop: Michael Bolton 9:00-12:20 Wellington 12 August and Sydney 15 August Good testing depends on setting the context in which it's happening. It also depends on heuristics - fallible methods for solving problems - and oracles - principles or mechanisms by which we recognize problems. All oracles are heuristic; no principle or mechanism can guarantee that something is perfect - only that it may satisfy certain requirements for certain people in certain circumstances. In this session, Michael will pose some apparently simple puzzles and problems that exercise critical thinking, systems thinking, and context-driven thinking skills, and will show how those skills can dramatically expand our notions of quality and risk. He'll argue that all testing is heuristic, and that to do better thinking and better testing, we need to broaden our concept of coverage beyond mere code coverage and into test coverage. Critical Thinking Skills for Software TestersOne Day Workshop (optional post conference), Wellington Only 9:00-5:00 Wednesday 13 August with Michael Bolton - Every test must have an expected, predicted result
- Effective testing requires complete, clear, consistent, and unambiguous specifications
- Bugs found earlier cost less to fix than bugs found later
- Testers are the quality gatekeepers for a product
- Repeated tests are fundamentally more valuable
- You can’t manage what you can’t measure
- Testing at boundary values is the best way to find bugs
- Test documentation is needed to deflect legal liability
- The more bugs testers find before release, the better the testing effort
- Rigorous planning is essential for good testing
- Exploratory testing is unstructured testing, and is therefore unreliable
- Adopting best practices will guarantee that we do a good job of testing
- Step by step instructions are necessary to make testing a repeatable process
If you’re a tester or a test manager, you’ve probably heard statements like these touted as universal, unquestionable truths about testing. At best, these bits of mythology and folklore are heuristics - fallible methods for solving a problem or making a decision. At worst, they’re potentially dangerous simplifications or outright fallacies that can threaten a tester’s credibility, a product’s value, or an organisation’s business. Testers live in a world of enormous complexity, scarce information, and extraordinary time pressure. This one-day workshop, presented by Michael Bolton, is designed to teach strategies and skills - questioning skills, critical thinking, context-driven thinking, general systems thinking - that can help testers deal confidently and thoughtfully with difficult testing situations In the workshop, we’ll question the myths of software testing; examine common cognitive biases, and the critical thinking tools that can help to manage them; learn modeling and general systems approaches to manage complexity and observational challenges; and work through exercises that model difficult testing problems - and suggest approaches to solving them. Key Points: - Heuristic approaches are the foundation of human decision-making, in disciplines from education to engineering
- While technical skills are undoubtedly important, applying them successfully requires higher-order skills
- Good testing is less about confirming, verifying, and validating, and more about thinking, questioning, exploring, investigating, and discovering
- As the principles of the Context-Driven School of Software Testing assert, while there are good practices in context, there are no practices that are universally best
Participants are encouraged to bring a laptop computer to the workshop (but sufficient will be available)  |