This post, for now brings about the conclusion of my futures in software testing series. I’ll use it as a summary and it’ll be my main link as a jump off point for the topic. I have plans to extend both the content and make it easier to use so stay tuned.
The purpose of the series was to propose an alternative mechanism by which testers can develop their own education. It relies on a self assessment model that helps testers identify areas of improvement. It never mandates process, procedures, techniques, approaches or models. It’s entirely focused on showing testers what they can do.
The following posts talk about the problem with a common model (ISTQB) and established the basics of the disciplined approach to software testing:
The next eight topics covered each of the disciplines and what their concepts, techniques and responsibilities are:
- The Automation Tester
- The Performance Tester
- The Business Domain Knowledge Tester
- The Test Lead & Test Manager
- The Behavioural & Functionality Tester
- The Infrastructure & Integration Tester
- The User Interaction Tester
- The Security Tester
Finally I described some real stories of testers I know who have used this mechanism to right their software testing careers.
It’s been a thorough joy coming up with this content and I’ve learn an amazing amount about how people learn and about testing.
This is an on-going, never ceasing project; so help contribute or check back and get the latest on each discipline.
You never know, you may just learn something.
|Ryan Boucher is a Software Inquisitor and is passionate about it. You can find a whole raft of articles and anecdotes about software testing and other topics he gets excited about.|