QA Processes, Tools

and metrics
▸ Group 1
OUTLINE

 QA Tools
 QA Process
 QA Metrics
 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 with respect to
functionality, design, reliability, durability, & price of
the product.
 What is Assurance?
 Assurance is nothing but a positive declaration on a product or
service, which gives confidence.
 It is certainty 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.
 What is quality
assurance?
▸ Quality Assurance (QA) is defined as an activity to ensure that an
organization is providing the best possible product or service to
customers.
▸ QA focuses on improving the processes to deliver Quality Products to
the customer.
▸ An organization has to ensure, that processes are efficient and effective
as per the quality standards defined for software products. Quality
Assurance is popularly known as QA Testing
Quality Assurance Tools

▸ WHAT IS QUALITY ASSURANCE TOOLS?

▹ Quality assurance tools facilitates quality
assurance control, quality assurance testing, risk
assessment, and other components of quality
that contribute to the control and validity of all a
company's products and services.
 What is quality
control?
▸ Quality control popularly abbreviated as QC. It is a Sortware
Engineering process used to ensure quality in a product or a
service. It does not deal with the processes used to create a
product; rather it examines the quality of the “end products”
and the final outcome.
 difference between quality
control and quality
assurance?
▸ Sometimes, QC is confused with the QA. Quality control is to
examine the product or service and check for the result. Quality
assurance is to examine the processes and make changes to the
processes which led to the end-product.
QC vs. QA
The Quality Assurance process can involve –

• Recognizing standards when any applied in software

development methods.
• To carry traditional processes, for example, quality reviews.
• Conduct in-process test data recording processes.
• Encouraging documentation procedure measures.

This extraordinary issue fills in as a platform for experts to

display hypothesis, results, understanding, and different
progressions in Software Quality Assurance process.
Process of Quality Assurance
 CHARASTERISTICS OF QUALITY ASSURANCE
PROCESS
1. Concentrate on the User Experience
Testing at all stages of the venture is critical. However, the most dominant point is the
user experience.
In case that the UX is terrible, it unavoidably implies the quality isn’t of standard.
Despite the fact that this will presumably result in variations in the earlier stage of
software development, the user experience should dependably be at the leading place.

2. Automation and Continuous Integration

Automation is essential since it offers quick review, empowering continuous integration
– an important part of the agile approach.
Automation is additionally solution to lessening costs and improving the productivity of
your QA staff; that is one of the principle reasons why QA engineers must teach
themselves and be apt to execute automation processes.
3.Test and Code Coverage
Numerous QA managers ramble about “test coverage,” that gives a decent broad image of the
quality of the product. But to accomplish genuine quality, test cases and code coverage
examination both ought to be held.
For instance, regardless of the fact that 100% test coverage is performed by you, you have to, in
any case, go for a minimum 90% function code coverage to guarantee the best outcomes.

4. The Shift-Left Approach

Software testing begins commonly once the coding stage is finished. In any case, for ideal quality in
an agile strategy, you have to drive the concentration and start checking as well as testing directly
from the origin of the venture. It guarantees bugs are identified sooner, that saves both money and
time.
Additionally, it ensures a positive association with developers in the group, quickens the delivery of
the application, and takes into consideration more noteworthy test coverage.

5. Smart Testing
Full and thorough testing can now and again lead to a challenge since numerous personals might
not have resources or time to experience each reasonable combination of cases.
But you ought to be smart in how and what to test. It implies, speaking with the engineer to discover
little experiments that will identify the best number of bugs.
6. Bug Prevention
QA managers are prepared to detect bugs, but an ingenious QA specialist will likewise consider how to avoid
them in any case.
Conventional QA begins testing at the UI level, yet an agile process begins with the functional and unit testing
and after that moves to the UI phase. This methodology keeps bugs from entering the top level of
development which can later on lead to more severe issues and likely postpone the delivery.
Furthermore, concentrate on major crucial bugs and errors at first as opposed to many small errors.

7. Portability
It is critical for software to adjust to various environments. For example, a framework should operate just as
efficiently on a web platform as it works on mobile.
The versatility, installability, replaceability, and conformance of the product should be recorded respectively.

8. Reliability
A system crash is not a unique situation. However, in quality testing, you require to check the system’s
capacity to resist component breakdown. The system ought to be ready to get back into complete control even
after a possible malfunction in the product.

9. Documentation
This process manages the administration and archiving of documents. Any variation in a record is done by
using the appropriate change control method. Approval of all kinds of documents is also done in this process.
 QA METRICS
• They simply help us to measure the quality and
make sure we meet our quality guidelines.
Measuring quality helps us to make the right
decisions at right times and identify actionable
trends.
• Metrics play an important role in tracking the
progress and quality.
There are different aspects of quality that can be measured
through the QA metrics.
• One is the product quality. We can have an overall idea of
where our products stands in terms of quality and what
immediate measures we can take to improve the quality of
a product.
• Another factor we can measure is the team efficiency. It
helps identify where the team’s time and budget are being
used ineffectively and optimize accordingly.
Metrics can be categorized as below.

• Process Metrics: These can be used to improve the process

efficiency of the Software Development Life Cycle, Testing
process, etc.
• Product Metrics: Product Metrics deal with the quality of
the software product
• Project Metrics: These can be used to measure the
efficiency of a project team or any testing tools being used
by the team members
Another way to categorize metrics is by what it conveys.

• Result Metrics: These metrics measure and gives output

based on the results of an activity/process which is
already completed.
• Predictive Metrics: These metrics are derived based on
other sources and they act as early warning signs of an
unfavorable result.
 Things we can cover using test metrics.

• To measure cost and time to test.

• Overall status of bugs.
• Count of fixed, reopened, closed, Deferred, bugs
measuring different statuses of bugs
• Hidden bugs testing team couldn’t find.
• Percentage and coverage of software testing
• Whether the delivery timelines are achievable