MeetUp with Michael Bolton | Testing Deep and Shallow
Presented at Nine
The first ever live stream from Nine featuring Michael Bolton
Breaking the Test Case Addiction (Part 9)
Last time, Frieda and I had been looking at visualizations of time spent on various testing activities, include work that foster test coverage of the product (T time), bug investigation and reporting (B time) and setup work to get ready to test, or tidying up afterwards (S time). “So…,” Frieda mused, “I could track T-time, and B-time, and S-time. But I’d be a little worried about watching the clock all … Read more
What is Software Testing? A Conversation with Michael Bolton
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
Breaking the Test Case Addiction (Part 8)
Throughout this series, we’ve been looking at an an alternative to artifact-based approaches to performing and accounting for testing: an activity-based approach. Frieda, my coaching client, and I had been discussing how to manage testing without dependence on formalized, scripted, procedural test cases. Part of any approach to making work accountable is communication between a manager or test lead and the person who had done the work. In session-based test … Read more
The Secret Life of Automation
The Web is abuzz with talk about “automated testing” and “test automation”. Automation comes with a tasty and digestible story: eliminate “manual testing”, and replace messy, complex humanity with reliable, fast, efficient robots! Yet there are many secrets hidden between the lines of the story.
Regression Obsession
Michael Bolton identifies factors to consider when linking the risk of regression to your overall testing strategy.
Breaking the Test Case Addiction (Part 7)
Throughout this series, we’ve been looking at an an alternative to artifact-based approaches to testing: an activity-based approach. In the previous post, we looked at a kind of scenario testing, using a one-page sheet to guide a tester through a session of testing. The one-pager replaces explicit, formal, procedure test cases with a theme and a set of test ideas, a set of guidelines, or a checklist. The charter helps … Read more
Testing without requirements
Sometimes as testers we are asked to work on projects where requirements are either vague or even non-existent, in these cases we need to look for ways to define what to test and how should the system under test behave.
Main takeaways:
– Alternative places to look for requirements
– How to work with stakeholders in order to get the information needed to test the system
– Tips on managing projects where requirements are not clear
For additional webinars and resources: https://www.practitest.com/qa-learnin…
Refactoring the Agile Testing Quadrants
Breaking the Test Case Addiction (Part 6)
In the last installment, we ended by asking “Once the tester has learned something about the product, how can you focus a tester’s work without over-focusing it? I provided some examples in Part 4 of this series. Here’s another: scenario testing. The examples I’ll provide here are based on work done by James Bach and Geordie Keitt several years ago. (I’ve helped several other organizations apply this approach much more … Read more