Interview questions for manual testing technology.

What’s Ad Hoc Testing ?
A testing where the tester tries to break the software by randomly trying functionality of software./
=Ad hoc Testing, also known as Random Testing or MonkeyTesting, is a method of software
testing without any planning and documentation. The tests are conducted informally and
randomly without any formal expected results. The tester improvise the steps and arbitrarily
executes them (like a monkey typing while dancing).
What’s the Accessibility Testing ?
Testing that determines if software will be usable by people with disabilities./
=Accessibility testing is a type of systems testing designed to determine whether individuals
with disabilities will be able to use the system in question, which could be software, hardware, or
some other type of system.
What’s the Alpha Testing ?
The Alpha Testing is conducted at the developer sites and in a controlled environment by the end user of
the software./
= Alpha testing is final testing before the software is released to the general public. It has two
phases: In the first phase of alpha testing, the software is tested by in-house developers. They
use either debugger software, or hardware-assisted debuggers. The goal is to catch bugs
quickly.
What’s the Beta Testing ?
Testing the application after the installation at the client place./
=A beta test is the second phase of software testing in which a sampling of the intended
audience tries the product out. (Beta is the second letter of the Greek alphabet.) Originally, the
term alpha testing meant the first phase of testing in a software development process.
What is Component Testing ?
Testing of individual software components (Unit Testing)./
= Component Testing is considered as the Module Testing, because we are testing each
module or component differently and effectively.
Suppose there is only a one project which consists of 10 components and we are testing each
component differently and effectively than it is known as component testing.

What’s Compatibility Testing ?
In Compatibility testing we can test that software is compatible with other elements of system./
Compatibility is a non- functional testing to ensure customer satisfaction. It is to determine
whether your software application or product is proficient enough to run in different browsers,
database, hardware, operating system, mobile devices and networks
What is Concurrency Testing ?
Multi-user testing geared towards determining the effects of accessing the same application code, module
or database records. Identifies and measures the level of locking, deadlocking and use of single-threaded
code and locking semaphores./
= Concurrency testing is also known as multi-user testing, performed to identify the defects in
an application when multiple users login to the application.
It helps in identifying and measuring the problems in system parameters such as response
time, throughput, locks/dead locks or any other issues associated with concurrency.
What is Conformance Testing?
The process of testing that an implementation conforms to the specification on which it is based. Usually
applied to testing conformance to a formal standard.
= Conformance testing also known as Compliance testing is a nonfunctional testing technique
which is done to validate, weather the system developed meets the organization’s prescribed
standards or not.
Non Functional Testing
There is a separate category of testing known as “Non Functional Testing”.
Nonfunctional testing, as the name suggests, focuses on the nonfunctional features of the
software. These nonfunctional features (which are not limited to) can include the below points:
 Load testing
 Stress Testing
 Volume Testing
 Compliance testing
 Operations Testing
 Documentation Testing
What is Context Driven Testing ?
The context-driven school of software testing is flavor of Agile Testing that advocates continuous and
creative evaluation of testing opportunities in light of the potential information revealed and the value of
that information to the organization right now./

Context-driven testing is more a testing approach rather than a testing technique, as it
recommends testers to choose their test techniques, test deliverable, test documentation and
test objectives by looking into the details of the specific situation.
Context-driven testing method is useful when programmers are not provided with any
documents.
The context-driven approach is based on the judgmental call of programmers and testers to
develop a software product.
What is Data Driven Testing ?
Testing in which the action of a test case is parameterized by externally defined data values, maintained
as a file or spreadsheet. A common technique in Automated Testing.
= Data-driven testing (DDT) is a methodology in which iterative repetition of the same sequence of
test steps are performed with the help of a data source in order to drive the input values of those
steps and/or the expected values while verification steps are performed. The environment settings
and control in the case of data-driven testing are not hard-coded.
In other words, data-driven testing is the building of a test script to execute together with all their
related data sets in a framework, which makes use of reusable test logic. Data-driven testing
provides advantages like reusability, repeatability, separation of test logic from test data and
reduction of the number of test cases.
What is Conversion Testing ?
Testing of programs or procedures used to convert data from existing systems for use in replacement
systems.
= Conversion testing is to verify that one data format can be converted into another data format
so that the converted data format can be used seamlessly by the application under test
appropriately.
Any kind of data can be converted from any form to another; however, for web-based
application, the webpages should be of the form HTML that should agree to W3C HTML
specification so that browsers can render the page correctly.
What is Dependency Testing ?
Examines an application’s requirements for pre-existing software,initial states and configuration in order
to maintain proper functionality.
= Dependency Testing, a testing technique in which an application's requirements are pre-
examined for an existing software, initial states in order to test the proper functionality.

The impacted areas of the application are also tested when testing the new features or existing
features.
What is Depth Testing ?
A test that exercises a feature of a product in full detail./
= Depth Testing is a testing technique in which feature of a product is tested in full detail. Each
of the feature is tested exhaustively during the integration phase and the defects are logged, are
captured across all parameters, functional and non functional.
What is Dynamic Testing ?
Testing software through executing it. See also Static Testing.
= Dynamic Testing is a kind of software testing technique using which the dynamic behavior of the code
is analysed.
For Performing dynamic, testing the software should be compiled and executed and parameters such as
memory usage, CPU usage, response time and overall performance of the software are analyzed.
Dynamic testing involves testing the software for the input values and output values are analyzed.
Dynamic testing is the Validation part of Verification and Validation.
DynamicTesting Techniques
The Dynamic Testing Techniques are broadly classified into two categories. They are:
 Functional Testing
 Non-Functional Testing
Levelsof DynamicTesting
There are various levels of Dynamic Testing Techniques. They are:
 Unit Testing
 Integration Testing
 System Testing
 Acceptance Testing
What is Endurance Testing ?
Checks for memory leaks or other problems that may occur with prolonged execution./

Endurance Testing also known as Soak Testing is performed to determine if the application under test
can sustain the continuous loads.
Endurance testing, non-functional testing involves examining the system if it can withstand a huge load
for a longer period of time and thereby measuring the system's reaction parameters.
What is End-to-End testing ?
Testing 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.
= End-to-end testing is a technique used to test whether the flow of an application right from start to
finish is behaving as expected. The purpose of performing end-to-end testing is to identify system
dependencies and to ensure that the data integrity is maintained between various system components
and systems.
The entire application is tested for critical functionalities such as communicating with the other systems,
interfaces, database, network, and other applications.
What is Exhaustive Testing ?
Testing which covers all combinations of input values and preconditions for an element of the software
under test.
Exhaustive testing is a testing or quality assurance approach in which all possible combinations of
scenarios and use/test cases are used for testing.
In testing software, it is all the possible combinations of every type of input as well as every permutation
and variation of how the input is carried out to ensure that everything works as expected. This goes the
same for hardware testing—pressing any and all combinations of buttons and switches to determine
which ones expose a bug so that it can be fixed.
What is Gorilla Testing ?
Testing one particular module, functionality heavily.
Gorilla Testing is a testing technique in which testers, sometimes developers also join hands with testers
to test a particular module thoroughly in all aspects.
Gorilla Testing, a technique in which repetitive Manual Testing process, which a tester would have done
several times before, is done again to test the robustness of the system.
What is Installation Testing ?

Confirms that the application under test recovers from expected or unexpected events without loss of data
or functionality. Events can include shortage of disk space,unexpected loss of communication, or power
out conditions.
Installation Testing is performed to verify if the software has been installed with all the necessary
components and the application is working as expected. This is very important as installation would be
the first user interaction with the end users.
Companies launch Beta Version just to ensure smoother transition to the actual product.
What is Localization Testing ?
This term refers to making software specifically designed for a specific locality.
Localization testing is performed to verify the quality of a product's localization for a particular target
culture/locale and is executed only on the localized version of the product.
What is Loop Testing ?
A white box testing technique that exercises program loops.
Loop testing a white box testing technique performed to validate the loops. There are four kinds of loops
as mentioned below:
 Simple Loops
 Nested Loops
 Concatenated Loops
 Unstructured Loops
What is Mutation Testing ?
Mutation testing is a method for determining if a set of test data or test cases is useful, by deliberately
introducing various code changes (‘bugs’) and retesting with the original test data/cases to determine if
the ‘bugs’ are detected. Proper implementation requires large computational resources.
Mutation Testing is a type of software testing where we mutate (change) certain statements in the source
code and check if the test cases are able to find the errors. It is a type of white box testing which is mainly
used for unit testing. The changes in mutant program are kept extremely small, so it does not affect the
overall objective of the program.
The goal of Mutation Testing is to assess the quality of the test cases which should be robust enough to
fail mutant code. This method is also called as Fault based testing strategy as it involves creating fault in
the program
What is Monkey Testing ?

Testing a system or an Application on the fly, i.e. just few tests here and there to ensure the system or an
application does not crash out.
Monkey testing is a software testing technique in which the testing is performed on the system under test
randomly. The Input data that is used to test also generated randomly and keyed into the system.
What is Positive Testing ?
Testing aimed at showing software works. Also known as “test to pass”. See also Negative Testing.
Positive testing is a testing technique to show that a product or application under test does what it is
supposed to do. Positive testing verifies how the application behaves for the positive set of data.
Positive Testing verifies if the application is Not showing error when it is not supposed to and showing
error when it is supposed to.
What is Negative Testing ?
Testing aimed at showing software does not work. Also known as “test to fail”. See also Positive Testing.
Negative testing is performed to ensure that the product or application under test does NOT fail when an
unexpected input is given. The purpose of Negative testing is to break the system and to verify the
application response during unintentional inputs.
What is Path Testing ?
Testing in which all paths in the program source code are tested at least once.
Path testing is an approach to testing where you ensure that every path through a program has been
executed at least once. You normally use a dynamic analyzer tool or test coverage analyzers to check
that all of the code in a program has been executed. The starting point for path testing is a program flow
graph.
What is Performance Testing ?
Testing conducted to evaluate the compliance of a system or component with specified performance
requirements. Often this is performed using an automated test tool to simulate large number of users. Also
known as “Load Testing”.

Performance testing, a non-functional testing technique performed to determine the system parameters in
terms of responsiveness and stability under various workload. Performance testing measures the quality
attributes of the system, such as scalability, reliability and resource usage.
What is Ramp Testing ?
Continuously raising an input signal until the system breaks down.
Ramp testing is the type of testing consisting in raising an input signal continuously until the system
breaks down. It may be conducted by the testing team or the performance engineer.
What is Recovery Testing ?
Confirms that the program recovers from expected or unexpected events without loss of data or
functionality. Events can include shortage of disk space,unexpected loss of communication, or power out
conditions.
Recovery testing is a type of non-functional testing technique performed in order to determine how quickly
the system can recover after it has gone through system crash or hardware failure. Recovery testing is
the forced failure of the software to verify if the recovery is successful.
What is the Re-testing testing ?
Retesting- Again testing the functionality of the application.
Re-testing is a type of testing performed to check the test cases that were unsuccessful in
the final execution are successfully pass after the defects are repaired.
What is the Regression testing ?
Regression- Check that change in code have not effected the working functionality.
Regression testing is a type of software testing executed to check whether a code change has not
unfavorably disturbed current features & functions of an Application.
What is Sanity Testing ?
Brief test of major functional elements of a piece of software to determine if its basically operational.
Sanity testing, a software testing technique performed by the test team for some basic tests. The aim of
basic test is to be conducted whenever a new build is received for testing. The terminologies such as

Smoke Test or Build Verification Test or Basic Acceptance Test or Sanity Test are interchangeably used,
however, each one of them is used under a slightly different scenario.
Sanity test is usually unscripted, helps to identify the dependent missing functionalities. It is used to
determine if the section of the application is still working after a minor change.
Sanity testing can be narrow and deep. Sanity test is a narrow regression test that focuses on one or a
few areas of functionality.
What is Scalability Testing ?
Performance testing focused on ensuring the application under test gracefully handles increases in work
load.
Scalability, a performance testing parameter that investigates a system's ability to grow by increasing the
workload per user, or the number of concurrent users, or the size of a database.
Attributes:
 Response Time
 Throughput
 Hits per second, Request per seconds, Transaction per seconds
 Performance measurement with number of users
 Performance measurement under huge load
 CPU usage, Memory usage while testing in progress
 Network Usage - data sent and received
 Web server - Request and response per second
What is Security Testing ?
Testing which confirms that the program can restrict access to authorized personnel and that the
authorized personnel can access the functions available to their security level.
Security Testing is a variant of Software Testing which ensures, that system and applications in an
organization, are free from any loopholes that may cause a big loss. Security testing of any system is
about finding all possible loopholes and weaknesses of the system which might result into a loss of
information at the hands of the employees or outsiders of the Organization.
The goal of security testing is to identify the threats in the system and measure its potential vulnerabilities.
It also helps in detecting all possible security risks in the system and help developers in fixing these
problems through coding.

What is Stress Testing ?
Stress testing is a form of testing that is used to determine the stability of a given system or entity. It
involves testing beyond normal operational capacity, often to a breaking point, in order to observe the
results.
Stress testing a Non-Functional testing technique that is performed as part of performance testing.
During stress testing, the system is monitored after subjecting the system to overload to ensure that the
system can sustain the stress.
The recovery of the system from such phase (after stress) is very critical as it is highly likely to happen in
production environment.
What is Smoke Testing ?
A quick-and-dirty test that the major functions of a piece of software work. Originated in the hardware
testing practice of turning on a new piece of hardware for the first time and considering it a success if it
does not catch on fire.
Smoke Testing is a testing technique that is inspired from hardware testing, which checks for the smoke
from the hardware components once the hardware's power is switched on. Similarly in Software testing
context, smoke testing refers to testing the basic functionality of the build.
If the Test fails, build is declared as unstable and it is NOT tested anymore until the smoke test of the
build passes.
What is Soak Testing ?
Running a system at high load for a prolonged period of time. For example, running severaltimes more
transactions in an entire day (or night) than would be expected in a busy day, to identify and performance
problems that appear after a large number of transactions have been executed.
Soak Testing also known as Endurance Testing is performed to determine if the application under test
can sustain the continuous loads.
Soak testing, non-functional testing involves examining the system if it can withstand a huge load for a
longer period of time and there by measuring the system's reaction parameters.

What’s the Usability testing ?
Usability testing is for user friendliness.
Usability testing is a way to see how easy to use something is by testing it with real users. Users are
asked to complete tasks, typically while they are being observed by a researcher, to see where they
encounter problems and experience confusion.
What’s the User acceptance testing ?
User acceptance testing is determining if software is satisfactory to an end-user or customer.
User acceptance testing, a testing methodology where the clients/end users involved in testing the
product to validate the product against their requirements. It is performed at client location at developer's
site.
For industry such as medicine or aviation industry, contract and regulatory compliance testing and
operational acceptance testing is also carried out as part of user acceptance testing.
UAT is context dependent and the UAT plans are prepared based on the requirements and NOT
mandatory to execute all kinds of user acceptance tests and even coordinated and contributed by testing
team.
What’s the Volume Testing ?
We can perform the Volume testing, where the system is subjected to large volume of data.
Volume testing is a Non-functional testing that is performed as part of performance testing where the
software is subjected to a huge volume of data. It is also referred as flood testing.
1.What are the components ofan SRS?
{A software requirements specification (SRS) is a description of a software system to be
developed. It lays out functional and non-functional requirements, and may include a set of use
cases that describe user interactions that the software must provide}
An SRS contains the following basic components:
Introduction
Overall Description
External Interface Requirements
System Requirements
System Features

2. What is the difference between a test plan and a QA plan?
A test plan lays out what is to be done to test the product and includes how quality control will work to
identify errors and defects. A QA plan on the other hand is more concerned with prevention of errors and
defects rather than testing and fixing them.
3. Howdo you test an application if the requirements are not available?
If requirements documentation is not available for an application, a test plan can be written based on
assumptions made about the application. Assumptions that are made should be well documented in the
test plan.
4. What is a peer review?
Peer reviews are reviews conducted among people that work on the same team. For example, a test case
that was written by one QA engineer may be reviewed by a developer and/or another QA engineer.
5. Howcan you tell when enough test cases have been created to adequately test a system or
module?
You can tell that enough test cases have been created when there is at least one test case to cover every
requirement. This ensures that all designed features of the application are being tested.
6. Who approves test cases?
The approver of test cases varies from one organization to the next. In some organizations, the QA lead
may approve the test cases while another approves them as part of peer reviews.
7. Give an example ofwhat can be done when a bug is found.
When a bug is found, it is a good idea to run more tests to be sure that the problem witnessed can be
clearly detailed. For example, let say a test case fails when Animal=Cat and. A tester should run more
tests to be sure that the same problem doesn’t exist with Animal=dog. Once the tester is sure of the full
scope of the bug can be documented and the bug adequately reported. This question is one of the most
frequently asked manual testing interview questions.
8. Who writes testplans and test cases?
Test plans are typically written by the quality assurance lead while testers usually write test cases.
9. Is quality assurance and testing the same?
Quality assurance and testing is not the same. Testing is considered to be a subset of QA. QA is should
be incorporated throughout the software development life cycle while testing is the phase that occurs after
the coding phase.
Typical Manual Testing Interview Questions:

10. What is a negative test case?
Negative test cases are created based on the idea of testing in a destructive manner. For example, testing
what will happen if inappropriate inputs are entered into the application.
11. Ifan application is in production, and one module ofcode is modified, is it necessary to retest
just that module or should all of the other modules be tested as well?
It is a good idea to perform regression testing and to check all of the other modules as well. At the least,
system testing should be performed.
12. What should be included in a test strategy?
The test strategy includes a plan for how to test the application and exactly what will be tested (user
interface, modules, processes,etc.). It establishes limits for testing and indicates whether manual or
automated testing will be used.
13. What can be done to develop a test for a system ifthere are no functional specifications or
any system and development documents?
When there are no functional specifications or system development documents, the tester should
familiarize themselves with the product and the code. It may also be helpful to perform research to find
similar products on the market.
14. What are the functional testing types?
The following are the types of functional testing:
Compatibility
Configuration
Error handling
Functionality
Input domain
Installation
Inter-systems
Recovery
15. What is the difference between sanity testing and smoke testing?
When sanity testing is conducted, the product is sent through a preliminary round of testing with the test
group in order to check the basic functionality such as button functionality. Smoke testing, on the other
hand is conducted by developers based on the requirements of the client.
16. Explain random testing.
Random testing involves checking how the application handles input data that is generated at random.
Data types are typically ignored and a random sequence of letter, numbers, and other characters are
inputted into the data field.
17. Define smoke testing.
Smoke testing is a form of software testing that is not exhaustive and checks only the most crucial

components of the software but does not check in more detail.
Advanced Manual Testing InterviewQuestions
18. What steps are involved in sanity testing?
Sanity testing is very similar to smoke testing. It is the initial testing of a component or application that is
done to make sure that it is functioning at the most basic level and it is stable enough to continue more
detailed testing.
19. What is the difference between WinRunner and Rational Robot?
WinRunner is a functional test tool but Rational Robot is capable of both functional and performance
testing. Also, WinRunner has 4 verification points and Rational Robot has 13 verification points.
20. What is the purpose ofthe testing process?
The purpose of the testing process is to verifying that input data produces the anticipated output.
21. What is the difference between QA and testing?
The goals of QA are very different from the goals of testing. The purpose of QA is to prevent errors is
the application while the purpose of testing is to find errors.
22. What is the difference between Quality Control and Quality Assurance?
Quality control (QC) and quality assurance (QA) are closely linked but are very different concepts. While
QC evaluates a developed product, the purpose of QA is to ensure that the development process is at a
level that makes certain that the system or application will meet the requirements.
23. What is the difference between regression testing and retesting?
Regression testing is performing tests to ensure that modifications to a module or system do not have a
negative effect on previous releases. Retesting is merely running the same testing again. Regression
testing is widely asked manual testing interview questions and hence further research to understand this
topic is needed.
24. Explain the difference between bug severity and bug priority.
Bug severity refers to the level of impact that the bug has on the application or system while bug priority
refers to the level of urgency in the need for a fix.
25. What is the difference between system testing and integration testing?
For system testing, the entire system as a whole is checked, whereas for integration testing, the interaction
between the individual modules are tested.
26. Explain the term bug.

A bug is an error found while running a program. Bug fall into two categories: logical and syntax.
Senior Tester InterviewQuestions
27. Explain the difference between functional and structural testing.
Functional testing is considered to be behavioral or black box testing in which the tester verifies that the
system or application functions according to specification. Structural testing on the other hand is based
on the code or algorithms and is considered to be white box testing.
28. Define defect density.
Defect density is the total number of defects per lines of code.
29. When is a test considered to be successful?
The purpose of testing is to ensure that the application operates according to the requirements and to
discover as many errors and bugs as possible. This means that tests that cover more functionality and
expose more errors are considered to be the most successful.
30. What good bug tracking systems have you used?
This is a simple interview question about your experience with bug tracking. Provide the system/systems
that you are most familiar with if any at all. It would also be good to provide a comparison of the pros
and cons of several if you have experience. Bug tracking is the essence of testing process and is a must
asked manual testing interview questions in any interview. Do not forget this.
31. In which phase should testing begin – requirements,planning, design,or coding?
Testing should begin as early as the requirements phase.
32. Can you test a program and find 100% ofthe errors?
It is impossible to fine all errors in an application mostly because there is no way to calculate how many
errors exist. There are many factors involved in such a calculation such as the complexity of the program,
the experience of the programmer, and so on. This Manual testing interview questions is the most tricky
questions considered by testers.
33. What is the difference between debugging and testing?
The main difference between debugging and testing is that debugging is typically conducted by a
developer who also fixes errors during the debugging phase. Testing on the other hand, finds errors rather
than fixes them. When a tester finds a bug, they usually report it so that a developer can fix it.
34. Howshould testing be conducted?
Testing should be conducted based on the technical requirements of the application.

35. What is considered to be a good test?
Testing that covers most of the functionality of an object or system is considered to be a good test.
36. What is the difference between top-down and bottom-up testing?
Top-Down testing begins with the system and works its way down to the unit level. Bottom-up testing
checks in the opposite direction, unit level to interface to overall system. Both have value but bottom-up
testing usually aids in discovering defects earlier in the development cycle, when the cost to fix errors is
lower.
37. Explain howto develop a test plan and a test case.
A test plan consists of a set of test cases. Test cases are developed based on requirement and design
documents for the application or system. Once these documents are thoroughly reviewed, the test cases
that will make up the test plan can be created.
38. What is the role ofquality assurance in a product development lifecycle?
Quality assurance should be involved very early on in the development life cycle so that they can have a
better understanding of the system and create sufficient test cases. However,QA should be separated
from the development team so that the team is not able to build influence on the QA engineers.
39. What is the average size ofexecutables that you have created?
This is a simple interview question about our experience with executables. If you know the size of any
that you’ve created,simply provide this info.
40. What version ofthe Oracle are you familiar with?
This is an interview question about experience. Simply provide the versions of the software that you have
experience with.
41. Howis an SQL query executed in Oracle 8?
This is an interview question to check your experience with Oracle and you can simply provide the
answer “from the command prompt.” If you do not have Oracle experience, do not pretend and simply
state that you have not worked on an Oracle database. Though this is a common manual testing interview
questions, the answers can be different. Because if you have experience in other tools such as TOAD,
SQL server etc.,you can conveniently answer as per your experience.
42. Have you performed tests on the front-end and the back-end?
This is an interview question in which you should explain whether you performed testing on the GUI or
the server portion of previous applications.
43. What is the most difficult problem you’ve found during testing?
This is a simple interview question in which you should provide an example. This is one of most tricky
manual testing interview questions as your answer will decide your job. You need to answer in such a
way that your problem solving skills and your eagerness to learn new things, and your dedication towards

the job will indicated by your answers.
44. What were your testing responsibilities at your previous employer?
This interview question is very likely being asked to verify your knowledge of your resume. Make sure
that you know what is on your resume and that it is the truth.
Difference between Retesting and Regression Testing
Regression Testing Re-testing

 Regression testing is carried out to confirm whether
a recent program or code change has not adversely
affected existing features
 Re-testing is carried out to confirm the test cases that
failed in the final execution are passing after the defects
are fixed
 The purpose of regression testing is that new code
changes should not have any side effects to existing
functionalities
 Re-testing is done on the basis of the defect fixes
 Defect verification is not the part of regression
testing
 Defect verification is the part of re-testing
 Based on the project and availability of resources,
regression testing can be carried out parallel with
Re-testing
 Priority of re-testing is higher than regression testing, so
it is carried out before regression testing
 You can do automation for regression testing,
manual testing could be expensive and time
consuming
 You cannot automate the test cases for Retesting
 Regression testing is known as a generic testing  Re-testing is a planned testing
 Regression testing is done for passed test cases  Retesting is done only for failed test cases
 Regression testing checks for un-expected side-
effects
 Re-testing makes sure that the original fault has been
corrected
 Regression testing is only done when there is any
modification or changes become mandatory in
existing project
 Re-testing executes a defect with same data and the same
environment with different inputs with new build
 Test cases for regression testing can be obtained
from the functional specification, user tutorials and
manuals, and defect reports in regards to corrected
problems
 Test cases for retesting cannot be obtained before start
testing.

Interview questions for manual testing technology.

Recommended

More Related Content

What's hot (20)

Similar to Interview questions for manual testing technology. (20)

Recently uploaded (20)

Interview questions for manual testing technology.