A new blog post on the series where Michael Bolton talks about the taboo of the Test Cases many people have. Here, he suggests how to communicate what was tested, and the findings of the testing, without using Test Cases, changing the focus to more face-to-face conversations.
If you consider testing a simple and straightforward, with no need for deep cognitive capacity and knowledge, then, if you want to automate testing (whatever you consider it), you probably don’t need people with extensive experience in coding, correct? I’ve talked a bit about it on 3 Reasons Why Automation Will Not Save You
On how our daily work in a solution can create a bias that removes our focus from the company/team goal to the product itself. Products are tools - and tools should be discarded when they don’t help us to achieve goals.