CAST was buzzing with talk of the BBST online software testing courses. The coming months have opportunities for everyone – including YOU – to get involved!
“Now, I know why my bugs were deferred. Bring it on. My bug reports are stronger.”
“The bug advocacy course was practical and gave powerful tools and concepts for immediate use at work. Its relevance in testing is immense and the real life exercises used in the course amplify the learning several times. In Juran’s assessment of quality as ‘Fitness for use’, this course fits the industry’s needs completely.”
“BBST Bug Advocacy takes learning about testing to another level. It is filled with practical exercises that I could use right away in my task as a tester . . . I recommend it to anyone who is serious about software bugs.”
“The BBST courses are truly excellent, and of course, an unbelievable value. As a hands-on tester and test manager, I often have to manage PM / customer expectations as well as train and mentor my testing teams. As a consultant I often have to articulate the challenges and benefits of testing to my clients. In this context – even putting aside the significant personal learning benefits of these courses – they deliver immense value: the clarity and power of the arguments they present is exemplary.” – Iain McCowatt
“All testers – those who are new to testing and those who have been testing for years – will gain skills and “take home” knowledge to share with project teams and apply immediately in order to improve the effectiveness of their day-to-day work. I can’t wait for my next BBST course!”
Bug reports are not just neutral technical reports. They are persuasive documents. The key goal of the bug report author is to provide high-quality information, well written, to help stakeholders make wise decisions about which bugs to fix. Key aspects of the content of this course include:
- Defining key concepts (such as software error, quality, and the bug processing workflow)
- the scope of bug reporting (what to report as bugs, and what information to include)
- Bug reporting as persuasive writing
- Bug investigation to discover harsher failures and simpler replication conditions
- Excuses and reasons for not fixing bugs
- Making bugs reproducible
- Lessons from the psychology of decision-making: bug-handling as a multiple-decision process dominated by heuristics and biases.
- Style and structure of well-written reports