Many times people start out in the world of QA but don't know what to read first or what to read next. That's why I made you a roadmap, also validated by some fellow QAs, and I wanted to share it with you. There's another one floating around on the internet, which I'm leaving here in case you want to check it out: Los enlaces son solo para miembros. Registrate o iniciá sesión
Below I'm going to explain each Stage until you become a Head QA.
Stage 1:
Understand the fundamentals of QA:
- What is QA?
- Why is it implemented in projects?
- Advantages of having a QA on the team
- The importance of having QA in projects
- Difference between a QA and a Tester
- White box, black box and gray box concepts
Study material:
https://underc0de.org/foro/qa-(quality-assurance)/por-que-es-fundamental-el-qa-en-un-proyecto/ (Why QA is essential in a project)
https://underc0de.org/foro/qa-(quality-assurance)/introduccion-a-qa-dictado-por-egg/ (Introduction to QA taught by EGG)
https://underc0de.org/foro/qa-(quality-assurance)/el-abismo-entre-tester-y-qa/ (Tester Vs QA)
Stage 2:
Work methodologies:
- Scrum
- Kanban
- Waterfall
- V-Model
- XP
Documentation on methodologies: https://underc0de.org/foro/qa-(quality-assurance)/scrum-metodologia-agil/
https://underc0de.org/foro/qa-(quality-assurance)/eventos-en-scrum/ (Scrum Events)
Stage 3:
Test cases:
- What are test cases?
- How are they built?
- Test case priorities
- Learn to use test management tools: XRAY, Zepyr, QMETRY, Excel, Test Link, etc
Documentation:
https://underc0de.org/foro/qa-(quality-assurance)/test-case-test-suite-test-plan/ (Test cases - Test Suite)
https://underc0de.org/foro/qa-(quality-assurance)/qmetry-desde-cero/ (QMETRY from scratch)
Los enlaces son solo para miembros. Registrate o iniciá sesión (QARMY test case template)
Stage 4:
Know how to use issue trackers:
- Know how to report bugs
- Know how to use Jira, Trello, Monday, Redmine, etc
Documentation:
Los enlaces son solo para miembros. Registrate o iniciá sesión (QARMY bug report template)
Stage 5:
Learn different functional testing techniques:
- Exploratory testing
- Sanity testing
- Regression testing
- Smoke testing
- Integration testing
- Unit testing (at component level)
Stage 6:
Database testing:
- SQL
- NoSQL
- Learn to use database clients
- Queries (SELECT, GROUP BY, ORDER BY, INER JOIN, etc)
Stage 7:
API Testing
- Testing REST and SOAP APIs
- Postman
- Swagger
Documentation:
https://underc0de.org/foro/qa-(quality-assurance)/testeo-de-apis-con-swagger/ (API testing with Swagger)
https://underc0de.org/foro/qa-(quality-assurance)/testeo-de-apis-con-postman/ (API testing with Postman)
https://underc0de.org/foro/qa-(quality-assurance)/variables-de-entorno-y-variables-globales-en-postman/ (Environment and global variables in Postman)
https://underc0de.org/foro/qa-(quality-assurance)/pruebas-automatizadas-con-postman/ (Automated tests with Postman)
https://underc0de.org/foro/qa-(quality-assurance)/corriendo-colecciones-de-apis-con-newman-y-reporte-en-html/ (Newman and report generation)
https://underc0de.org/foro/qa-(quality-assurance)/obtener-todos-los-endopints-de-una-api-en-un-paso-mas-simple-con-postman/ (Exporting endpoints from Swagger)
Stage 8:
Learn to write test cases in BDD.
At this point we start heading toward the world of automation. BDD is a way of writing test cases with the goal of automating them later.
Stage 9:
Mobile Testing:
- Know the difference between an emulator and a simulator
- Know how to run simulators on the PC (XCODE) for iOS
- Know how to use Browser Stack
- Other tools to emulate Android operating systems: Genymotion, Bluestacks
- Know the difference between a Native APP, PWA and responsive
- Know how to test responsive
- Know how to use CatLog
- Know how to use TestFlight and App Distribution (Firebase)
- Know how to perform Alpha and Beta testing
Stage 10:
Non-Functional Testing: More technical tests
- Stress Testing
- Performance Testing
- Volume Testing
- Security Testing
- Accessibility Testing
- Pixel Perfect
Documentation:
https://underc0de.org/foro/qa-(quality-assurance)/pruebas-de-stress-con-jmeter/ (Stress testing with JMETER)
https://underc0de.org/foro/qa-(quality-assurance)/estres-de-apis-con-jmeter/ (API stress testing with JMETER)
https://underc0de.org/foro/qa-(quality-assurance)/ejecutando-jmeter-desde-la-consola/ (Running JMETER from the console)
Stage 11:
Monitoring and Log review
So that a QA can find the root cause of a problem, it's recommended they know how to review logs and monitor. Some applications for this are:
- Data Dog
- Grafana
- Crashlytics (Firebase)
- CloudWatch
Stage 12:
Using code repositories, in order to automate later and keep the code centralized in a single place.
Some of these tools are:
- GitHub (Github desktop)
- GitLab
- BitBucket
- Know GIT concepts (Important)
Stage 13:
Programming fundamentals: You don't need to be a programming expert to start automating, but you do need programming concepts to be able to do it. Some of the most used languages for automation are:
- Javascript
- Python
- Java
- C#
Stage 14:
Automated testing: These tests are divided into:
- Web Automation
- Mobile Automation
- API Automation
- Desktop Application Automation
Also keep in mind that there are frameworks and technologies that already have everything pre-built so you don't have to do everything from scratch. Some of them are:
- Autoc0de
- Playc0de
- Serenity
- Cypress
- Jasmine
- Playwright
- Robot
- Jest
These frameworks work with Selenium, PlayWright, etc.
Automation with Katalon: https://underc0de.org/foro/qa-(quality-assurance)/pruebas-automatizadas-con-katalon/
Autoc0de:
Automation with Autoc0de: https://underc0de.org/foro/testing-automatizado/automatizaciones-con-autoc0de-desde-cero/
Autoc0de 2.0 Methods Documentation https://underc0de.org/foro/testing-automatizado/autoc0de-2-0-web-documentacion-de-metodos/
Autoc0de Web Repo: Los enlaces son solo para miembros. Registrate o iniciá sesión
Autoc0de Mobile Repo: Los enlaces son solo para miembros. Registrate o iniciá sesión
Autoc0de APIs Repo: Los enlaces son solo para miembros. Registrate o iniciá sesión
Autoc0de Forum: https://underc0de.org/foro/testing-automatizado/
Autoc0de Website: Los enlaces son solo para miembros. Registrate o iniciá sesión
Playc0de:
Playc0de from scratch: https://underc0de.org/foro/playc0de/playc0de-ejecutando-pruebas-con-playwright-desde-0/
Playc0de Repo: Los enlaces son solo para miembros. Registrate o iniciá sesión
Playc0de Website: Los enlaces son solo para miembros. Registrate o iniciá sesión
Cypress:
Getting started with Cypress: https://underc0de.org/foro/qa-(quality-assurance)/comenzando-con-cypress/
First automated tests: https://underc0de.org/foro/qa-(quality-assurance)/como-hacemos-pruebas-automatizadas-de-cypress-en-nuestra-interfaz/
Create a new spec with Cypress: https://underc0de.org/foro/qa-(quality-assurance)/crear-nueva-especificacion-con-cypress-primeros-pasos/
Create a basic example with Cypress: https://underc0de.org/foro/qa-(quality-assurance)/crear-un-ejemplo-real-con-cypress-basico/
Creating a new project with Cypress: https://underc0de.org/foro/qa-(quality-assurance)/creando-un-nuevo-proyecto-con-cypress/
Cypress example using ChatGPT: https://underc0de.org/foro/qa-(quality-assurance)/ejemplo-de-cypress-usando-chatgpt/
Comparison between Cypress and Playwright: https://underc0de.org/foro/qa-(quality-assurance)/comparacion-entre-cypress-y-playwright/
Stage 15:
Continuous Integration: Once we have our automation, it's highly recommended to put it into continuous integration so it runs on its own after each deploy. Some of the most used technologies are:
- Jenkins
- Pipelines
- Travis
- Azure DevOps
Stage 16:
Process Lead:
Once a QA has gained a lot of experience, they can become a process lead. This is someone who understands the business and how to implement QA. They communicate well with the client, know how to manage QA teams, etc.
Often, this process lead doesn't have all the technical knowledge mentioned in the other Stages. But they do have good soft communication skills.
This position is usually offered by the company, or you can apply for an open QA Lead position at some company.
Stage 17:
QA Technical Lead:
This is someone who, over the years, has acquired a lot of technical knowledge (everything mentioned earlier in this roadmap). They know how to implement tests, what kind of tests to do, where to do them, etc.
They also know how to lead teams and teach technical skills to other team members.
Stage 18:
Head QA: The person who coordinates the entire QA area. Usually found in very large companies where there are several QA teams.
Important documentation
QARMY test plan template: https://underc0de.org/foro/qa-(quality-assurance)/modelo-de-plan-de-pruebas-qarmy/
QA Glossary: https://underc0de.org/foro/qa-(quality-assurance)/glosario-para-qas-componentes-web-y-mobile/
Interview questions: https://underc0de.org/foro/qa-(quality-assurance)/mi-primera-entrevista-laboral-!/
Basic QA interview questions: https://underc0de.org/foro/qa-(quality-assurance)/preguntas-basicas-para-una-entrevista-qa/
Well, that's all for now! I hope you like it and find it useful!
Over time I'll keep updating this post with more material!
Los enlaces son solo para miembros. Registrate o iniciá sesión
Below I'm going to explain each Stage until you become a Head QA.
Stage 1:
Understand the fundamentals of QA:
- What is QA?
- Why is it implemented in projects?
- Advantages of having a QA on the team
- The importance of having QA in projects
- Difference between a QA and a Tester
- White box, black box and gray box concepts
Study material:
https://underc0de.org/foro/qa-(quality-assurance)/por-que-es-fundamental-el-qa-en-un-proyecto/ (Why QA is essential in a project)
https://underc0de.org/foro/qa-(quality-assurance)/introduccion-a-qa-dictado-por-egg/ (Introduction to QA taught by EGG)
https://underc0de.org/foro/qa-(quality-assurance)/el-abismo-entre-tester-y-qa/ (Tester Vs QA)
UcRj3HEPSHM
Stage 2:
Work methodologies:
- Scrum
- Kanban
- Waterfall
- V-Model
- XP
0nPXLWHeR3I
Cascada / Waterfall
LfLLacFbfqs
Kanban
sHTUUQQLX64
Full Scrum
fS_dUizpAQM
Scrum Summary
Cascada / Waterfall
LfLLacFbfqs
Kanban
sHTUUQQLX64
Full Scrum
fS_dUizpAQM
Scrum Summary
Documentation on methodologies: https://underc0de.org/foro/qa-(quality-assurance)/scrum-metodologia-agil/
https://underc0de.org/foro/qa-(quality-assurance)/eventos-en-scrum/ (Scrum Events)
Stage 3:
Test cases:
- What are test cases?
- How are they built?
- Test case priorities
- Learn to use test management tools: XRAY, Zepyr, QMETRY, Excel, Test Link, etc
AkaboE7_4WU
Creating test cases
TZCRwh6v_ok
QMETRY
wrrd9EI6x5U
XRAY
Creating test cases
TZCRwh6v_ok
QMETRY
wrrd9EI6x5U
XRAY
Documentation:
https://underc0de.org/foro/qa-(quality-assurance)/test-case-test-suite-test-plan/ (Test cases - Test Suite)
https://underc0de.org/foro/qa-(quality-assurance)/qmetry-desde-cero/ (QMETRY from scratch)
Los enlaces son solo para miembros. Registrate o iniciá sesión (QARMY test case template)
Stage 4:
Know how to use issue trackers:
- Know how to report bugs
- Know how to use Jira, Trello, Monday, Redmine, etc
ImKCRntCx5c
Bug reporting - Best practices
LsB9khxzX6o
Severity - Priority and bug reports in Jira
Bug reporting - Best practices
LsB9khxzX6o
Severity - Priority and bug reports in Jira
Documentation:
Los enlaces son solo para miembros. Registrate o iniciá sesión (QARMY bug report template)
Stage 5:
Learn different functional testing techniques:
- Exploratory testing
- Sanity testing
- Regression testing
- Smoke testing
- Integration testing
- Unit testing (at component level)
Stage 6:
Database testing:
- SQL
- NoSQL
- Learn to use database clients
- Queries (SELECT, GROUP BY, ORDER BY, INER JOIN, etc)
Stage 7:
API Testing
- Testing REST and SOAP APIs
- Postman
- Swagger
PkR75URDdPc
Introduction to APIs
Introduction to APIs
aoENzj1azr0
API Testing with Swagger
API Testing with Swagger
f8i3LPbZ2Sk
Postman Certification from scratch
Postman Certification from scratch
Documentation:
https://underc0de.org/foro/qa-(quality-assurance)/testeo-de-apis-con-swagger/ (API testing with Swagger)
https://underc0de.org/foro/qa-(quality-assurance)/testeo-de-apis-con-postman/ (API testing with Postman)
https://underc0de.org/foro/qa-(quality-assurance)/variables-de-entorno-y-variables-globales-en-postman/ (Environment and global variables in Postman)
https://underc0de.org/foro/qa-(quality-assurance)/pruebas-automatizadas-con-postman/ (Automated tests with Postman)
https://underc0de.org/foro/qa-(quality-assurance)/corriendo-colecciones-de-apis-con-newman-y-reporte-en-html/ (Newman and report generation)
https://underc0de.org/foro/qa-(quality-assurance)/obtener-todos-los-endopints-de-una-api-en-un-paso-mas-simple-con-postman/ (Exporting endpoints from Swagger)
Stage 8:
Learn to write test cases in BDD.
At this point we start heading toward the world of automation. BDD is a way of writing test cases with the goal of automating them later.
soHu_YsXCXg
Gherking - BDD - TDD
Gherking - BDD - TDD
Stage 9:
Mobile Testing:
- Know the difference between an emulator and a simulator
- Know how to run simulators on the PC (XCODE) for iOS
- Know how to use Browser Stack
- Other tools to emulate Android operating systems: Genymotion, Bluestacks
- Know the difference between a Native APP, PWA and responsive
- Know how to test responsive
- Know how to use CatLog
- Know how to use TestFlight and App Distribution (Firebase)
- Know how to perform Alpha and Beta testing
Stage 10:
Non-Functional Testing: More technical tests
- Stress Testing
- Performance Testing
- Volume Testing
- Security Testing
- Accessibility Testing
- Pixel Perfect
Documentation:
https://underc0de.org/foro/qa-(quality-assurance)/pruebas-de-stress-con-jmeter/ (Stress testing with JMETER)
https://underc0de.org/foro/qa-(quality-assurance)/estres-de-apis-con-jmeter/ (API stress testing with JMETER)
https://underc0de.org/foro/qa-(quality-assurance)/ejecutando-jmeter-desde-la-consola/ (Running JMETER from the console)
Stage 11:
Monitoring and Log review
So that a QA can find the root cause of a problem, it's recommended they know how to review logs and monitor. Some applications for this are:
- Data Dog
- Grafana
- Crashlytics (Firebase)
- CloudWatch
Stage 12:
Using code repositories, in order to automate later and keep the code centralized in a single place.
Some of these tools are:
- GitHub (Github desktop)
- GitLab
- BitBucket
- Know GIT concepts (Important)
Stage 13:
Programming fundamentals: You don't need to be a programming expert to start automating, but you do need programming concepts to be able to do it. Some of the most used languages for automation are:
- Javascript
- Python
- Java
- C#
Stage 14:
Automated testing: These tests are divided into:
- Web Automation
- Mobile Automation
- API Automation
- Desktop Application Automation
Also keep in mind that there are frameworks and technologies that already have everything pre-built so you don't have to do everything from scratch. Some of them are:
- Autoc0de
- Playc0de
- Serenity
- Cypress
- Jasmine
- Playwright
- Robot
- Jest
These frameworks work with Selenium, PlayWright, etc.
lgVInoVfcJ4
Playwright workshop from scratch
GINC8zpjMZ8
Cypress from scratch Part 1
2goz7erK_gw
Cypress from scratch Part 2
Playwright workshop from scratch
GINC8zpjMZ8
Cypress from scratch Part 1
2goz7erK_gw
Cypress from scratch Part 2
Automation with Katalon: https://underc0de.org/foro/qa-(quality-assurance)/pruebas-automatizadas-con-katalon/
Autoc0de:
Automation with Autoc0de: https://underc0de.org/foro/testing-automatizado/automatizaciones-con-autoc0de-desde-cero/
Autoc0de 2.0 Methods Documentation https://underc0de.org/foro/testing-automatizado/autoc0de-2-0-web-documentacion-de-metodos/
Autoc0de Web Repo: Los enlaces son solo para miembros. Registrate o iniciá sesión
Autoc0de Mobile Repo: Los enlaces son solo para miembros. Registrate o iniciá sesión
Autoc0de APIs Repo: Los enlaces son solo para miembros. Registrate o iniciá sesión
Autoc0de Forum: https://underc0de.org/foro/testing-automatizado/
Autoc0de Website: Los enlaces son solo para miembros. Registrate o iniciá sesión
Playc0de:
Playc0de from scratch: https://underc0de.org/foro/playc0de/playc0de-ejecutando-pruebas-con-playwright-desde-0/
Playc0de Repo: Los enlaces son solo para miembros. Registrate o iniciá sesión
Playc0de Website: Los enlaces son solo para miembros. Registrate o iniciá sesión
Cypress:
Getting started with Cypress: https://underc0de.org/foro/qa-(quality-assurance)/comenzando-con-cypress/
First automated tests: https://underc0de.org/foro/qa-(quality-assurance)/como-hacemos-pruebas-automatizadas-de-cypress-en-nuestra-interfaz/
Create a new spec with Cypress: https://underc0de.org/foro/qa-(quality-assurance)/crear-nueva-especificacion-con-cypress-primeros-pasos/
Create a basic example with Cypress: https://underc0de.org/foro/qa-(quality-assurance)/crear-un-ejemplo-real-con-cypress-basico/
Creating a new project with Cypress: https://underc0de.org/foro/qa-(quality-assurance)/creando-un-nuevo-proyecto-con-cypress/
Cypress example using ChatGPT: https://underc0de.org/foro/qa-(quality-assurance)/ejemplo-de-cypress-usando-chatgpt/
Comparison between Cypress and Playwright: https://underc0de.org/foro/qa-(quality-assurance)/comparacion-entre-cypress-y-playwright/
Stage 15:
Continuous Integration: Once we have our automation, it's highly recommended to put it into continuous integration so it runs on its own after each deploy. Some of the most used technologies are:
- Jenkins
- Pipelines
- Travis
- Azure DevOps
Stage 16:
Process Lead:
Once a QA has gained a lot of experience, they can become a process lead. This is someone who understands the business and how to implement QA. They communicate well with the client, know how to manage QA teams, etc.
Often, this process lead doesn't have all the technical knowledge mentioned in the other Stages. But they do have good soft communication skills.
This position is usually offered by the company, or you can apply for an open QA Lead position at some company.
Stage 17:
QA Technical Lead:
This is someone who, over the years, has acquired a lot of technical knowledge (everything mentioned earlier in this roadmap). They know how to implement tests, what kind of tests to do, where to do them, etc.
They also know how to lead teams and teach technical skills to other team members.
Stage 18:
Head QA: The person who coordinates the entire QA area. Usually found in very large companies where there are several QA teams.
Important documentation
QARMY test plan template: https://underc0de.org/foro/qa-(quality-assurance)/modelo-de-plan-de-pruebas-qarmy/
QA Glossary: https://underc0de.org/foro/qa-(quality-assurance)/glosario-para-qas-componentes-web-y-mobile/
Interview questions: https://underc0de.org/foro/qa-(quality-assurance)/mi-primera-entrevista-laboral-!/
Basic QA interview questions: https://underc0de.org/foro/qa-(quality-assurance)/preguntas-basicas-para-una-entrevista-qa/
Well, that's all for now! I hope you like it and find it useful!
Over time I'll keep updating this post with more material!