Software Testing Final Revision interview questions and Answers.

1. Software
Testing
February 5
Quality Analyst(Manual Testing)
Interview Questions Final Revision

2. 1. what is difference between QA, QC and Software Testing?
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
2. When to start QA in a project?
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.
3. What are verification and validation and difference between these two?
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, walkthroughs 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.
4. What is difference between Smoke testing and Sanity Testing?
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.

3.  Sanity testing is narrow and deep approach of testing and smoke testing is focused testing based
on major functionalities.
5. What is Test ware?
The test ware is:
 The subset of software which helps in performing the testing of application.
 Test ware is required to plan, design, and execute tests. It contains documents, scripts, inputs,
expected results, set-up and additional software or utilities used in testing.
 Test ware is term given to combination of all utilities and application software that required for
testing a software package.
Test ware is special because it has:
1. Different purpose
2. Different metrics for quality
3. Different users
6. What is difference between Retesting and Regression testing?
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.
7. Explain bug life cycle.
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.

4.  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.
8. What is severity and priority of bug? Give some example.
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?
Example
 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.
9. What is the role of QA in a project development?
QA stands for QUALITY Analyst. 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 Analyst 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.
 QA team ensures traceability of test cases to requirements.
10. What is the difference between build and release?
BUILD: is a number given to installable software that is given to testing team for testing by the
development team. Build number assigned are incremental and sequential.
RELEASE: is a number given to installable software that is handed over to customer by the developer or
tester.
The information of build, release and version are displayed in software help page. Using this build and
release customer can let the customer team know which release version build that are using.

5. e.g. "9.4.123.2" (Release Number, Version Number, Build Number, Patch Number)
11. Explain bug leakage and bug release.
Bug Leakage: When customer or end user discovered a bug which can be detected by the testing team.
Or when a bug is detected which can be detected in pervious build then this is called as Bug Leakage.
Bug release: is when a build is handed to testing team with knowing that defect is present in the
release. The priority and severity of bug is low. It is done when customer want the application on the
time. Customer can tolerate the bug in the released then the delay in getting the application and the
cost involved in removing that bug. These bugs are mentioned in the Release Notes handed to client for
the future improvement chances.
12. What is regression testing?
Regression Testing: When changes in the code of the software are made to fix the previous bug. Then
testing needs to be perform to ensure that it will not generate a new bug in the application and it works
as specified and that it has not negatively impacted any functionality that it offered previously.
Regression Testing is important because of following reason:
 That the application works even after the alteration in the code were made.
 The original functionality continues to work as specified even after doing changes in the
software application.
 The alteration to the software application has not introduced any new bugs.
13. What is Bug Triage?
Bug triage is a process to:
 Ensure bug report completeness.
 Analyze and assign bug to proper component.
 Assign bug to proper bug owner.
 Set appropriate bug priority.
 Adjust bug severity properly.
14. What type of tests you perform on the web based application?
For web application we perform following time of test:
1. Functionality Testing.
2. Usability Testing.
3. Navigation Testing.
4. Configuration and Compatibility testing.
5. Reliability and Availability Testing.
6. Performance Testing.
7. Load and Stress Testing.
8. Security Testing

6. 15. You are a tester. Now How will you choose which defect to remove in 1000000
defects?
First thing testers are not responsible for fixing the bug they are only responsible for debugging the bug
and prioritizing those bugs. These bugs are now reported in bug report template with the severity and
priority of the bug.
Tester assigns severity level to the defects depending upon their impact on other parts of application.
Every bug has its severity and priority values assign by tester. If a defect does not allow you to go ahead
and test the product, it is critical one so it has to be fixed as soon as possible. We have 5 levels as:
 Critical
 High
 Medium
 Low
 Cosmetic
16. What is the testing lifecycle?
There is no standard testing life cycle, but it is consist of following phases:
 Test Planning (Test Strategy, Test Plan, Test Bed Creation)
 Test Development (Test Procedures, Test Scenarios, Test Cases)
 Test Execution
 Result Analysis (compare Expected to Actual results)
 Defect Tracking
 Reporting
17. What is good code?
A good code is code that works. The good code must not contain the defect or bug and is readable by
other developers and easily maintainable. Organizations have coding standards all developers should
follow, and also every programmer and software engineer has different ideas about what is best and
what are too many or too few rules. We need to keep in mind that excessive use of rules can decrease
both productivity and creativity. Peer reviews and code analysis tools can be used to check for problems
and enforce standards.
18. What is the role of Bug Tracking System?
The Bug Tracking System role is discussed below:
 Testers and developers can know the status of the bug at every stage.
 Changes to the Status will be available to all team members.
 Developers and Testers can easily interact with bugs.
 Repetition of bugs will be avoided.
 Easy to distribute the bug among the developer.
 It will act as a centralized one for defects.

7. 19. What is data driven testing?
Data Driven is an automation testing part in which test input or output values, these values are
read from data files. It is performed when the values are changing by the time. The different
data files may include data pools, csv files, Excel files. The data is then loaded into variables in
recorded or manually coded scripts. For data driven testing we use Parameter zing and Regular
expression Technique.
20. Explain CMM.
Capability Maturity Model (CMM) is divided in five levels:
 Initial: The organization is characterized by an ad hoc set of activities. The processes aren't
defined and success depends on individual effort and heroics.
 Repeatable: In this level some processes are repeatable, possibly with consistent results.
 Defined: In this level, we define all processes are documented for both management and
engineering activities, and standards.
 Managed: Detailed measures of each process are defined and product quality data is routinely
collected. Both process and products are quantitatively understood and controlled.
 Optimizing: In this we optimize the application by following improvement process.
21. What the purpose of testing?
Software Testing: is the process of assuring that product which is developed by the manufactured by
developer is meeting the user requirement. The motive to perform testing is to find the bugs and make
sure that they get fixed. The purposes of testing are following:
 Quality assurance, Verification and Validation,
 To find the bugs before the product is released to customer.
 To improve the quality of the product
 The Purpose of Testing is to evaluate that the product is according to requirements
22. What is the difference between Stub and Driver?
STUBS: Assume you have 3 modules, Module A, Module B and module C. Module A is ready and
we need to test it, but module A calls functions from Module B and C which are not ready, so developer
will write a dummy module which simulates B and C and returns values to module A. This dummy
module code is known as stub.

8. DRIVERS: Now suppose you have modules B and C ready but module A which calls functions
from module B and C is not ready so developer will write a dummy piece of code for module A which will
return values to module B and C. This dummy piece of code is known as driver.
23. Explain the different types of Severity?
1. User Interface Defect-Low
2. Boundary Related Defects-Medium
3. Error Handling Defects-Medium
4. Calculation Defects-High
5. Interpreting Data Defects-High
6. Hardware Failures& Problems-High
7. Compatibility and Intersystem defects-High
8. Control Flow defects-High
9. Load conditions (Memory leakages under load testing)-High
24. How Severity and Priority are related to each other?
 Severity- tells the seriousness/depth of the bug where as
 Priority- tells which bug should rectify first.
 Severity- Application point of view
 Priority- User point of view
25. What is Bug?
A fault is a program which causes it to perform in an unintended or unanticipated manner.
26. What is Defect?
If software misses some feature or function from what is there in requirement it is called as defect.
27. Types of Software Testing
Black box testing – Internal system design is not considered in this type of testing. Tests are based on
requirements and functionality.
White box testing – This testing is based on knowledge of the internal logic of an application’s code.
Also known as Glass box Testing. Internal software and code working should be known for this type of
testing. Tests are based on coverage of code statements, branches, paths, conditions.
Unit testing – Testing of individual software components or modules. Typically done by the programmer
and not by testers, as it requires detailed knowledge of the internal program design and code. May
require developing test drive modules or test harnesses.

9. Incremental integration tests – Bottom up approach for testing i.e. continuous testing of an application
as new functionality is added; Application functionality and modules should be independent enough to
test separately. Done by programmers or by testers.
Integration testing - Testing of integrated modules to verify combined functionality after integration.
Modules are typically code modules, individual applications, client and server applications on a network,
etc. This type of testing is especially relevant to client/server and distributed systems.
Functional testing – This type of testing ignores the internal parts and focus on the output is as per
requirement or not. Black-box type testing geared to functional requirements of an application.
System testing – Entire system is tested as per the requirements. Black-box type testing that is based on
overall requirements specifications, covers all combined parts of a system.
End-to-end testing – Similar to system testing, involves testing of a complete application environment in
a situation that mimics real-world use, such as interacting with a database, using network
communications, or interacting with other hardware, applications, or systems if appropriate.
Sanity testing - Testing to determine if a new software version is performing well enough to accept it for
a major testing effort. If application is crashing for initial use then system is not stable enough for
further testing and build or application is assigned to fix.
Regression testing – Testing the application as a whole for the modification in any module or
functionality. Difficult to cover all the system in regression testing so typically automation tools are used
for these testing types.
Acceptance testing -Normally this type of testing is done to verify if system meets the customer
specified requirements. User or customers do this testing to determine whether to accept application.
Load testing – It’s a performance testing to check system behavior under load. Testing an application
under heavy loads, such as testing of a web site under a range of loads to determine at what point the
system’s response time degrades or fails.
Stress testing – System is stressed beyond its specifications to check how and when it fails. Performed
under heavy load like putting large number beyond storage capacity, complex database queries,
continuous input to system or database load.
Performance testing – Term often used interchangeably with ‘stresses and ‘load’ testing. To check
whether system meets performance requirements. Used different performance and load tools to do
this.

10. Usability testing – User-friendliness check. Application flow is tested, Can new user understand the
application easily, Proper help documented whenever user stuck at any point. Basically system
navigation is checked in this testing.
Install/uninstall testing - Tested for full, partial, or upgrade install/uninstall processes on different
operating systems under different hardware, software environment.
Recovery testing – Testing how well a system recovers from crashes, hardware failures, or other
catastrophic problems.
Security testing – Can system be penetrated by any hacking way? Testing how well the system protects
against unauthorized internal or external access. Checked if system, database is safe from external
attacks.
Compatibility testing – Testing how well software performs in a particular hardware/software/operating
system/network environment and different combination s of above.
Comparison testing – Comparison of product strengths and weaknesses with previous versions or other
similar products.
Alpha testing – In house virtual user environment can be created for this type of testing. Testing is done
at the end of development. Still minor design changes may be made as a result of such testing.
Beta testing – Testing typically done by end-users or others. Final testing before releasing application for
commercial purpose.
28. When to Start Testing?
An early start to testing reduces the cost, time to rework and error free software that is delivered to the
client. However in Software Development Life Cycle (SDLC) testing can be started from the
Requirements Gathering phase and lasts till the deployment of the software. However it also depends
on the development model that is being used.
For example in Water fall model formal testing is conducted in the Testing phase, but in incremental
model, testing is performed at the end of every increment/iteration and at the end the whole
application is tested.
Testing is done in different forms at every phase of SDLC like during Requirement gathering phase, the
analysis and verifications of requirements are also considered testing. Reviewing the design in the
design phase with intent to improve the design is also considered as testing. Testing performed by a
developer on completion of the code is also categorized as Unit type of testing.

11. 29. When to Stop Testing?
Unlike when to start testing it is difficult to determine when to stop testing, as testing is a never ending
process and no one can say that any software is 100% tested. Following are the aspects which should be
considered to stop the testing:
Testing deadlines.
Completion of test case execution.
Completion of Functional and code coverage to a certain point.
Bug rate falls below a certain level and no high priority bugs are identified.
Management decision.