Convert Figma logo to code with AI

fityanos logoawesome-quality-assurance-roadmap

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

1,858
330
1,858
8

Top Related Projects

A curated list of awesome test automation frameworks, tools, libraries, and software for different programming languages. Sponsored by https://zapple.tech and https://automated-testing.info

A curated list of testing resources

A collection of public resources about how software companies test their software

Quick Overview

The "awesome-quality-assurance-roadmap" repository is a comprehensive guide for Quality Assurance (QA) professionals and aspiring testers. It provides a structured roadmap covering various aspects of software testing, including methodologies, tools, and best practices. The repository serves as a valuable resource for individuals looking to start or advance their careers in QA.

Pros

  • Offers a well-organized and detailed roadmap for QA professionals
  • Covers a wide range of topics, from basic concepts to advanced testing techniques
  • Includes links to external resources for further learning
  • Regularly updated with community contributions

Cons

  • May be overwhelming for complete beginners due to the extensive content
  • Some linked resources might become outdated over time
  • Lacks interactive elements or hands-on exercises
  • Primarily focuses on web and mobile testing, with less emphasis on other domains

Getting Started

To get started with the awesome-quality-assurance-roadmap:

  1. Visit the repository at https://github.com/fityanos/awesome-quality-assurance-roadmap
  2. Browse through the README.md file to get an overview of the roadmap
  3. Click on specific topics or sections to explore detailed information and resources
  4. Star the repository to keep track of updates and new additions
  5. Consider contributing to the project by submitting pull requests or suggesting improvements

Competitor Comparisons

A curated list of awesome test automation frameworks, tools, libraries, and software for different programming languages. Sponsored by https://zapple.tech and https://automated-testing.info

Pros of awesome-test-automation

  • More comprehensive coverage of test automation tools and frameworks across various programming languages
  • Includes sections for specific areas like mobile, game, and Windows GUI testing
  • Regularly updated with contributions from the community

Cons of awesome-test-automation

  • Less structured learning path for beginners in quality assurance
  • Lacks a clear roadmap for career progression in QA
  • Focuses primarily on tools rather than concepts and methodologies

Code comparison

While both repositories primarily consist of curated lists and don't contain significant code samples, here's a brief comparison of their README structures:

awesome-test-automation:

# Awesome Test Automation

A curated list of awesome test automation frameworks, tools, libraries, and software for different programming languages.

## Programming languages
...

awesome-quality-assurance-roadmap:

# Awesome Quality Assurance Roadmap

A curated list of awesome QA resources for anyone interested in learning about software testing and quality assurance.

## The Roadmap
...

The awesome-test-automation repository focuses on categorizing tools by programming language, while awesome-quality-assurance-roadmap provides a structured learning path for QA professionals.

A curated list of testing resources

Pros of awesome-testing

  • More comprehensive coverage of testing tools and resources across various domains
  • Better organization with clear categories and subcategories
  • Regularly updated with recent contributions

Cons of awesome-testing

  • Lacks a structured learning path or roadmap for beginners
  • Doesn't provide as much context or explanations for each resource
  • May be overwhelming for newcomers due to the sheer volume of information

Code comparison

While both repositories are primarily curated lists of resources, they don't contain significant code samples. However, here's a comparison of their README structures:

awesome-testing:

# Awesome Testing [![Awesome](https://cdn.rawgit.com/sindresorhus/awesome/d7305f38d29fed78fa85652e3a63e154dd8e8829/media/badge.svg)](https://github.com/sindresorhus/awesome)

- [Another Awesome](#another-awesome)
- [Blogs](#blogs)
- [Books](#books)

awesome-quality-assurance-roadmap:

# Awesome Quality Assurance Roadmap [![Awesome](https://cdn.rawgit.com/sindresorhus/awesome/d7305f38d29fed78fa85652e3a63e154dd8e8829/media/badge.svg)](https://github.com/sindresorhus/awesome)

## Contents

- [QA Roadmap](#qa-roadmap)
- [How to use this guide](#how-to-use-this-guide)

The awesome-quality-assurance-roadmap repository provides a more structured approach with a roadmap and guidance on how to use the resources, while awesome-testing offers a broader collection of testing-related links and tools.

A collection of public resources about how software companies test their software

Pros of howtheytest

  • Focuses on real-world testing practices from well-known companies
  • Provides insights into industry-specific testing strategies
  • Regularly updated with new company testing methodologies

Cons of howtheytest

  • Limited scope compared to the comprehensive QA roadmap
  • Lacks structured learning path for beginners
  • May not cover all aspects of quality assurance

Code comparison

While both repositories primarily consist of markdown files and don't contain significant code samples, here's a comparison of their repository structures:

howtheytest:

├── README.md
├── CONTRIBUTING.md
├── companies
│   ├── Company1.md
│   ├── Company2.md
│   └── ...

awesome-quality-assurance-roadmap:

├── README.md
├── CONTRIBUTING.md
├── images
│   └── ...
├── resources
│   └── ...

The howtheytest repository organizes content by company, while awesome-quality-assurance-roadmap follows a more traditional roadmap structure with resources and images.

Both repositories serve different purposes: howtheytest provides real-world examples of testing practices, while awesome-quality-assurance-roadmap offers a comprehensive learning path for QA professionals. The choice between them depends on whether you're looking for industry-specific insights or a structured learning approach to quality assurance.

Convert Figma logo designs to code with AI

Visual Copilot

Introducing Visual Copilot: A new AI model to turn Figma designs to high quality code using your components.

Try Visual Copilot

README

Awesome Quality Assurance Roadmap Awesome

Contents

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