For the third and final post in this series of three reflecting on my personal takeaways from this year’s TestBash Manchester I knew I wanted to focus on Lisi Hocke’s closing talk “A Code Challenge of Confidence” – well, ‘talk’ may be a bit weak given the actual demonstration of her topic live in the session! – but I found there were complimentary threads in what Lisi talked about which chimed with several other talks as well.
It seems strange to those outside our industry that success of our software often lies in the way those of us who build it speak to one another. Surely an application lives and dies on the ability of great coders to write great code… right? Whilst that’s definitely true to some extent, this opens up when we begin to consider what “great” really means. What’s good, valuable, valid is contextual – and our software has to fit the needs of so many different people, each with their own context!
Who wants to fail? In life, we strive to succeed, to do well, and to avoid the pitfalls and dangers we are beset by. As testers however, we need to take a different attitude to failure. Failure pays our bills! Without failure, without the human predisposition to make mistakes, short-sighted or narrow decisions, we are out of a job. So – how do we foster a more accepting attitude towards failure, and learn to not only enjoy it, but encourage it?
A cautionary tale of testing “just the AC” and the things we can learn from one structural engineer’s Very Bad Day
When we talk about testing or QA, we often think of an activity which occurs mostly at the end of the development cycle. Code “drops into test” once it’s merged, tests are prepared ready for this critical (and late) moment when testing can begin in earnest. But in collaborative, agile teams, testing and quality focus […]
QA is a much-maligned acronym which is routinely shorthand for “Quality Assurance” (whatever the hell that actually means – you don’t assure quality by discovering and sharing information about the software), it’s variously “nicked” to stand for Quality Analysis, Question Asking, Quality Activism… but the one which I think is the neatest translation of these […]
This evening I attended an AMA (hosted by Ministry of Testing) by Lisa Crispin, one of my testing heroes and probably the first “named tester” I was ever aware of. It covered a topic close to my heart as an advocacy-focused “Team Glue” tester: Whole-Team Testing. It was a real honour to have a question […]