fityanos / awesome-quality-assurance-roadmap Goto Github PK

Typo in spelling of Functional. Please fix. let me know if i can help

Understanding that the main goal of software testing is to find or detect bugs or defects as much as possible before releasing to the Production.

The section of understanding of Test Cases and Scenarios is incorrect:

"Test Cases are clearly written and documented"

1. Depends on what test technique you are using. Some test techniques don't use written words, they use diagrams instead. Others like combinatorial and domain testing use only values (numbers, words, letters, characters, etc).
2. Unless you are doing old school, traditional test management, you shouldn't structure test cases as procedures. If you are mainly using exploratory testing your documentation will look a whole lot different than someone doing traditional test management.

"you can cover hire possibilities"

1. What does this mean?

Cant able to view the pdf of === > [awesome-quality-assurance-roadmap]

• Glass Box (white box), Grey Box and Black Box are approaches to software testing, not strategies.
• Strategies are plans of action. So for example in one testing strategy you could employ multiple approaches, both black box and glass box.

• I'd rename Testing Types to be Test Techniques
• Since you are only listing a few, I'd actually summarize as "My favorite, Top 12, etc, something to give the reader a sense this is a small subset of the techniques"

The road map can reach out to many QA Engineers as well as people looking forward to starting a career in.

Translating the description and text within readme can be beneficial.

Hi I really like your roadmap. Great work 👍

You can add KarateFramework(KarateDSL) to API Automation Framework section.
And Locust.io to Load & Performance Test section.

For details :

• Karateframework : https://github.com/intuit/karate
• Locust : https://locust.io/

Great work so far!
I would suggest that Accessibility Testing should be added under Non-Functional Testing section.

In more detail this includes a knowledge of:

• WCAG (W3C Web Content Accessibility Guidelines) - https://www.w3.org/WAI/standards-guidelines/wcag/
• Screen reader technology such as NVDA or JAWS (Windows), VoiceOver (Mac)
• Checklists via the a11y project - https://a11yproject.com/
• Accessibility checker browser plugin tools such as WAVE, Axe, WCAG Color contrast checker or Dark Mode checker
• Automated pipeline tooling such as pa11y - https://pa11y.org/

Happy to assist in adding these and contributing.

The README layout is a bit weird, with

1. Introduction (spelled wrong)
2. Test Plan Document sample
3. You should create a new section entitled Roadmap or QA Engineer Roadmap

You should add tools for generating end-to-end automated tests. There is an open-source tool called KEPLOY which generates automated test cases and data mocks.

website: https://keploy.io/
github: https://github.com/keploy/keploy
video: https://youtu.be/-XQuaeZANnk