About awesome-quality-assurance-roadmap

A curated learning roadmap for aspiring Software Quality Assurance and Quality Automation Engineers. It serves as a starting point for building a career in software testing, covering the essential concepts, skills, and methodologies needed in the field. The resource emphasizes understanding how software components work and integrate, and developing the critical skill of identifying unintended behaviors through systematic testing. The roadmap includes a structured learning path for QA and software testing, a downloadable generic test plan sample PDF suitable for various software testing deliveries, and professional advice for practitioners. Key guidance includes not trusting test code you have not seen fail, mastering manual testing before jumping into automation, ensuring test code actually validates functionality, avoiding the common pitfall of trusting 200 OK server responses for unauthorized API calls, and writing test code that is readable, reusable, and does not require additional testing. Ideal for begi

f

Published by

fityanos

Visit View Profile

README.md

View on GitHub

❗The updated roadmap can be seen on https://fityanos.github.io/anasfitiani/qaroadmap.html

Awesome Quality Assurance Roadmap

Introduction

Testing is an essential phase in any product life cycle; whether if it's a food, cars, or software production line, the outcomes should match what's expected and meet, satisfy the need that we created the product for.

Having a solid base of understanding how the software components work and integrate with each other as well as gaining the skills of breaking things is an essential skill-set for any QA engineer. Software testing is the art of investigating the software and finding any unintended behavior that might generate undesired scenarios.

Below you can find the path for QA and software testing learning curve which you might need to start the journey.

Test Plan Sample

One of the most important documents to be generated by the QA team is the test plan, as the team will acting blindly without; not knowing the criteria, the starting point, or even when to perform different testing types can risk the whole delivery and causes bad code delivery.

Test plan sections and content can vary based on project and delivery nature, therefore, the attached test plan PDF is considered as a generic one that serves all software testing delivery purposes.

Attached PDF can be found here test_plan_sample.pdf for downloading.

The Road Map

QA Engineer Road Map 2022

Advices

Don't trust a test code that you didn't see it failing.
Understand software testing and do not jump into automation; personally, I classify automation as an efficient way to work a redundant task. make sure to properly design your test criteria and later on, you can automate to achieve the previous.
Automation is not more than documenting manually written tests and engineering it in a way the code will be readable, understandable, and reusable.
Make sure that your testing code is actually testing something.
Your testing code shall not require testing.
200~OK is not always okay; Do not rely only on server status while testing, getting 200 status for an unauthorized API call is risking your software security.

Contributing

See the contributing.md for details on how to contribute.

awesome-quality-assurance-roadmap