Q.What is SQA metrics? Discuss a case
Implement Cross Browser Testing -Cross browser
where this metric can be applied to assure the
quality of the product
1. Software quality metrics are a subset of software
metrics that focus on the quality aspects of the
product, process, and project. These are more closely
associated with process and product metrics than with
project metrics.
2. Software quality metrics can be further divided into
three categories – A)Product quality metrics B)In-
process quality metrics C)Maintenance quality
metrics 3.Product Quality Metrics-1.Mean Time to
Failure 2.Defect Density 3.Customer Problems
4.Customer Satisfaction
4.In-process Quality Metrics In-process quality
metrics deals with the tracking of defect arrival
during formal machine testing for some
organizations. This metric includes….,1.Defect
density during machine testing 2.Defect arrival
pattern during machine testing
3.Phase-based defect removal pattern 4.Defect removal
effectiveness
5.Maintenance Quality Metrics-Although much cannot
be done to alter the quality of the product during this
phase, following are the fixes that can be carried out to
eliminate the defects as soon as possible with excellent
fix quality.
1.Fix backlog and backlog management index 2.Fix
response time and fix responsiveness 3.Percent
delinquent fixes 4.Fix quality
6.Google reliability testing: code coverage as a
quality metric-1.Google has engrained testing into
the heart of the development process so that every
team is responsible for the quality of their products,
and testers are only an external source used for
creating automation….,2.Additionally, there is a
significant emphasis for teams to commit smaller bite-
size commits that can be easily rolled back if failures
do arise….,3. One vital software quality metric widely
used at Google is code coverage. Code coverage is the
percentage of code that is covered by automated
tests. At Google, over 90 percent of the projects are
covered with automated testing tools
Q. State and Explain formal approaches to
achieve software quality.
1. Software Quality Assurance (SQA) is simply a way to
assure quality in the software. It is the set of activities
which ensure processes, procedures as well as
standards are suitable for the project and
implemented correctly.
2. Test Early- Testing is important when learning how
to improve software quality and shouldn’t be
neglected. Testing aims to catch defects early during
the design phase so they don’t snowball and grow
into bigger issues later. Software development teams
resort to manual testing for many problems, but
companies leverage automated testing strategies for
non-UI tasks.
3.
testing checks if the software runs seamlessly across
different web browsers, screen sizes, and mobile
apps. With multiple devices and models coming out in
the market, cross browser testing is becoming integral
for every developer
4. Use Quality Controls from the Beginning-Quality
management and control is an ongoing process, so
testers must cooperate with developers and work
together. A structured approach effectively improves
test processes and cuts maintenance costs with native
testing tools.
5. Have Clear Communication-Clear communication
with all team members is integral to the software
quality improvement process. Having consistent KPIs
(Key Performance Indicators) throughout the project
and conveying accurate test reports helps in
communicating.
6. . Create a Risk Registry-Risk management is critical
to software quality improvement, and project
managers know they must monitor risks throughout
the development lifecycle7. Document Your Project
Requirements-Good documentation defines the
scope of the project, milestones, deliverables, and
technical specifications, thus ensuring you meet
deadlines and stay on track. The documentation also
defines customers’ needs and lists functional and non-
functional requirements
7. Produce Bug Reports-A good bug report can make
software testing and improvement highly effective. It
includes all possible scenarios, and use-cases and
describes behave
8. ours exhibited while testing new features. You can
add screenshots of failure exceptions in the report,
list all possible solutions, and a bug summary.
Q. 7. Explain ISO 9000 Quality standard parameters
1.ISO 9000 is defined as a set of international
standards on quality management and quality
assurance developed to help companies effectively
document the quality system elements needed to
maintain an efficient quality system.
2. They are not specific to any one industry and can
be applied to organizations of any size.
3. ISO 9000 deals with the fundamentals of quality
management systems, including the eight
management principles on which the family of
standards is based.
4. Principles: 1. Customer Focus-Your customers
should be at the center of any company decisions.
Your customers, after all, are your raison d’être.
Routine activities should be carried out with a focus
on customer satisfaction by all employees.
2. Leadership- A dedicated leadership team can be
instrumental in creating quality culture. When a
company leader is engaged, supportive, and
dedicated to their staff, these qualities will be passed
down and emulated by their team members
3. Engagement of people- Workplace collaboration
can help to strengthen quality culture across an
organization. Regular cross-functional working is a
great way to generate ideas through brainstorming
sessions and working groups 4. Process approach-
The process approach is a method of thinking applying
to understand and plan the sequence and interactions
of processes in the system. 5. Improvement- An
organization is a constantly evolving entity. It should
be adaptable, flexible, and ready to embrace change.
6. Evidence based decision making- Evidence-
based decision making is a process for making the
best decisions possible using all the evidence
available. 7.Relationship management -Improper
communication and collaboration are yet another
common reason that companies fail to develop a
quality culture.
Q 8. What is Total Quality Management (TQM)? How
one can achieve TQM in their organization
1. The concept of TQM • Produce quality work the
first time.• Focus on the customer.• Have a strategic
approach to improvement.• Improve continuously.•
Encourage mutual respect and teamwork.
2. Total quality management (TQM) has been
defined as an integrated organizational effort
designed to improve quality at every level.
3. It is the process to produce a perfect product by
a series of measures
4. require an organized effort by the entire company
to prevent or eliminate errors at every stage in
production is called total quality management.
steps:1. Clarify your vision, mission, and values-The
TQM approach requires all employees to work
towards the same goals. This allows them to
understand where the company is heading, what you
want to accomplish, and the values they need to
adhere to when working and making decisions.
2. Develop ways to measure success-The only way to
know if you're succeeding is if you have a way to
measure success. This can be different for every
company and team
3. Identify your target audience and seek feedback
from them-Your target audience or customer group
depends on the product or service you sell.
Determining who your key customer groups are can
help you create products or services targeted to
them.
4. Develop an improvement plan-Using the
feedback you received, create a plan that helps you
improve in your weak areas. For example, if multiple
customers complained that one of your products
isn't long lasting, you can create a new one that suits
their needs. 5.Monitor data-After implementing your
improvement plan, monitor how your changes are
being received. You can resurvey customers to see if
they still recommend improvements or if they're
happy with your updates.
Q 6. Explain Six Sigma method of Quality control
Six Sigma(σ) 1.Daveloped by Motorola in late 1980 ,
Six Sigma is quality model Originally developed for
manufacturing process….,2.Sigma is the standard
deviation between mean of process and nearest
Specification limit there will be practically no items
that fails to meet the specification….,3.Six Sigma is
way to achieve business rowers emphasizing on lower
cost number of defects. This process will produce less
than 3.4 defects per million. To achieve this tangent it
uses a methodology known as DMATE 1.Define
opportunities 2.Measure performance 3.Anclyse the
opportunities 4.imoprove the performance 4. A six-
sigma method is one in which 99.99966% of all the
opportunities to produce some features of a
component are statistically expected to be free of
defects….,Six Sigma is a set of methods and tools for
process improvement…,5. In the 1980s, Motorola
was developing Quasar televisions which were
famous, but at the time there were lots of defects
that came up on that due to picture quality and
sound variations.
Characteristics of Six Sigma-1. Statistical Quality
Control- It denotes Standard Deviation in
statistics
.Standard Deviation is used for measuring the
quality of output. Standard Deviation is used to
measure variance, which is an essential tool for
measuring non conformance as far as the quality of
output is concerned. 2.Methodical Approach-Six
Sigma is not a merely quality improvement strategy
in theory, as it features a well-defined set system
approach of application in DMAIC and DMADV
which can be used to improve the quality of
production. The alternative method DMADV stands
for Design-Measure-Analyze-Design-Verify act and
Data-Based Approach.3. Project and Objective-
Based Focus: The Six Sigma process is
implemented for an organization's project tailored
to its specification and requirements.4. Customer
Focus- The customer focus is fundamental to the
Six Sigma approach. Quality improvement and
control standards are based on specific customer
requirements.
 Q. list all quality parameters require to establish to
good quality culture within the organization?
1.Customer Focus: The organization must have a
clear understanding of the needs and expectations
of its customers and strive to meet or exceed them.
2.Leadership Commitment: The top management
must demonstrate their commitment to quality by
setting the right examples and promoting quality
at all levels.
3.Continuous Improvement: The organization
must have a process in place for continuous
improvement and strive to enhance its products,
services, and processes.
4.Employee Involvement: Employees must be
encouraged to participate in quality initiatives and
provide suggestions for improvement.
5.Process-Based Approach: The organization must
establish processes to manage its operations and
ensure that they are effective and efficient.
6.Evidence-Based Decision Making: Decisions
must be based on data and facts, rather than
assumptions or opinions.
7.Supplier Relationships: The organization must
establish and maintain relationships with
suppliers who share its commitment to quality.
8.Training and Development: Employees must be
trained and developed to ensure that they have
the necessary skills and knowledge to perform
their jobs effectively.
9.Communication: Effective communication
channels must be established to ensure that
quality-related information is shared across the
organization.
10.By establishing these quality parameters, an
organization can create a culture of good quality
that promotes customer satisfaction, employee
engagement, and continuous improvement.
Q. classify the defects on the basis of severity levels
in software testing
1. Bug Severity- Severity defines how impactful
can a bug be to the system. Basically how severe it
is. For example, an application crashing defect will
be considered highly severe as compared to a
simple spelling mistake defect. Defect severity is
divided under 4 stages – low, minor, major, and
critical.
2. LOW – As the name suggests, these bugs do not
harm the system in any critical way. Although they
are harmless, yet valid and need to be removed.
3.MINOR – These bugs do affect the system in a
certain manner. However, do not restrict its
functioning in any way. The system might behave in
an undesirable manner but does not stop the
functioning of the system.
4.MAJOR – These bugs too do not collapse the
whole system. None the less hamper major parts of
it. Thus disrupting basic functions of the system.
5.CRITICAL – These bugs might cause the complete
shutdown of the system. Or affect the application in
a way that the user cannot proceed to the next task.
Such bugs need immediate attention.
6. Bug Priority – A) Priority defines the urgency of
fixing the bug. As an example consider a defect
about the logo not getting clearly displayed. This
bug is not critical from a technical point of view.
B) We can divide priority into 3 levels – High,
Medium, and Low.
1.HIGH – Such defect needs immediate attention as
it might lead to complete failure of the system. The
earliest resolution of such defects should be
conducted.
2.MEDIUM – Such bugs do not affect the working of
the system. These can be solved simultaneously
with the testing as well as the design phase.
These bugs do need to be fixed but do not need any
immediate attention.
3.LOW – These bugs are at the lowest priority.
These are fixed once the developer is done with the
high and medium-priority bugs.
Q. what is cyclomatic complexity and explain its
significance
1. Cyclomatic complexity is a software metric that
measures the complexity of a program by counting
the number of independent paths through its
source code. The higher the cyclomatic complexity
of a program, the more difficult it is to test,
understand, and maintain.
2.In software testing, cyclomatic complexity is
significant because it helps identify areas of a
program that are more likely to contain errors.
Programs with high cyclomatic complexity are
more likely to have defects, and therefore, require
more testing and quality assurance efforts.
3.By measuring the cyclomatic complexity of a
program, developers can better prioritize their
testing efforts, focusing on areas of the code that
are more complex and likely to have errors. This
can help to improve the effectiveness of testing,
leading to higher quality software.
4.Furthermore, the cyclomatic complexity metric
can be used as a threshold for defining test
coverage. A higher cyclomatic complexity value
indicates that more test cases are needed to achieve
complete code coverage, as there are more paths
through the program that need to be tested.
5.Complexity is an important metric for software
testing as it helps to identify areas of a program
that are more complex and likely to have errors. By
focusing testing efforts on these areas, developers
can improve the quality of their software and
reduce the risk of defects in production.
Q. explain the design and architecture of Test case 2: Verify that the user stories cover all the
automation test tools in software testing functional requirements of the product.
Below are some of the essential components that Test case 3: Verify that the user stories are testable
comprise the design and architecture of automation and measurable.
test tools: 3. Iteration testing: In Agile, the product is
1.Test automation framework: This component developed in small iterations. The testing scenario
includes the set of guidelines, rules, and standards should ensure that each iteration is tested
for designing and executing automated tests. A thoroughly before moving to the next iteration.
framework provides an organized approach for test Test case 1: Verify that the requirements of the
automation and helps to ensure consistency and iteration are clear and well defined.
maintainability of the test suite. The framework Test case 2: Verify that the developed functionality
comprises four layers - driver script, library files, meets the requirements of the iteration.
application module, and utility files. Test case 3: Verify that the developed functionality
2.Test script: This component is a set of does not break the existing functionality of the
instructions written in a programming language to product.
automate the testing process. Test scripts should be 4. Agile development methodology requires a well-
designed in such a way that they can be easily defined testing scenario that covers user story
maintained and reusable. testing, iteration testing, acceptance testing, and
3.Object repository: This component is a database regression testing. The above-mentioned test cases
that stores the objects of the application being can be used as a starting point to ensure that the
tested. The object repository helps to centralize the developed product meets the desired quality
management of test objects, making it easier to standards.
maintain test scripts. Q. A program reads an integer number within range
4.Test data: This component includes the inputs, [1, 100] and determines whether it is prime
expected outputs, and preconditions required for number or not. Design test cases for this program
executing the test scripts. using BVC, robust testing method.
5.Test execution engine: This component is 1. Test cases using Boundary value checking (BVC):
responsible for running the test scripts and the total number of test cases will be 4n + 1 = 5
generating the test results. It interacts with the test In this example, the set of minimum and maximum
automation framework, test scripts, and the values is shown below:
application under test to perform the test Min value = 1 + Min value = 2
automation. Max value = 100 - Max value = 99
6.Test reporting: This component is responsible for Nominal value = 50 - 55
generating reports that summarize the results of Using these values, test cases can be designed as
the automated tests. It provides detailed Test case id Integer Expected output
information on the test execution, test results, and variable
identified issues. 1 1 Not a prime no.
7. the design and architecture of automation test 2 2 Prime no.
tools in software testing include several essential 3 100 Not a prime no.
components that work together to automate the 4 99 Not a prime no.
testing process
5 53 Prime no.
Q. analyze the test scenario of agile development
2) Test cases using robust testing:
method and create some test cases
There is one variable, the total number of test cases
1. Agile development methodology focuses on
will be 6n + 1 = 7. The set of boundary values is
iterative and incremental development, where
shown below Min value = 1 + Min value = 2
requirements and solutions evolve through the
Max value = 100 - Max value = 99
collaborative effort of self-organizing and cross-
Nominal value = 50 - 55
functional teams. Testing is an integral part of the
Using these values, test cases can be designed
Agile development process, and the testing
Test Integer Expected output
scenarios must be well defined to ensure that the
case id variable
developed product meets the desired quality
standards. Here are some test scenarios 1 0 Invalid input
2. User story testing: In Agile, user stories are used 2 1 Not a prime no.
to define the requirements of the product. The 3 2 Prime no.
testing scenario should ensure that the user stories 4 100 Not a prime no.
are validated and verified. 5 99 Not a prime no.
Test case 1: Verify that the user stories are written 6 101 Invalid input
in a clear and concise language that can be easily 7 53 Prime no.
understood by the team.