QUALITY ASSURANCE (QA) | 2025/2026
LATEST EXAM | QUESTIONS WITH
VERIFIED ANSWERS | WITH
GUARANTEE PASS A+!!
Quality Assurance (QA): QA refers to the planned and systematic way of monitoring the
quality of process which is followed to produce a quality product. QA tracks the
outcomes and adjusts the process to meet the expectation.
Quality Control (QC): Concern with the quality of the product. QC finds the defects and
suggests improvements. The process set by QA is implemented by QC. The QC is the
responsibility of the tester.
Software Testing: is the process of ensuring that product which is developed by the
developer meets the user requirement. The motive to perform testing is to find the bugs
and make sure that they get fixed. - answers What is difference between QA, QC and
Software Testing?
A good time to start the QA is from the beginning of the project startup. This will lead to
plan the process which will make sure that product coming out meets the customer
quality expectation.QA also plays a major role in the communication between teams. It
gives time to step up the testing environment. The testing phase starts after the test
plans are written, reviewed and approved. - answers When to start QA in a project?
Verification: process of evaluating steps which is followed up to development phase to
determine whether they meet the specified requirements for that stage.
Validation: process of evaluating product during or at the end of the development
process to determine whether product meets specified requirements.
Difference between Verification and Validation:
Verification is Static Testing where as Validations is Dynamic Testing.
Verification takes place before validation.
Verification evaluates plans, documents, requirements and specifications, where as
Validation evaluates product.
Verification inputs are checklist, issues list, walk-through and inspection, where as in
Validation testing of actual product.
Verification output is set of documents, plans, specifications and requirement
documents where as in Validation actual product is output. - answers What are
verification and validation and difference between these two?
The difference between smoke and sanity testing is described below:
Sanity testing is performed when new build is released after fixing bugs where as
smoke testing is performed to check the major functionalities of the application.
Sanity is performed by the tester or the developer but smoke testing can be performed
by the tester or developer.
,Smoke testing is performed earlier where as sanity is performed after the smoke testing.
Sanity testing is narrow and deep approach of testing and smoke testing is focused
testing based on major functionalities. - answers What is difference between Smoke
testing and Sanity Testing?
Destructive testing includes methods where material is broken down to evaluate the
mechanical properties, such as strength, toughness and hardness.
For example, finding the quality of a weld is good enough to withstand extreme pressure
and also to verify the properties of a material.
Benefits of Destructive Testing (DT)
Verifies properties of a material
Determines quality of welds
Helps you to reduce failures, accidents and costs
Ensures compliance with regulations - answers What is destructive testing, and what
are its benefits?
The testware is:
The subset of software which helps in performing the testing of application.
Testware are required to plan, design, and execute tests. It contains documents,
scripts, inputs, expected results, set-up and additional software or utilities used in
testing.
Testware is term given to combination of all utilities and application software that
required for testing a software package.
Testware is special because it has:
1. Different purpose
2. Different metrics for quality
3. Different users - answers What is Testware?
The difference between Retesting and Regression testing are below:
Retesting is done to verify defects fixes where as regression is perform to check if the
defect fix have not impacted other functionality that was working fine before doing
changes in the code.
Retesting is planned testing based on the defect fixes listed where as regression is not
be always specific to any defect fix. Also regression can be executed for some modules
or all modules.
Retesting concern with executing those test cases that are failed earlier whereas
regression concern with executing test cases that was passed in earlier builds.
Retesting has higher priority over regression, but in some case retesting and
regression testing are carried out in parallel. - answers What is difference between
Retesting and Regression testing?
Bug Life Cycle:
When a tester finds a bug .The bug is assigned with NEW or OPEN status.
The bug is assigned to development project manager who will analyze the bug .He will
check whether it is a valid defect. If it is not valid bug is rejected, now status is
REJECTED.
, If not, next the defect is checked whether it is in scope. When bug is not part of the
current release .Such defects are POSTPONED
Now, Tester checks whether similar defect was raised earlier. If yes defect is assigned
a status DUPLICATE
When bug is assigned to developer. During this stage bug is assigned a status IN-
PROGRESS
Once code is fixed. Defect is assigned with FIXED status.
Next the tester will re-test the code. In case the test case passes the defect is CLOSED
If the test case fails again the bug is RE-OPENED and assigned to the developer.
That's all to Bug Life Cycle. - answers Explain bug life cycle.
Priority: concern with application from the business point of view.
It answers: How quickly we need to fix the bug? Or How soon the bug should get fixed?
Severity: concern with functionality of application. It deals with the impact of the bug on
the application.
How much the bug is affecting the functionality of the application?
Ex:
High Priority and Low Severity:
Company logo is not properly displayed on their website.
High Priority and High Severity:
Suppose you are doing online shopping and filled payment information, but after
submitting the form, you get a message like "Order has been cancelled."
Low Priority and High Severity:
If we have a typical scenario in which the application get crashed, but that scenario
exists rarely.
Low Priority and Low Severity:
There is a mistake like "You have registered success" instead of successfully, success
is written. - answers What is severity and priority of bug? Give some example.
Software problem are listed below:
1. Purchasing the license of tool (QTP, selenium, QC, LR)
2. Lack of skilled Tester to run the tool
3. Expectation that automated tests will find a lot of new defects
4. Maintenance of automated tests
5. Technical problems of tools - answers What are the common problems with software
automation?
QA stands for QUALITY ASSURANCE. QA team assures the quality by monitor the
whole development process. QA tracks the outcomes and adjusting process to meet the
expectation.
The role of Quality Assurance is discussed below:
QA team is responsible for monitoring the process to be carried out for development.
Responsibilities of QA team are planning testing execution process.
QA Lead creates the time tables and agrees on a Quality Assurance plan for the
product.
QA team communicated QA process to the team members.
LATEST EXAM | QUESTIONS WITH
VERIFIED ANSWERS | WITH
GUARANTEE PASS A+!!
Quality Assurance (QA): QA refers to the planned and systematic way of monitoring the
quality of process which is followed to produce a quality product. QA tracks the
outcomes and adjusts the process to meet the expectation.
Quality Control (QC): Concern with the quality of the product. QC finds the defects and
suggests improvements. The process set by QA is implemented by QC. The QC is the
responsibility of the tester.
Software Testing: is the process of ensuring that product which is developed by the
developer meets the user requirement. The motive to perform testing is to find the bugs
and make sure that they get fixed. - answers What is difference between QA, QC and
Software Testing?
A good time to start the QA is from the beginning of the project startup. This will lead to
plan the process which will make sure that product coming out meets the customer
quality expectation.QA also plays a major role in the communication between teams. It
gives time to step up the testing environment. The testing phase starts after the test
plans are written, reviewed and approved. - answers When to start QA in a project?
Verification: process of evaluating steps which is followed up to development phase to
determine whether they meet the specified requirements for that stage.
Validation: process of evaluating product during or at the end of the development
process to determine whether product meets specified requirements.
Difference between Verification and Validation:
Verification is Static Testing where as Validations is Dynamic Testing.
Verification takes place before validation.
Verification evaluates plans, documents, requirements and specifications, where as
Validation evaluates product.
Verification inputs are checklist, issues list, walk-through and inspection, where as in
Validation testing of actual product.
Verification output is set of documents, plans, specifications and requirement
documents where as in Validation actual product is output. - answers What are
verification and validation and difference between these two?
The difference between smoke and sanity testing is described below:
Sanity testing is performed when new build is released after fixing bugs where as
smoke testing is performed to check the major functionalities of the application.
Sanity is performed by the tester or the developer but smoke testing can be performed
by the tester or developer.
,Smoke testing is performed earlier where as sanity is performed after the smoke testing.
Sanity testing is narrow and deep approach of testing and smoke testing is focused
testing based on major functionalities. - answers What is difference between Smoke
testing and Sanity Testing?
Destructive testing includes methods where material is broken down to evaluate the
mechanical properties, such as strength, toughness and hardness.
For example, finding the quality of a weld is good enough to withstand extreme pressure
and also to verify the properties of a material.
Benefits of Destructive Testing (DT)
Verifies properties of a material
Determines quality of welds
Helps you to reduce failures, accidents and costs
Ensures compliance with regulations - answers What is destructive testing, and what
are its benefits?
The testware is:
The subset of software which helps in performing the testing of application.
Testware are required to plan, design, and execute tests. It contains documents,
scripts, inputs, expected results, set-up and additional software or utilities used in
testing.
Testware is term given to combination of all utilities and application software that
required for testing a software package.
Testware is special because it has:
1. Different purpose
2. Different metrics for quality
3. Different users - answers What is Testware?
The difference between Retesting and Regression testing are below:
Retesting is done to verify defects fixes where as regression is perform to check if the
defect fix have not impacted other functionality that was working fine before doing
changes in the code.
Retesting is planned testing based on the defect fixes listed where as regression is not
be always specific to any defect fix. Also regression can be executed for some modules
or all modules.
Retesting concern with executing those test cases that are failed earlier whereas
regression concern with executing test cases that was passed in earlier builds.
Retesting has higher priority over regression, but in some case retesting and
regression testing are carried out in parallel. - answers What is difference between
Retesting and Regression testing?
Bug Life Cycle:
When a tester finds a bug .The bug is assigned with NEW or OPEN status.
The bug is assigned to development project manager who will analyze the bug .He will
check whether it is a valid defect. If it is not valid bug is rejected, now status is
REJECTED.
, If not, next the defect is checked whether it is in scope. When bug is not part of the
current release .Such defects are POSTPONED
Now, Tester checks whether similar defect was raised earlier. If yes defect is assigned
a status DUPLICATE
When bug is assigned to developer. During this stage bug is assigned a status IN-
PROGRESS
Once code is fixed. Defect is assigned with FIXED status.
Next the tester will re-test the code. In case the test case passes the defect is CLOSED
If the test case fails again the bug is RE-OPENED and assigned to the developer.
That's all to Bug Life Cycle. - answers Explain bug life cycle.
Priority: concern with application from the business point of view.
It answers: How quickly we need to fix the bug? Or How soon the bug should get fixed?
Severity: concern with functionality of application. It deals with the impact of the bug on
the application.
How much the bug is affecting the functionality of the application?
Ex:
High Priority and Low Severity:
Company logo is not properly displayed on their website.
High Priority and High Severity:
Suppose you are doing online shopping and filled payment information, but after
submitting the form, you get a message like "Order has been cancelled."
Low Priority and High Severity:
If we have a typical scenario in which the application get crashed, but that scenario
exists rarely.
Low Priority and Low Severity:
There is a mistake like "You have registered success" instead of successfully, success
is written. - answers What is severity and priority of bug? Give some example.
Software problem are listed below:
1. Purchasing the license of tool (QTP, selenium, QC, LR)
2. Lack of skilled Tester to run the tool
3. Expectation that automated tests will find a lot of new defects
4. Maintenance of automated tests
5. Technical problems of tools - answers What are the common problems with software
automation?
QA stands for QUALITY ASSURANCE. QA team assures the quality by monitor the
whole development process. QA tracks the outcomes and adjusting process to meet the
expectation.
The role of Quality Assurance is discussed below:
QA team is responsible for monitoring the process to be carried out for development.
Responsibilities of QA team are planning testing execution process.
QA Lead creates the time tables and agrees on a Quality Assurance plan for the
product.
QA team communicated QA process to the team members.
