mirror of
https://github.com/kamranahmedse/developer-roadmap.git
synced 2026-09-24 15:00:31 +08:00
chore: sync content to repo (#10178)
Co-authored-by: nilbuild <4921183+nilbuild@users.noreply.github.com>
This commit is contained in:
github-actions[bot]
co-authored by
nilbuild
nilbuild
parent
33df3b1757
commit
3d3d07c5a7
@@ -6,5 +6,4 @@ Visit the following resources to learn more:
|
||||
|
||||
- [@article@What is Accessibility Testing? (Examples)](https://www.guru99.com/accessibility-testing.html)
|
||||
- [@article@Accessibility Testing Tutorial (Step By Step Guide)](https://www.softwaretestinghelp.com/what-is-web-accessibility-testing/)
|
||||
- [@article@IBM Accessibility Toolkit](https://www.ibm.com/able/)
|
||||
- [@feed@Explore top posts about Accessibility](https://app.daily.dev/tags/accessibility?ref=roadmapsh)
|
||||
- [@article@IBM Accessibility Toolkit](https://www.ibm.com/able/)
|
||||
@@ -1,12 +1,10 @@
|
||||
# Agile Model
|
||||
|
||||
The agile model refers to a software development approach based on iterative development. Agile methods break tasks into smaller iterations or parts that do not directly involve long-term planning. The project scope and requirements are laid down at the beginning of the development process. Plans regarding the number of iterations, the duration, and the scope of each iteration are clearly defined in advance.
|
||||
|
||||
The Agile software development methodology is one of the simplest and most effective processes to turn a vision for a business need into software solutions.
|
||||
|
||||
The Agile model is an iterative, incremental approach to software development that delivers working software in short cycles called sprints or iterations. Testing is integrated throughout each iteration rather than as a separate phase. Agile teams collaborate closely between developers and QA, with continuous feedback and adaptation to change.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@Agile Methodology: What is Agile Methodology in Software Testing?](https://www.geeksforgeeks.org/software-testing/what-is-agile-methodology/)
|
||||
- [@article@Agile Methodology: What is Agile Model in Software Testing?](https://www.guru99.com/agile-scrum-extreme-testing.html)
|
||||
- [@article@Manifesto for Agile Software Development](https://agilemanifesto.org/)
|
||||
- [@feed@Explore top posts about Agile](https://app.daily.dev/tags/agile?ref=roadmapsh)
|
||||
- [@feed@Explore top posts about Agile](https://app.daily.dev/tags/agile?ref=roadmapsh)
|
||||
@@ -1,19 +1,6 @@
|
||||
# Artillery
|
||||
|
||||
Artillery is a modern, powerful & easy-to-use performance testing toolkit. Use it to ship scalable applications that stay performant & resilient under high load.
|
||||
|
||||
Artillery prioritizes developer productivity and happiness, and follows the "batteries-included" philosophy.
|
||||
|
||||
Features
|
||||
--------
|
||||
|
||||
* Emulate complex user behavior with scenarios
|
||||
* Load testing and smoke testing
|
||||
* Batteries included
|
||||
* Extensible & hackable
|
||||
* Integrations and add-ons
|
||||
* Designed for cross-team collaboration
|
||||
* Planet-scale testing
|
||||
|
||||
Artillery is an open-source load testing toolkit for APIs and microservices. Test scenarios are defined in YAML or JavaScript, and it supports HTTP, WebSocket, and Socket.io protocols. Artillery is designed to run in CI/CD pipelines and integrates with monitoring platforms for capturing and visualizing performance data.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
|
||||
@@ -7,5 +7,4 @@ Visit the following resources to learn more:
|
||||
- [@official@Atlassian](https://www.atlassian.com/)
|
||||
- [@official@What is Jira used for?](https://www.atlassian.com/software/jira/guides/use-cases/what-is-jira-used-for#glossary-of-items)
|
||||
- [@article@What is Jira?](https://www.simplilearn.com/tutorials/jira/what-is-jira-and-how-to-use-jira-testing-software)
|
||||
- [@article@JIRA Tutorial: A Complete Hands-On How-To-Use JIRA Guide](https://www.softwaretestinghelp.com/atlassian-jira-tutorial-1/)
|
||||
- [@feed@Explore top posts about Atlassian](https://app.daily.dev/tags/atlassian?ref=roadmapsh)
|
||||
- [@article@JIRA Tutorial: A Complete Hands-On How-To-Use JIRA Guide](https://www.softwaretestinghelp.com/atlassian-jira-tutorial-1/)
|
||||
@@ -1,8 +1,6 @@
|
||||
# Authentication authorization
|
||||
|
||||
`Authentication` is the process of verifying that an individual, entity or website is whom it claims to be. Authentication in the context of web applications is commonly performed by submitting a username or ID and one or more items of private information that only a given user should know.
|
||||
|
||||
`Authorization` may be defined as "the process of verifying that a requested action or service is approved for a specific entity" (NIST). `Authorization` is distinct from authentication which is the process of verifying an entity's identity. When designing and developing a software solution, it is important to keep these distinctions in mind. A user who has been authenticated (perhaps by providing a username and password) is often not authorized to access every resource and perform every action that is technically possible through a system.
|
||||
# Authentication / Authorization
|
||||
|
||||
Authentication testing verifies that the system correctly identifies users through login flows, session management, and token handling. Authorization testing verifies that authenticated users can only access the resources they are permitted to. Weak authentication or authorization is consistently among the most critical and exploited security vulnerabilities.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
|
||||
@@ -1,8 +1,6 @@
|
||||
# Bitbucket
|
||||
|
||||
Bitbucket is a Git based hosting and source code repository service that is Atlassian's alternative to other products like GitHub, GitLab etc.
|
||||
|
||||
Bitbucket offers hosting options via Bitbucket Cloud (Atlassian's servers), Bitbucket Server (customer's on-premise) or Bitbucket Data Centre (number of servers in customers on-premise or cloud environment)
|
||||
Bitbucket is a Git based hosting and source code repository service that is Atlassian's alternative to other products like GitHub, GitLab etc. Bitbucket offers hosting options via Bitbucket Cloud (Atlassian's servers), Bitbucket Server (customer's on-premise) or Bitbucket Data Centre (number of servers in customers on-premise or cloud environment)
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
|
||||
@@ -1,10 +1,6 @@
|
||||
# Chrome dev tools
|
||||
|
||||
These are a set of tools built into the browser to aid frontend developers diagnose and solve various issues in their applications — such as JavaScript and logical bugs, CSS styling issues or even just making quick temporary alterations to the DOM.
|
||||
|
||||
To enter the dev tools, right click and click **Inspect** (or press `ctrl+shift+c`/`cmd+opt+c`) to enter the Elements panel. Here you can debug CSS and HTML issues. If you want to see logged messages or interact with javascript, enter the **Console** tab from the tabs above (or press `ctrl+shift+j`/`cmd+opt+j` to enter it directly). Another very useful feature in the Chrome dev tools is the Lighthouse (for checking performance) — more on this later.
|
||||
|
||||
NOTE: This isn't a chrome-specific feature, and most browsers (Chromium based or otherwise) will have their own, largely-similar set of devtools.
|
||||
# Chrome DevTools
|
||||
|
||||
Chrome DevTools includes an accessibility panel, a color contrast checker, and Lighthouse accessibility audits for evaluating web page compliance. The accessibility tree view shows how assistive technologies interpret page elements. DevTools also simulates visual impairments like color blindness to help evaluate inclusive design.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
|
||||
@@ -1,8 +1,6 @@
|
||||
# CI / CD
|
||||
|
||||
Continuous Integration is a software development method where team members integrate their work at least once daily. An automated build checks every integration to detect errors in this method. In Continuous Integration, the software is built and tested immediately after a code commit. In a large project with many developers, commits are made many times during the day. With each commit, code is built and tested.
|
||||
|
||||
Continuous Delivery is a software engineering method in which a team develops software products in a short cycle. It ensures that software can be easily released at any time. The main aim of continuous delivery is to build, test, and release software with good speed and frequency. It helps reduce the cost, time, and risk of delivering changes by allowing for frequent updates in production.
|
||||
|
||||
Continuous Integration and Continuous Delivery (CI/CD) automates building, testing, and deploying code on every change. For QA, CI/CD pipelines run automated test suites on every commit or pull request, providing rapid feedback on regressions. Common CI/CD platforms used in QA include CircleCI, GitLab CI, Jenkins, Travis CI, Bamboo, Drone, TeamCity, and Azure DevOps.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# CSR vs SSR
|
||||
|
||||
CSR stands for Client Side Rendering and SSR stands for Server Side Rendering. CSR pages are computed in your machine and then shown by your browser while in the case of SSR, the server sends ready to show Html content directly. Primarily React, Vue, and Angular apps are examples of CSR (technically it is possible for them to be executed in SSR mode too) and almost all older tech stacks are SSR like PHP, ruby on rails, java, dot net, etc. From the user's standpoint, CSR apps take higher time to render but compensate by avoiding page reloads later (SPA) while SSR apps often have faster initial load time but do a full page reload often.
|
||||
|
||||
Client-Side Rendering (CSR) builds pages in the browser using JavaScript after load, while Server-Side Rendering (SSR) delivers fully rendered HTML from the server. The rendering approach affects when elements are available in the DOM, which directly impacts how and when automation tools can safely interact with the page.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
|
||||
@@ -6,5 +6,4 @@ Visit the following resources to learn more:
|
||||
|
||||
- [@article@Exploratory Testing](https://www.satisfice.com/exploratory-testing)
|
||||
- [@article@Exploratory Testing 3.0](https://www.satisfice.com/blog/archives/1509)
|
||||
- [@article@History of Definitions of Exploratory Testing](https://www.satisfice.com/blog/archives/1504)
|
||||
- [@feed@Explore top posts about Testing](https://app.daily.dev/tags/testing?ref=roadmapsh)
|
||||
- [@article@History of Definitions of Exploratory Testing](https://www.satisfice.com/blog/archives/1504)
|
||||
@@ -1,8 +1,6 @@
|
||||
# Gatling
|
||||
|
||||
Gatling is a highly capable load testing tool. It is designed for ease of use, maintainability and high performance. Out of the box, Gatling comes with excellent support of the HTTP protocol that makes it a tool of choice for load testing any HTTP server. As the core engine is actually protocol agnostic, it is perfectly possible to implement support for other protocols. For example, Gatling currently also ships JMS support.
|
||||
|
||||
Gatling’s architecture is asynchronous as long as the underlying protocol, such as HTTP, can be implemented in a non blocking way. This kind of architecture lets us implement virtual users as messages instead of dedicated threads, making them very resource cheap. Thus, running thousands of concurrent virtual users is not an issue.
|
||||
|
||||
Gatling is an open-source load testing framework written in Scala, designed for high-performance testing of HTTP-based services. Tests are written as code using a fluent DSL and can be version-controlled alongside application code. Gatling generates detailed HTML reports and is known for its ability to simulate large numbers of concurrent users efficiently.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
|
||||
@@ -5,6 +5,6 @@ Git is a free and open source distributed version control system designed to han
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@roadmap@Visit Dedicated Git & GitHub Roadmap](https://roadmap.sh/git-github)
|
||||
- [@course@Why use Git? (Interactive Lesson)](https://inter-git.com/lessons/introduction)
|
||||
- [@video@Git & GitHub Crash Course For Beginners](https://www.youtube.com/watch?v=SWYqp7iY_Tc)
|
||||
- [@video@Complete Git and GitHub Tutorial](https://www.youtube.com/watch?v=apGV9Kg7ics)
|
||||
- [@course@Why use Git? (Interactive Lesson)](https://inter-git.com/lessons/introduction)
|
||||
- [@video@Complete Git and GitHub Tutorial](https://www.youtube.com/watch?v=apGV9Kg7ics)
|
||||
@@ -1,6 +1,6 @@
|
||||
# Grafana
|
||||
|
||||
Grafana is the open-source platform for monitoring and observability. It allows you to query, visualize, alert on and understand your metrics no matter where they are stored.
|
||||
|
||||
Grafana is an open-source analytics and visualization platform for creating dashboards from metrics stored in data sources like Prometheus, InfluxDB, and Datadog. QA teams use Grafana to visualize load test results, track performance metrics over time, and build custom dashboards for monitoring test environment health.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
|
||||
@@ -1,12 +1,6 @@
|
||||
# Headless Testing
|
||||
|
||||
Headless testing is when end-to-end tests are performed without loading the browser's user interface. Since the browser operates as a typical browser would but does not make use of the user interface, it is considered highly suitable for automated testing.
|
||||
|
||||
A few example cases where one may use headless browser testing include:
|
||||
|
||||
* Automating HTML event responses, such as form submission, keyboard events, mouse-clicking, etc.
|
||||
* Web scraping
|
||||
* Generating screenshots of webpages
|
||||
|
||||
Headless testing runs browser-based tests without a visible graphical user interface. Headless browsers execute JavaScript and render pages in memory, making tests faster and suitable for CI/CD environments where a display server is not available. Tools for headless testing include Cypress, Playwright, Puppeteer, Zombie.js, Headless Chrome, Headless Firefox, and HtmlUnit.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
|
||||
@@ -1,11 +1,9 @@
|
||||
# HTML/CSS/JavaScript Basics
|
||||
|
||||
HTML stands for HyperText Markup Language. It is used on the front and gives structure to the webpage, which you can style using CSS and make interactive using JavaScript.
|
||||
|
||||
CSS or Cascading Style Sheets is the language used to style the front end of any website. CSS is a cornerstone technology of the World Wide Web, alongside HTML and JavaScript.
|
||||
|
||||
JavaScript allows you to add interactivity to your pages. You may have seen common examples on the websites: sliders, click interactions, popups, and so on.
|
||||
# HTML, CSS, JavaScript
|
||||
|
||||
HTML, CSS, and JavaScript are the three core web technologies that frontend test automation engineers must understand. HTML defines the structure of web pages, CSS controls styling and layout, and JavaScript powers interactivity. This knowledge enables testers to locate elements reliably, understand rendering behavior, and write effective automation scripts.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@feed@Explore top posts about CSS](https://app.daily.dev/tags/css?ref=roadmapsh)
|
||||
- [@roadmap@Visit the Dedicated HTML Roadmap](https://roadmap.sh/html)
|
||||
- [@roadmap@Visit the Dedicated CSS Roadmap](https://roadmap.sh/css)
|
||||
- [@roadmap@Visit the Dedicated JavaScript Roadmap](https://roadmap.sh/javascript)
|
||||
@@ -1,8 +1,6 @@
|
||||
# HtmlUnit
|
||||
|
||||
HtmlUnit is a "GUI-Less browser for Java programs". It models HTML documents and provides an API that allows you to invoke pages, fill out forms, click links, etc... just like you do in your "normal" browser. It has fairly good JavaScript support (which is constantly improving) and is able to work even with quite complex AJAX libraries, simulating Chrome, Firefox or Internet Explorer depending on the configuration used.
|
||||
|
||||
HtmlUnit is not a generic unit testing framework. It is specifically a way to simulate a browser for testing purposes and is intended to be used within another testing framework such as JUnit or TestNG.
|
||||
# HTML Unit
|
||||
|
||||
HtmlUnit is a headless, Java-based browser for testing web applications. It simulates a browser by processing HTML, JavaScript, and CSS without a graphical interface. HtmlUnit is commonly used in Java-based test suites as a lightweight headless browser option, particularly in projects using Selenium WebDriver with a Java stack.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
|
||||
@@ -1,8 +1,6 @@
|
||||
# k6
|
||||
|
||||
Grafana k6 is an open-source load testing tool that makes performance testing easy and productive for engineering teams. k6 is free, developer-centric, and extensible.
|
||||
|
||||
Using k6, you can test the reliability and performance of your systems and catch performance regressions and problems earlier. k6 will help you to build resilient and performant applications that scale.
|
||||
Grafana k6 is an open-source load testing tool that makes performance testing easy and productive for engineering teams. k6 is free, developer-centric, and extensible. Using k6, you can test the reliability and performance of your systems and catch performance regressions and problems earlier. k6 will help you to build resilient and performant applications that scale.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
|
||||
@@ -1,8 +1,6 @@
|
||||
# Kanban
|
||||
|
||||
Kanban is a very popular framework for development in the agile software development methodology. It provides a transparent way of visualizing the tasks and work capacity of a team. It mainly uses physical and digital boards to allow the team members to visualize the current state of the project they are working on.
|
||||
|
||||
A kanban board is an agile project management tool designed to help visualize work, limit work-in-progress, and maximize efficiency.
|
||||
|
||||
Kanban is an Agile workflow management method that visualizes work on a board with columns representing stages like To Do, In Progress, and Done. Work items flow through columns as they are completed, and work-in-progress limits prevent bottlenecks. QA teams use Kanban to manage testing tasks and make workflow impediments visible.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
|
||||
@@ -1,10 +1,6 @@
|
||||
# Karate framework
|
||||
|
||||
Karate is the only open-source tool to combine API test-automation, mocks, performance-testing and even UI automation into a single, unified framework. The BDD syntax popularized by Cucumber is language-neutral, and easy for even non-programmers. Assertions and HTML reports are built-in, and you can run tests in parallel for speed.
|
||||
|
||||
There's also a cross-platform stand-alone executable for teams not comfortable with Java. You don't have to compile code. Just write tests in a simple, readable syntax - carefully designed for HTTP, JSON, GraphQL and XML. And you can mix API and UI test-automation within the same test script.
|
||||
|
||||
A Java API also exists for those who prefer to programmatically integrate Karate's rich automation and data-assertion capabilities.
|
||||
# Karateframework
|
||||
|
||||
Karate is an open-source test automation framework that combines API testing, mocking, and performance testing using a plain-text Gherkin-like syntax. It does not require programming knowledge for basic test cases, making it accessible to non-developer testers. Karate integrates with CI/CD pipelines and supports parallel test execution out of the box.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
|
||||
@@ -1,7 +1,3 @@
|
||||
# QA Basics
|
||||
|
||||
The phrase "fit for use or purpose" sums up quality, which is incredibly difficult to define. It all comes down to fulfilling the requirements and expectations of the consumer in terms of the product's usefulness, design, dependability, durability, and price.
|
||||
|
||||
Assurance is nothing more than a confident statement made about a good or service. It is the assurance that a good outcome is guaranteed for a good or service. It offers a warranty that the product will perform faultlessly in accordance with expectations or needs.
|
||||
|
||||
Quality Assurance (QA) also known as QA testing is an activity to ensure that an organization provides the best product or service to the customers. QA testing of a software involves the testing of performance, adaptability, and functionality. Yet, software quality assurance extends beyond software quality; it also comprises the quality process used for developing, testing, and release of software products. QA relies on the software development cycle, which includes the management of software requirements, design, coding, testing, and release.
|
||||
# Learn the Fundamentals
|
||||
|
||||
The fundamentals of QA cover the core concepts, terminology, and practices every software tester needs to know. This includes what quality assurance is, common testing techniques and approaches, test management tools, and how QA integrates into software development lifecycles.
|
||||
@@ -1,18 +1,6 @@
|
||||
# Load and Performance Testing
|
||||
|
||||
Performance Testing is a subset of Performance Engineering. It is a process of evaluating a system’s behavior under various extreme conditions. The main intent of performance testing is to monitor and improve key performance indicators such as response time, throughput, memory, CPU utilization, and more.
|
||||
|
||||
There are three objectives (three S) of Performance testing to observe and evaluate: `Speed`, `Scalability` and `Stability`. Following are the commonly used performance testing types, but not limited to:
|
||||
|
||||
* Load Testing
|
||||
* Stress Testing
|
||||
* Spike Testing
|
||||
* Endurance Testing
|
||||
* Volume Testing
|
||||
* Scalability Testing
|
||||
* Capacity Testing
|
||||
|
||||
Load Testing is one type of performance testing. It helps to evaluate the application under tests' behaviors such as response time, throughput, pass/fail transactions, and more under the normal workload. e.g., cart checkout response time is 500 milliseconds under typical business hours.
|
||||
# Load & Performance Testing
|
||||
|
||||
Load and performance testing evaluates how a system behaves under expected and peak traffic conditions. Tools like K6, JMeter, Gatling, Locust, and Artillery simulate concurrent users and measure response times, throughput, and error rates. Results inform capacity planning, infrastructure decisions, and optimization priorities.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
|
||||
@@ -1,12 +1,6 @@
|
||||
# Locust
|
||||
|
||||
Locust is an easy-to-use, scriptable and scalable performance testing tool. You define the behavior of your users in regular Python code instead of being stuck in a UI or restrictive domain-specific language. This makes Locust infinitely expandable and very developer friendly. Given below are some of the features of Locust.
|
||||
|
||||
* Write test scenarios in plain old Python
|
||||
* Distributed and scalable - supports hundreds of thousands of concurrent users
|
||||
* Web-based UI
|
||||
* Can test any system
|
||||
* Hackable
|
||||
|
||||
Locust is an open-source Python-based load testing tool where user behavior is defined in plain Python code. It simulates large numbers of concurrent users using lightweight coroutines rather than threads, making it efficient for high-load scenarios. Locust provides a real-time web UI for monitoring results and supports distributed load generation.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
|
||||
@@ -4,5 +4,4 @@ Test Management is a process of managing the testing activities in order to ensu
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@Test Management Process in Software Testing](https://www.guru99.com/test-management-phases-a-complete-guide-for-testing-project.html)
|
||||
- [@feed@Explore top posts about Testing](https://app.daily.dev/tags/testing?ref=roadmapsh)
|
||||
- [@article@Test Management Process in Software Testing](https://www.guru99.com/test-management-phases-a-complete-guide-for-testing-project.html)
|
||||
@@ -1,8 +1,6 @@
|
||||
# OWASP 10
|
||||
|
||||
The Open Web Application Security Project, or OWASP, is an international non-profit organization dedicated to web application security.
|
||||
|
||||
The OWASP Top 10 is a regularly-updated report outlining security concerns for web application security, focusing on the 10 most critical risks. The report is put together by a team of security experts from all over the world. OWASP refers to the Top 10 as an ‘awareness document’ and they recommend that all companies incorporate the report into their processes in order to minimize and/or mitigate security risks.
|
||||
|
||||
The OWASP Top 10 is a list of the most critical web application security risks, published by the Open Web Application Security Project. It covers vulnerabilities like injection attacks, broken authentication, insecure deserialization, and security misconfiguration. Security testing commonly uses the OWASP Top 10 as a checklist to verify that an application's most critical risks are addressed.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# PagerDuty
|
||||
|
||||
Through its SaaS-based platform, PagerDuty empowers developers, DevOps, IT operations and business leaders to prevent and resolve business-impacting incidents for exceptional customer experience. When revenue and brand reputation depends on customer satisfaction, PagerDuty arms organizations with the insight to proactively manage events that may impact customers across their IT environment. With hundreds of native integrations, on-call scheduling and escalations, machine learning, business-wide response orchestration, analytics, and much more, PagerDuty gets the right data in the hands of the right people in real time, every time.
|
||||
# Pager Duty
|
||||
|
||||
PagerDuty is an incident management and alerting platform that routes alerts from monitoring tools to on-call teams. In QA contexts, it notifies engineers of critical failures detected in staging or production environments. PagerDuty integrates with tools like Datadog, New Relic, and Grafana to trigger incidents based on defined threshold conditions.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
|
||||
@@ -1,21 +1,6 @@
|
||||
# Performance Testing
|
||||
|
||||
Performance Testing is a subset of Performance Engineering. It is a process of evaluating a system’s behavior under various extreme conditions. The main intent of performance testing is monitoring and improving key performance indicators such as response time, throughput, memory, CPU utilization, and more.
|
||||
|
||||
There are three objectives (three S) of Performance testing to observe and evaluate: `Speed`, `Scalability`, and `Stability`.
|
||||
|
||||
Types of Performance Testing
|
||||
----------------------------
|
||||
|
||||
Following are the commonly used performance testing types, but not limited to:
|
||||
|
||||
* Load Testing
|
||||
* Stress Testing
|
||||
* Spike Testing
|
||||
* Endurance Testing
|
||||
* Volume Testing
|
||||
* Scalability Testing
|
||||
* Capacity Testing
|
||||
|
||||
Performance testing measures the speed, scalability, and stability of a system under various conditions. It encompasses load testing, stress testing, endurance testing, and spike testing. The goal is to identify performance bottlenecks and verify that response times and throughput meet defined service level objectives.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
|
||||
@@ -1,12 +1,9 @@
|
||||
# Project Management
|
||||
|
||||
A project is a temporary endeavor to create a unique product, service, or result. A project is temporary because it has a defined beginning and end time, and it is unique because it has a particular set of operations designed to accomplish a goal.
|
||||
|
||||
Project Management is a discipline of planning, organizing, motivating, and controlling the resources to achieve specific project goals. The main objective of project management is to achieve project goals and targets while keeping in mind the project scope, time, quality, and cost. It facilitates the project workflow with team collaboration on a single project.
|
||||
|
||||
Project management tools in QA help teams plan, track, and coordinate testing activities within the broader software project. They manage requirements, bugs, sprints, and progress reporting. Platforms commonly used in QA teams include Atlassian products, Assembla, YouTrack, and Trello.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@What are the Main Objectives of Project Management?](https://www.guru99.com/introduction-project-management-pmp-certification.html)
|
||||
- [@article@Project Management in Software Testing](https://huddle.eurostarsoftwaretesting.com/project-management-in-software-testing/)
|
||||
- [@article@Project Management Life Cycle Phases: What are the stages?](https://www.guru99.com/initiation-phase-project-management-life-cycle.html)
|
||||
- [@feed@Explore top posts about Project Management](https://app.daily.dev/tags/project-management?ref=roadmapsh)
|
||||
- [@article@Project Management Life Cycle Phases: What are the stages?](https://www.guru99.com/initiation-phase-project-management-life-cycle.html)
|
||||
@@ -1,16 +1,6 @@
|
||||
# QA Mindset
|
||||
|
||||
As a Quality Assurance Engineer, your primary responsibility is to nurture a proactive, quality-centric, and holistic mindset throughout the organization. This involves promoting the understanding that quality is not solely the responsibility of the QA chapter, or achieved through manual testing alone, but rather a shared commitment that requires collaboration from all team members. Quality should be seamlessly integrated into every phase of the software development lifecycle, from requirements gathering to deployment and maintenance. Your role is to take initiative, provide guidance, and lead the company in adopting best practices and methodologies that prioritize quality. By educating and empowering your colleagues, you can foster a culture where everyone understands the significance of delivering high-quality products and is equipped with the knowledge and tools to contribute effectively to this goal.
|
||||
|
||||
A few important points:
|
||||
|
||||
* Foster a quality-centric mindset and promote shared responsibility for quality across the organization
|
||||
* Integrate quality processes into every phase of the software development lifecycle and encourage collaboration among team members
|
||||
* Take initiative, provide guidance, and lead the company in adopting best practices for ensuring high-quality products
|
||||
* Implement and maintain robust automation frameworks to enhance testing efficiency, coverage, and reliability
|
||||
* Continuously improve quality processes, stay updated with industry trends, and advocate for the importance of quality in driving customer satisfaction and business success
|
||||
* Think outside the box, ask questions, explore edge cases, and don't be afraid to misuse the product to uncover potential issues
|
||||
* Foster open communication, transparency, and a proactive approach to identifying and mitigating quality risks early in the development process
|
||||
|
||||
The QA mindset is the set of critical thinking habits and attitudes that make an effective tester. It includes questioning assumptions, thinking about how systems can fail, paying attention to detail, and advocating for the user's perspective. A strong QA mindset balances thoroughness with pragmatism, focusing testing effort where it creates the most value.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# QA reporting
|
||||
|
||||
The International Software Testing Qualifications Board (ISTQB) glossary defines a QA report as: _Documentation summarizing test activities and results_. By documenting the testing that was conducted and the results that were achieved, QA reports provide valuable insight into the health of the code base and critical metrics. As such, they should be generated on a regular basis to ensure the quality standards are being met. So basically, test reports should document all of the test cases that were performed during software testing, as well as the results of those tests. They should also deliver relevant information about the product and highlight any areas where improvements can be made.
|
||||
# Reporting
|
||||
|
||||
Test reporting collects and presents the results of test execution in a readable format for QA teams, developers, and stakeholders. Good reports show which tests passed or failed, trends over time, defect density, and coverage levels. Tools like TestRail, Allure, and JUnit report formats integrate with CI/CD systems to publish results automatically after each build.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
|
||||
@@ -1,21 +1,3 @@
|
||||
# Responsive vs adaptive
|
||||
|
||||
There are two approaches to ensuring a website is optimized for mobile, tablet, laptop and PC screens: responsive design and adaptive design. While both are intended to solve the same problem, they use different strategies.
|
||||
|
||||
What is responsive design?
|
||||
==========================
|
||||
|
||||
A website created with responsive design serves up the same site to every device, but that site is fluid and will change its layout and appearance based on the size and orientation of the device.
|
||||
|
||||
Developers use CSS to ensure each page of the site can reformat based on the size of the user's viewport and only need to create one codebase for the site. They use something called breakpoints to tell the site when to adjust to accommodate different screen sizes.
|
||||
|
||||
The majority of new sites now use responsive, which has been made easier for less experienced designers and developers, thanks to the availability of themes accessible through CMS systems such as WordPress, Joomla, and Drupal.
|
||||
|
||||
Responsive design does not offer as much control as adaptive, but takes much less work to both build and maintain. Responsive layouts are also fluid, and whilst adaptive can and do use percentages to give a more fluid feel when scaling, these can again cause a jump when a window is resized.
|
||||
|
||||
What is adaptive design?
|
||||
========================
|
||||
|
||||
In adaptive design, a different website layout is created for each device's screen. As it loads, the site recognizes the size of the screen and serves up the layout that was made for that viewport. In fact, you can create a different user experience for each of six common screen sizes from very small to very large: 320px, 480px, 760px, 960px, 1200px and 1600px.
|
||||
|
||||
Adaptive is useful for retrofitting an existing site in order to make it more suitable for mobile phones. This allows you to take control of the design and web development for specific, multiple viewports. The number of viewports that you choose to design for is entirely up to you, your company, and your overall budget. It does, however, afford you a certain amount of control (for example over content and layout) that you will not necessarily have using responsive design.
|
||||
# Responsive vs Adaptive
|
||||
|
||||
Responsive design uses fluid layouts that scale to any screen size, while adaptive design serves fixed layouts targeted to specific breakpoints. Testing responsive and adaptive applications requires verifying layouts across different viewport sizes and devices. Automated tests can simulate various resolutions, and visual regression tools detect unexpected layout changes.
|
||||
@@ -1,8 +1,6 @@
|
||||
# Robot framework
|
||||
|
||||
Robot Framework is a Python-based, extensible keyword-driven automation framework for acceptance testing, acceptance test driven development (ATDD), behavior driven development (BDD) and robotic process automation (RPA).
|
||||
|
||||
Robot Framework is open and extensible. Robot Framework can be integrated with virtually any other tool to create powerful and flexible automation solutions.
|
||||
# Robot
|
||||
|
||||
Robot Framework is an open-source, keyword-driven test automation framework with a human-readable tabular test syntax. It is extensible through Python or Java libraries and supports web, API, desktop, and mobile testing. Robot Framework is widely used for acceptance testing and integrates with SeleniumLibrary and the Browser Library.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
|
||||
@@ -1,8 +1,6 @@
|
||||
# Run scope
|
||||
|
||||
A Simple Tool for Monitoring Complex APIs. Verify that the structure and content of your API calls meets your expectations. Powerful and flexible assertions give you total control over defining a successful API call.
|
||||
|
||||
Create simple monitors with dynamic data for even the most complex use cases. More than simple string matching, build API validations without any code and use them across local dev, staging and production environments.
|
||||
# RunScope
|
||||
|
||||
Runscope (now part of Blazemeter) is an API monitoring and testing tool that checks API endpoints for correctness, performance, and availability on a scheduled or triggered basis. It is used for continuous API monitoring in production and staging environments. Runscope alerts teams when API responses deviate from expected behavior or exceed response time thresholds.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
|
||||
@@ -5,5 +5,4 @@ Security Testing is a type of Software Testing that uncovers vulnerabilities, th
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@What is Security Testing? Types with Example](https://www.guru99.com/what-is-security-testing.html)
|
||||
- [@article@Security Testing: Types, Tools, and Best Practices](https://brightsec.com/blog/security-testing/)
|
||||
- [@feed@Explore top posts about Security](https://app.daily.dev/tags/security?ref=roadmapsh)
|
||||
- [@article@Security Testing: Types, Tools, and Best Practices](https://brightsec.com/blog/security-testing/)
|
||||
@@ -1,8 +1,6 @@
|
||||
# Security Testing
|
||||
|
||||
Security testing is a process intended to reveal flaws in the security mechanisms of an information system that protect data and maintain functionality as intended. Due to the logical limitations of security testing, passing the security testing process is not an indication that no flaws exist or that the system adequately satisfies the security requirements.
|
||||
|
||||
Typical security requirements may include specific elements of confidentiality, integrity, authentication, availability, authorization and non-repudiation. Actual security requirements tested depend on the security requirements implemented by the system. Security testing as a term has a number of different meanings and can be completed in a number of different ways. As such, a Security Taxonomy helps us to understand these different approaches and meanings by providing a base level to work from.
|
||||
|
||||
Security testing identifies vulnerabilities and weaknesses in an application that could be exploited by attackers. It covers authentication and authorization controls, secrets management, vulnerability scanning, adherence to OWASP guidelines, and analysis of common attack vectors. Security testing is increasingly integrated into CI/CD pipelines as part of DevSecOps practices.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
|
||||
@@ -1,8 +1,6 @@
|
||||
# Selenium IDE
|
||||
|
||||
Selenium IDE is an open source web automation testing tool from the Selenium Suite used primarily for QA purposes. It functions as a Firefox extension and does not require any programming knowledge and test cases can be created simply by interacting with the browser.
|
||||
|
||||
Selenium itself is an open-source, automated testing tool used to test web applications across various browsers. It's primarily built in Java and supports several browsers and programming languages. Selenium IDE was developed to speed up the creation of automation scripts. It’s a rapid prototyping tool and can be used by engineers with no programming knowledge whatsoever. Because of its simplicity, Selenium IDE is best used as a prototyping tool and not a complete solution for developing and maintaining complex test suites.
|
||||
|
||||
Selenium IDE is a browser extension for Chrome and Firefox that records user interactions and generates Selenium-compatible test scripts. It is designed for rapid test creation without programming, making it accessible to manual testers. Recorded scripts can be exported in multiple languages and integrated into existing Selenium-based automation suites.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
|
||||
@@ -1,8 +1,6 @@
|
||||
# Stress Testing
|
||||
|
||||
`Stress Testing` is a type of `Performance Testing`. The objective of stress testing is to identify the breaking point of application under test under extreme normal load.
|
||||
|
||||
e.g. Injecting high volume of requests per second to an API might cause the disruption to its service, or throws HTTP 503 Service Unavailable or cause other consequences.
|
||||
|
||||
Stress testing evaluates a system's behavior when pushed beyond its normal operational capacity. It determines the system's breaking point by gradually increasing load until failure. Stress tests reveal how the system fails, whether it fails gracefully, and how it recovers after load is reduced.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
|
||||
@@ -1,21 +1,6 @@
|
||||
# SWAs, PWAs and JAMstack
|
||||
|
||||
SWAs
|
||||
----
|
||||
|
||||
A Static Web Application is any web application that can be delivered directly to an end user's browser without any server-side alteration of the HTML, CSS, or JavaScript content. While this can encompass very flat, unchanging sites like a corporate web site, static web applications generally refer to rich sites that utilize technologies in the browser instead of on the server to deliver dynamic content.
|
||||
|
||||
PWAs
|
||||
----
|
||||
|
||||
At their heart, Progressive Web Apps are just web applications. Using progressive enhancement, new capabilities are enabled in modern browsers. Using service workers and a web app manifest, your web application becomes reliable and installable. If the new capabilities aren't available, users still get the core experience.
|
||||
|
||||
Progressive Web Apps provide you with a unique opportunity to deliver a web experience your users will love. Using the latest web features to bring enhanced capabilities and reliability, Progressive Web Apps allow what you build to be installed by anyone, anywhere, on any device with a single codebase.
|
||||
|
||||
Jamstack
|
||||
--------
|
||||
|
||||
Jamstack is an architectural approach that decouples the web experience layer from data and business logic, improving flexibility, scalability, performance, and maintainability. Jamstack removes the need for business logic to dictate the web experience. It enables a composable architecture for the web where custom logic and 3rd party services are consumed through APIs.
|
||||
# SWAs, PWAs, JAMStack
|
||||
|
||||
Single Web Apps (SWAs), Progressive Web Apps (PWAs), and JAMStack are modern web application architectures with distinct rendering and caching behaviors. PWAs add offline support and installability, while JAMStack pre-renders content at build time for fast delivery. Testing these architectures requires understanding service worker interactions, offline behavior, and incremental static regeneration.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
|
||||
@@ -1,8 +1,6 @@
|
||||
# Test Cases and Scenarios
|
||||
|
||||
A Test Case is a set of actions executed to verify a particular feature or functionality of your software application. A Test Case contains test steps, test data, precondition, and postcondition developed for a specific test scenario to verify any requirement. The test case includes specific variables or conditions, using which a testing engineer can compare expected and actual results to determine whether a software product is functioning as per the requirements of the customer.
|
||||
|
||||
A Test Scenario is defined as any functionality that can be tested. It is a collective set of test cases which helps the testing team to determine the positive and negative characteristics of the project.
|
||||
|
||||
Test cases are documented descriptions of conditions, inputs, and expected results used to verify a specific aspect of a system. Test scenarios describe the higher-level situation being tested, and one scenario typically encompasses multiple test cases. Well-written test cases provide repeatable, clear documentation of what is being tested and what constitutes pass or fail.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
|
||||
@@ -1,17 +1,7 @@
|
||||
# Testing Approaches
|
||||
|
||||
Test approach has two techniques:
|
||||
|
||||
* Proactive - An approach in which the test design process is initiated as early as possible in order to find and fix the defects before the build is created.
|
||||
* Reactive - An approach in which the testing is not started until after design and coding are completed.
|
||||
|
||||
Three approaches are commonly used to implement functional testing:
|
||||
|
||||
* Black Box Testing
|
||||
* White Box Testing
|
||||
* Gray Box Testing
|
||||
|
||||
Testing approaches describe the general perspective from which tests are designed and executed. The three main categories are white box testing, which tests internal code paths; black box testing, which tests behavior without knowledge of internals; and gray box testing, which combines elements of both.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@Functional Testing Approaches and Agile Considerations](https://www.qualitylogic.com/knowledge-center/functional-testing-approaches-agile-considerations/)
|
||||
- [@feed@Explore top posts about Testing](https://app.daily.dev/tags/testing?ref=roadmapsh)
|
||||
- [@article@Functional Testing Approaches and Agile Considerations](https://www.qualitylogic.com/knowledge-center/functional-testing-approaches-agile-considerations/)
|
||||
@@ -1,3 +1,3 @@
|
||||
# Testing Methodologies
|
||||
|
||||
Testing methodologies are structured approaches to software testing, each with its own philosophy and techniques. Test-Driven Development (TDD) involves writing tests before writing the code, ensuring the code meets specific requirements. Acceptance Test-Driven Development (ATDD) focuses on defining acceptance criteria collaboratively with stakeholders, driving development from a business perspective. Behavior-Driven Development (BDD) uses plain language descriptions of system behavior to create tests, promoting better communication between developers, testers, and business stakeholders. Root Cause Analysis (RCA) is a systematic process for identifying the underlying causes of problems or defects, aiming to prevent recurrence rather than just addressing the symptoms.
|
||||
|
||||
Testing methodologies define structured approaches for integrating testing into the development process. Common methodologies include Test-Driven Development (TDD), Acceptance Test-Driven Development (ATDD), Behavior-Driven Development (BDD), and Root Cause Analysis (RCA). Each shapes when tests are written, by whom, and how they communicate intent.
|
||||
@@ -1,10 +1,6 @@
|
||||
# Trello
|
||||
|
||||
Trello is a popular, simple, and easy-to-use collaboration tool that enables you to organize projects and everything related to them into boards. With Trello, you can find all kinds of information, such as:
|
||||
|
||||
* What’s being worked on?
|
||||
* Who’s working on what?
|
||||
* What progress the project is making
|
||||
|
||||
Trello is a visual project management tool based on Kanban-style boards with cards and lists. Teams use it to track tasks, manage workflows, and coordinate work across members. In QA contexts, Trello is commonly used for lightweight test planning and defect tracking in smaller teams or projects.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
|
||||
@@ -1,8 +1,6 @@
|
||||
# Verification and Validation
|
||||
|
||||
Verification in Software Testing is a process of checking documents, design, code, and program in order to check if the software has been built according to the requirements or not. The main goal of verification process is to ensure quality of software application, design, architecture etc. The verification process involves activities like reviews, walk-throughs and inspection.
|
||||
|
||||
Validation in Software Engineering is a dynamic mechanism of testing and validating if the software product actually meets the exact needs of the customer or not. The process helps to ensure that the software fulfills the desired use in an appropriate environment. The validation process involves activities like unit testing, integration testing, system testing and user acceptance testing.
|
||||
|
||||
Verification checks that the software meets its specified design and requirements, asking "Are we building the product right?" Validation checks that the software meets the actual needs of the user, asking "Are we building the right product?" Both activities are performed at different stages of the development process and together ensure both correctness and fitness for purpose.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
|
||||
@@ -5,6 +5,6 @@ Version control/source control systems allow developers to track and control cha
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@roadmap@Visit Dedicated Git & GitHub Roadmap](https://roadmap.sh/git-github)
|
||||
- [@course@Why version control? (Interactive Lesson)](https://inter-git.com/lessons/introduction)
|
||||
- [@article@What is Version Control?](https://www.atlassian.com/git/tutorials/what-is-version-control)
|
||||
- [@video@Version Control System (VCS)](https://www.youtube.com/watch?v=SVkuliabq4g)
|
||||
- [@course@Why version control? (Interactive Lesson)](https://inter-git.com/lessons/introduction)
|
||||
- [@video@Version Control System (VCS)](https://www.youtube.com/watch?v=SVkuliabq4g)
|
||||
@@ -1,10 +1,6 @@
|
||||
# Vulnerability Scanning
|
||||
|
||||
Vulnerability scanning identifies hosts and host attributes (e.g., operating systems, applications, open ports), but it also attempts to identify vulnerabilities rather than relying on human interpretation of the scanning results. Many vulnerability scanners are equipped to accept results from network discovery and network port and service identification, which reduces the amount of work needed for vulnerability scanning.
|
||||
|
||||
Also, some scanners can perform their own network discovery and network port and service identification. Vulnerability scanning can help identify outdated software versions, missing patches, and misconfigurations, and validate compliance with or deviations from an organization’s security policy.
|
||||
|
||||
This is done by identifying the operating systems and major software applications running on the hosts and matching them with information on known vulnerabilities stored in the scanners’ vulnerability databases.
|
||||
|
||||
Vulnerability scanning uses automated tools to detect known security weaknesses in applications, dependencies, and infrastructure. Scanners check against databases of known vulnerabilities like the CVE list and flag outdated libraries, insecure configurations, and exposed endpoints. Regular automated scanning is a baseline practice in DevSecOps workflows.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
|
||||
@@ -1,10 +1,6 @@
|
||||
# Webdriver.io
|
||||
|
||||
WebdriverIO is a progressive automation framework built to automate modern web and mobile applications. It simplifies the interaction with your app and provides a set of plugins that help you create a scalable, robust and stable test suite.
|
||||
|
||||
WebdriverIO leverages the power of the WebDriver protocol that is developed and supported by all browser vendors and guarantees a true cross-browser testing experience. While other automation tools require you to download modified browser that aren't used by actual users or emulate user behavior by injecting JavaScript, WebdriverIO relies on a common agreed standard for automation that is properly tested and ensures compatibility for decades to come.
|
||||
|
||||
During the development of this automation standard the web has changed a lot and many of the requirements that developers have today to test their web application can not be fulfilled using WebDriver anymore. While some of the core contributors of this project help support the next generation of the WebDriver protocol, WebdriverIO provides an alternative automation solution based on the Chrome DevTools protocol. This allows the user to seamlessly switch between conventional commands based on WebDriver and powerful browser interactions through Puppeteer.
|
||||
|
||||
WebdriverIO is a Node.js-based test automation framework for web and mobile applications built on the WebDriver protocol. It provides an async API for browser automation and integrates with popular test frameworks like Mocha, Jasmine, and Cucumber. WebdriverIO supports Selenium, Chrome DevTools Protocol, and Appium as underlying drivers.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
|
||||
@@ -1,8 +1,6 @@
|
||||
# WebPageTest
|
||||
|
||||
WebPageTest is a web performance tool providing deep diagnostic information about how a page performs under a variety of conditions.
|
||||
|
||||
Each test can be run from different locations around the world, on real browsers, over any number of customizable network conditions.
|
||||
WebPageTest is a web performance tool providing deep diagnostic information about how a page performs under a variety of conditions. Each test can be run from different locations around the world, on real browsers, over any number of customizable network conditions.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
|
||||
@@ -1,19 +1,8 @@
|
||||
# What is Quality
|
||||
|
||||
Quality is extremely hard to define, and it is simply stated: “Fit for use or purpose.” It is all about meeting the needs and expectations of customers concerning the functionality, design, reliability, durability, & price of the product.
|
||||
|
||||
What is Assurance
|
||||
-----------------
|
||||
|
||||
Assurance is nothing but a positive declaration of a product or service, which gives confidence. It is certain of a product or a service which it will work well. It provides a guarantee that the product will work without any problems as per the expectations or requirements.
|
||||
|
||||
Quality Assurance in Software Testing
|
||||
-------------------------------------
|
||||
|
||||
Quality Assurance in Software Testing is defined as a procedure to ensure the quality of software products or services provided to the customers by an organization. Quality assurance focuses on improving the software development process and making it efficient and effective per the quality standards defined for software products. Quality Assurance is popularly known as QA Testing.
|
||||
# What is Quality Assurance?
|
||||
|
||||
Quality Assurance (QA) is a systematic process for ensuring that software products meet defined quality standards before delivery. It encompasses planning, executing, and evaluating tests to identify defects, verify requirements, and improve development processes. QA is process-oriented and aims to prevent defects throughout the development cycle, not just detect them at the end.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@What is Quality Assurance(QA)? Process, Methods, Examples](https://www.guru99.com/all-about-quality-assurance.html)
|
||||
- [@article@What Do Software Testers Do?](https://www.ministryoftesting.com/articles/what-do-software-testers-do)
|
||||
- [@feed@Explore top posts about QA](https://app.daily.dev/tags/qa?ref=roadmapsh)
|
||||
- [@article@What Do Software Testers Do?](https://www.ministryoftesting.com/articles/what-do-software-testers-do)
|
||||
@@ -1,10 +1,6 @@
|
||||
# Zephyr
|
||||
|
||||
Zephyr is a testing solution that improves the quality of your software by managing and monitoring end-to-end testing. It is very effective for managing manual testing. Its key capabilities include:
|
||||
|
||||
* Test-case creation
|
||||
* Organization of tests by product releases and components
|
||||
* Assignment of tests to the Quality Assurance team
|
||||
|
||||
Zephyr is a test management solution available as a Jira plugin (Zephyr Scale, Zephyr Squad) and as a standalone product. It allows teams to create test cases, organize them into cycles, execute tests, and view reports without leaving the Jira interface. Zephyr is widely used in teams that rely on Jira as their primary project tracking tool.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user