QA ATL 2020 Day 2.5http://www.qaatl.com From the YouTube description… Too often, conference sessions don’t allow enough time for questions and answers. For QA ATL, Michael Bolton will deliver a conference session that is nothing but questions and answers. Michael invites you to ask him anything about topics near and dear to him, including (but not limited to) developing test strategy, recognizing problems in products, thinking critically, analyzing risk, applying tools, … Read more
Klára Jánová is a dedicated tester who studies and practices and advocates Rapid Software Testing. Recently, on LinkedIn, she said: I might EXPECT something to happen. But that doesn’t necessarily mean that I WANT IT/DESIRE for IT to happen. I even may want it to happen, but it not happening doesn’t have to automatically mean that there’s a problem. The point of this post: no more “expected results” in the … Read more
This post serves two purposes. It is yet another installation in The Series That Ate My Blog; and it’s a kind of personal exploration of work in progress on the Rapid Software Testing Guide to Test Reporting. Your feedback and questions on this post will help to inform the second project, so I welcome your comments. As a tester, your mission is to evaluate the product and report on its … Read more
Michael Bolton, software testing consultant and trainer at DevelopSense, chats with TechWell Community Manager Owen Gotimer about what software testing is, the responsibility testers can and should accept, and the importance of communication in software development.
Continue the conversation with Michael and Owen (@owen) on the TechWell Hub (http://hub.techwell.com/)! Royalty Free Music from Bensound
As promised, (at last!) here are some follow-up notes on previous installments in the series that starts here. Let’s revisit the original question: Do you perform any exploratory testing on APIs? How do you do it? To review: there’s a problem with the question. Asking about “exploratory testing” is a little like asking about “vegetarian cauliflower”, “carbon-based human beings”, or “metallic copper”. Testing is fundamentally exploratory. Testing is an attempt … Read more
Over the last several years, a set of ideas and activities have been dumped into a big bucket called “Agile Software Development”. Agile development has hit mainstream recognition. Yet there is often uncertainty and turmoil around what “Agile development” means, in theory and in practice, and the confusion affects Agile projects and the people in them. There have been some discussion points, such as Mike Cohn’s Agile Testing Pyramid and Marick, Crisipin and Gregory’s Agile Testing Quadrants, and many people have found them helpful. Yet James Bach and Michael Bolton, authors of Rapid Software Testing, still hear testers expressing a good deal of pain over the role of the tester and the structures of testing activity in Agile projects.
Rapid Software Testing (RST) is a skill set and a mindset focused on doing the fastest, least expensive testing that still completely fulfills the mission. From RST’s perspective, testing is testing and Agile is context. Whether you adopt RST, working in Agile contexts, or neither, or both, Michael Bolton will provide observations and advice on how to adapt your testing to fit mission context you’re in.
Bio
Michael Bolton is a consulting software tester and testing teacher who helps people to solve testing problems that they didn’t realize they could solve. He is the co-author (with senior author James Bach) of Rapid Software Testing, a methodology and mindset for testing software expertly and credibly in uncertain conditions and under extreme time pressure. Michael has 25 years of experience testing, developing, managing, and writing about software. For almost 20 years, he has led DevelopSense, a Toronto-based testing and development consultancy.
Presented by esterzy.pl
Summary: Loops of exploration, experimentation, studying, modeling, and learning are the essence of testing, not an add-on to it. The intersection of activity and models (such as the Heuristic Test Strategy Model) help us to perform testing while continuously developing, refining, and reviewing it. Testing is much more than writing a bunch of automated checks to confirm that the product can do something; it’s an ongoing investigation in which we … Read more
There’s much talk these days of DevOps, and Agile development, and “shift left”. Apparently, in these process models, it’s a revelation that testers can do more than test a built product, and that testers can and should be involved at every step of development. In Rapid Software Testing, that’s not exactly news. From the beginning, we’ve rejected the idea that the product has to be complete, or has to pass … Read more
For QASymphony, Quality Jam 2017: Michael Bolton “A Ridiculously Rapid Introduction to Rapid Software Testing”
Structured Programming, Total Quality Management, Agile, Scrum, Devops—and after all this time, projects still stumble and products still drive us crazy.
Want a quick idea for a burst of activity that will reveal both bugs and opportunities for further exploration? Play “Honest Manual Writer”. Here’s how it works: imagine you’re the world’s most organized, most thorough, and—above all—most honest documentation writer. Your client has assigned you to write a user manual, including both reference and tutorial material, that describes the product or a particular feature of it. The catch is that, … Read more