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

:books: The starting point of your career as a Software Quality Assurance Engineer | Quality Automation Engineer :books:

License: Creative Commons Zero v1.0 Universal

testing automation-test roadmap software-testing e2e-testing api-testing quality-engineering qa career awesome-list

awesome-quality-assurance-roadmap's Introduction

Awesome Quality Assurance Roadmap

Introduction
Test Plan Sample
The Road Map
Advices

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

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's People

Contributors

Stargazers

Watchers

Forkers

praful-raut phambaonam anoop2811 taiqixp aamirbhat arjunreddyd krzysztofp89 borun84 realinkyfreak nemanjajeremic irinabehrend peterxiao ardha2008 bobbydowling6 mudasser-nazir ronakgune wbudoyo07 disruptive-tech-community anjeshojha flamato anastasiapast daverockz giangnd2508 chaibizi yblakhina gonnastepsteph tamilabubuteishvili sagargadde bhavanipedavalli knowledgescout voytenkoden1987 mr-sour techbychoice awesome-roadmaps ryota-vl douglas-xie javaboy19 didarulcseiubat17 robbinespu andresoro jakocrivas dariuszjenek balhayer swapnil2593 wiralegawa gnavarroco jemaltech kelvinksps kashanahmed867 muhagunghidayat echosierran isaacmwauramuturi agirishkumar 0exp rsaccoll dragomirstefanacatalina freezesoul aicherepanov joaocarneiro 3024k romanflowerface starworldx irfnrdh evidenceekanem dipakchavda2912 5m477 zawawimanja doquoctoan neo4reo amitsarkar007 zr4x antonyfuentes jwcastillo othreecodes mimik2020 jasminenabilanov starj ceteongvanness cuhavp chebakuvaldos hainguyenh paritie dangleit01 alex-strt hoangtu250891 raffylopez alexbelij nuclearfanta dittrichlucas thejufo lkrust mkappo juniorschmitz fabiocaraujo adsguilherme smily-pirate severinepozzo meta5 mhangman scsiiq

awesome-quality-assurance-roadmap's Issues

Add testing advice

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.

Non-Functional Testing Addition - Accessibility testing

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.

Testing Strategies should be renamed to Testing Approaches

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.

Test Cases & Scenarios is incorrect

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

"Test Cases are clearly written and documented"

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).
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"

What does this mean?

For details :

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

Create better separation between sections

The README layout is a bit weird, with

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

not able to view pdf

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

Testing Types should be renamed to Testing Techniques

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"