Scribd
Upload
185 views10 pages

Quality Assurance (QA)

Uploaded by

gautamsingh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
185 views10 pages

Quality Assurance (QA)

Uploaded by

gautamsingh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 10

Quality Assurance (QA)

Content of the session

QA Introduction What is Quality Assurance (QA)

Testing Activities What are the activities be do while testing

Bug Reporting How to report a bug

Bug Life Cycle Tracking and Managing Defects

Smoke, Sanity, and Regression


Definitions Only
Testing

Risk-Based Testing What is risk based testing

Static and Dynamic Testing Difference only


QA Introduction

What is Quality
Assurance (QA)
Testing Activities

Some activities involved in software


testing include:
• Test planning
• Test analysis
• Test case development
• Test execution
• Test reporting
• Evaluating exit criteria
Bug Reporting
A bug report is a document that details a software issue or defect and
is used to inform developers and other stakeholders so that the
problem can be resolved. Bug reports are a vital part of the software
testing process, as they help to ensure that the final product meets
quality standards and functions as intended.

The bug reporting process is a series of steps that a team follows to


identify, document, and resolve a bug in software:

• Bug discovery
• Bug report creation
• Bug assignment
• Bug analysis
• Bug prioritization
• Bug resolution
• Bug verification
• Bug closure
Bug Life Cycle in Software Development

As we know during the development of any software product the development teams follow
the Software Development Life Cycle (SDLC) processes.
Smoke, Sanity, and Regression
Smoke testing
--
Testing
Checks the stability of a software build by testing critical functionalities, such as login
forms and loading assets. Smoke testing is usually done on initial builds, and is often
performed by both developers and testers.

Sanity testing
--
Ensures that code changes work as intended by testing more detailed functions of the
app. Sanity testing is usually performed on relatively stable builds by the QA team.

Regression testing
--
Ensures that every aspect of a software build works as intended after updates,
configuration changes, or code changes. Regression testing is usually performed by
the QA team, and is often automated.
Risk-Based
Testing
Risk-based testing (RBT) is a software testing method that identifies and prioritizes the most
critical areas of a product for testing. The goal of RBT is to ensure that testing efforts are
focused on the areas that are most likely to cause issues or problems.

RBT involves the following steps:

1. Identify risks
---Identify potential risks that could negatively impact the product's functionality,
performance, or usability. These risks could include defects, failures, or security breaches.

2. Analyze risks
---Evaluate the identified risks based on their likelihood of occurring and their potential
impact on the system.

3. Prioritize testing
---Focus testing efforts on the areas with the highest risk. Critical features and functionalities
are tested more thoroughly than lower-risk or less important features.
Static and Dynamic
Testing
Static Testing
Static Testing, also known as Verification testing or Non-execution
testing, is a type of Software Testing method that checks for defects in
software without executing the code of the software application.

Dynamic Testing
Dynamic Testing is a type of Software Testing that is performed to
analyze the dynamic behavior of the code. It includes the testing of
the software for the input values and output values that are analyzed.
Thanks!
Do you have any questions ?

You might also like