We're looking to promote one of our customer service agents into a testing role. Right now they roughly go through our deploys in a staging environment prior to it going live. They've requested more formal training in QA testing, and I am looking for ways to get them started on this journey. One question I saw (Training a non-QA employee to do QA) helped a bit, but some of the answers seem out of date. At least one is broken.
Have them learn about:
- Unit vs. Integrated vs. User Acceptance vs Performance testing*
- Boundary Value Testing - https://en.wikipedia.org/wiki/Boundary_testing
- Security Testing - https://en.wikipedia.org/wiki/Security_testing
- Usability and Accessibility* - https://www.w3.org/WAI/intro/usable
- This site and questions like How do you prepare yourself for a testing position?
- Happy, Sad, Optional path testing
- Testing different devices, browsers and versions
- How to file a good bug report - Best guidelines for bug reporting?
- How to capture both screenshots and videos on all devices being tested
- What the company considers to be its key quality metrics
- The four quadrants of Agile testing - https://sqa.stackexchange.com/a/3569/8992
- The Testing Pyramid - Implementing the Test Pyramid as QA
I've done my best to provide links which should be stable for years / decades as they are wikipedia, w3.org, stack exchange, etc.
Note that once they have learned all the above they are exceedingly valuable. You may need to pay them much more and hire additional testers for all the needs they will realize are in their domain - which is also yours.
* Warning - massive topics, be selective in what you apply.
From my personal experience in transitioning from the go-to user support specialist to a more QA-heavy role, I found my involvement in QA and testing activities continue to increase and evolve over time:
- Understanding the QA process/workflow -> how it fits in the end-to-end SDLC
- Writing detailed bug reports -> managing issue tracking system
- Creating user stories and test cases -> test plans and strategies
- Reviewing tech specs -> contributing/collaborating with developers and engineers
- Performing exploratory, ad-hoc tests -> functional, acceptance, smoke, regression testing
- Building empathy with developers/engineers/PMs/BAs and gaining a deep understanding of all the moving parts required to build
Looking back, my foray into QA was pretty informal and organic. Areas I wish I had more formal, in-depth training and guidance in were:
- Crash course in Quality Assurance 101 (back to basics/fundamentals, key concepts and industry terminology)
- More coaching/mentorship from in-house QA specialists, developers/engineers, and networking opportunities around my community (online/offline)
- Knowledge of and exposure to leading QA/Software Testing resources readily available (though this can be discovered through self-education initiatives if the individual is self-motivated)
- Transparency and insight into prospective career paths/tracks for up-and-coming QAs
ISTQB Foundation level should be enough to start https://www.astqb.org/get-certified/istqb-syllabi-the-istqb-software-tester-certification-body-of-knowledge/
As soon as people learn basis Advanced level can be taken.
Syllabuses about 70-100 pages, easy to read.