ISTQB-FL

TOP INTERVIEW QUESTIONS

AND ANSWERS

Part- 2
Prepare By :
Mariam Elnshar
Software Testing Engineer
[email protected]
01201956860
Q #1) What is Dynamic Testing?
Answer: Dynamic testing is done by executing the code or program with
various input values and later on the output is verified.

Q #2) What is GUI Testing?

Answer: GUI or Graphical User Interface testing is the process of testing
the software’s user interface against the provided
requirements/mockups/HTML designs etc.,

Q #3) What is Formal Testing?

Answer: Software verification, carried out by following a test plan,
testing procedures and proper documentation with approval from the
customer is termed as Formal Testing.

Q #4) What is Risk-Based Testing?

Answer: Identifying the critical functionality in the system and then
deciding the orders in which these functionalities are to be tested and
perform testing is termed as Risk-based Testing.

Q #5) What is Early Testing?

Answer: Perform testing as soon as possible in the development
lifecycle to find defects at the early stages of STLC. Early testing is
helpful to reduce the cost of fixing defects at the later stages of STLC.

Q #6) What is Exhaustive Testing?

Answer: Testing functionality with all valid, invalid inputs and pre-
conditions is called Exhaustive testing.

Q #7) What is Defect Clustering?

Answer: Any small module or functionality may contain a number of
defects and to concentrate more on testing these functionalities is
known as Defect Clustering.
Q #8) What is Pesticide Paradox?
Answer: If already prepared test cases do not find defects, add/revise
test cases to find more defects, this is known as Pesticide Paradox.

Q #9) What is Static Testing?

Answer: Manual verification of the code without executing the program
is called Static Testing. In this process, the issues are identified in the
code by verifying code, requirement and design documents.

Q #10) What is Positive Testing?

Answer: It is the form of testing which is conducted on the application
to determine if the system works properly or not. Basically, it is known
as the “test to pass” approach.

Q #11) What is Negative Testing?

Answer: Testing software with a negative approach to check if the
system is not “showing error when not supposed to” and “not showing
error when supposed to” is termed as Negative Testing.

Q #12) What is an End-to-End Testing?

Answer: Testing the overall functionality of the system including the
data integration among all the modules is called End-to-End Testing.

Q #13) What is Exploratory Testing?

Answer: Exploring the application, understanding its functionalities,
adding (or) modifying the existing test cases for better testing is called
Exploratory testing.

Q #14) What is Monkey Testing?

Answer: Testing conducted on an application without any plan and
carried out randomly with the tests to find any system crash with the
intention of finding tricky defects is called Monkey Testing.
Q #15) What is Non-Functional Testing?
Answer: Validating various non-functional aspects of the system such as
user interfaces, user-friendliness, security, compatibility, Load, Stress,
and Performance, etc., is called Non-Functional testing.

Q #16) What is Usability Testing?

Answer: Checking how easily the end-users are able to understand and
operate the application is called Usability Testing.

Q #17) What is Security Testing?

Answer: Validating whether all security conditions are properly
implemented in the software (or) not is called Security testing.

Q #18) What is Performance Testing?

Answer: The process of measuring various efficiency characteristics of a
system such as response time, load stress transactions per minute,
transaction mix, etc., is termed Performance Testing.

Q #19) What is Load Testing?

Answer: Analyzing both the functional and performance behavior of an
application under various conditions is called Load Testing.

Q #20) What is Stress Testing?

Answer: Checking the application behavior under stress conditions
(or)
Reducing the system resources and keeping the load as constant and
checking how the application is behaving is called Stress Testing.

Q #21) What is Process?

Answer: A process is a set of practices performed to achieve a given
purpose; it may include tools, methods, materials or people.
Q #22) What is Software Configuration Management?
Answer: The process of identifying, organizing and controlling changes
to Software development and maintenance.
(or)
It is a methodology to control and manage a software development
project.

Q #23) What is a Testing Process / Life Cycle?

Answer: It includes the below factors:
• Writing a Test Plan
• Test Scenarios
• Test Cases
• Executing the Test Cases
• Test Results
• Defect Reporting
• Defect Tracking
• Defect Closing
• Test Release

Q #24) What is the full form of CMMI?

Answer: Capability Maturity Model Integration

Q #25) What is a Code Walk Through?

Answer: An informal analysis of the program source code to find the
defects and verify the coding techniques is termed as a Code Walk
Through.

Q #26) What is Unit Level Testing?

Answer: Testing of single programs, modules or unit of code is termed
as Unit Level Testing.
Q #27) What is Integration Level Testing?
Answer: Testing of related programs, modules (or) unit of code.
(or)
Partitions of the system which are ready for testing with other
partitions of the system are termed as Integration level testing.

Q #28) What is System Level Testing?

Answer: Testing of the entire computer system across all the modules is
termed as System-level testing. This kind of testing can include
Functional as well as Structural Testing.

Q #29) What is Alpha Testing?

Answer: Testing of a whole computer system before rolling out to the
UAT is termed as Alpha testing.

Q #30) What is User Acceptance Testing (UAT)?

Answer: UAT is the form of testing of a computer system by the client
to verify if it adhered to the provided requirements or not.

Q #31) What is a Test Plan?

Answer: It is a document describing the scope, approach, resources,
and schedule of testing activities. It identifies test items, features to be
tested, testing tasks, who will do each task, and any risks requiring
contingency planning.

Q #32) What is a Test Scenario?

Answer: Identifying all the possible areas to be tested (or) what is to be
tested is termed as Test Scenario.

Q #33) What is ECP (Equivalence Class Partition)?

Answer: It is a method for deriving test cases.
Q #34) What is a Defect?
Answer: Any flaw or imperfection in a software work product is termed
as a Defect.
(or)
When the expected result does not match with the application actual
result, it is termed as a Defect.

Q #35) What is Severity?

Answer: It defines the importance of the defect from the functional
point of view i.e. how critical is a defect with respect to the application.

Q #36) What is Priority?

Answer: It indicates the importance or urgency of fixing a defect

Q #37) What is Re-Testing?

Answer: Re-testing the application means verifying whether the defects
have been fixed or not.

Q #38) What is Regression Testing?

Answer: Verifying an existing functional and non-functional area after
making changes to the part of a software or addition of new features is
termed as Regression Testing.

Q #39) What is Recovery Testing?

Answer: Checking whether the system is able to handle some
unexpected or unpredictable situations is called Recovery Testing.

Q #40) What is Globalization Testing?

Answer: It is the process of verifying whether the software can be run
independently of its geographical and cultural environment. Verifying if
the application has the feature to set and change language, date,
format, and currency or if it is designed for global users.
Q #41) What is Localization Testing?
Answer: Verifying globalized application for a particular locality of
users, under cultural and geographical conditions is termed as
Localization Testing.

Q #42) What is Installation Testing?

Answer: Checking whether we are able to install a software successfully
(or) not, as per the guidelines given in the installation document is
called Installation Testing.

Q #43) What is Un-Installation Testing?

Answer: Checking whether we are able to uninstall the software from
the system successfully (or) not is called Un-Installation Testing

Q #44) What is Compatibility Testing?

Answer: Checking whether the application is compatible with different
software and hardware environment or not is called Compatibility
Testing.

Q #45) What is a Test Strategy?

Answer: It is a part of a test plan describing how testing is carried out
for the project and what testing types need to be performed on the
application.

Q #46) What is a Test Case?

Answer: A Test case is a set of pre-conditional steps to be followed with
input data and expected behavior to validate the functionality of a
system.

Q #47) What is Business Validation Test Case?

Answer: A test case that is prepared to check the business condition or
a business requirement is called the Business Validation test case.
Q #48) What is a Good Test Case?
Answer: A Test case that has a high priority of catching defects is called
a Good Test Case.

Q #49) What is Use Case Testing?

Answer: Validating a software to confirm whether it is developed as per
the use cases or not is called Use Case testing.

Q #50) What is a Defect Age?

Answer: The time gap between the date of detection & the date of
closure of a defect is termed as Defect Age.

Q #51) What is the Showstopper Defect?

Answer: A defect that does not permit testing to continue further is
called Showstopper Defect.

Q #52) What is a Test Closure?

Answer: It is the last phase of the STLC, where the management
prepares various test summary reports that explain the complete
statistics of the project based on the testing carried out.

Q #53) What is Bucket Testing?

Answer: Bucket testing is also known as A/B testing. It is mostly used to
study the impact of various product designs on website metrics. Two
simultaneous versions run on a single or a set of web pages to measure
the difference in click rates, interface, and traffic.
Q #54) What is meant by Entry Criteria and Exit Criteria in Software
Testing?
Answer: Entry Criteria is the process that must be present when a
system begins, like,
• SRS – Software
• FRS
• Use Case
• Test Case
• Test Plan
Exit criteria ensure whether the testing is completed and the
application is ready for release, like,
• Test Summary Report
• Metrics
• Defect Analysis Report
•
Q #55) What is Concurrency Testing?
Answer: This is a multiple user testing to access the application at the
same time to verify the effect on code, module or DB and it is mainly
used to identify the locking and deadlocking situations in the code.

Q #56) What is Web Application Testing?

Answer: Web application testing is done on a website to check – load,
performance, security, functionality, interface, compatibility and other
usability-related issues.

Q #57) What is Unit Testing?

Answer: Unit testing is done to check whether the individual modules
of the source code are working properly or not.
Q #58) What is Interface Testing?
Answer: Interface testing is done to check whether the individual
modules are communicating properly as per the specifications or not.
Interface testing is mostly used to test the user interface of GUI
applications.

Q #59) What is Gamma Testing?

Answer: Gamma testing is done when the software is ready for release
with the specified requirements, this testing is done directly by skipping
all the in-house testing activities.

Q #60) What is the Test Harness?

Answer: Test Harness is configuring a set of tools and test data to test
an application under various conditions, which involves monitoring the
output with the expected output for correctness.
The benefits of Testing Harness are: Productivity increase due to
process automation and increase in the product quality

Q #61) What is Scalability Testing?

Answer: It is used to check whether the functionality and performance
of a system are capable to meet the volume and size changes as per the
requirements.
Scalability testing is done using the load test by changing various
software, hardware configurations, and testing environment.

Q #62) What is Fuzz Testing?

Answer: Fuzz testing is a black-box testing technique that uses random
bad data to attack a program to check if anything breaks in the
application.
Q #63) What is the difference between QA, QC, and Testing?
Answer:
• QA: It is process-oriented and its aim is to prevent the
defects in an application.
• QC: QC is product-oriented and it is a set of activities used to
evaluate a developed work product.
• Testing: Executing and verifying an application with the
intention of finding defects.
•
Q #64) What is Data-Driven Testing?
Answer: It is an Automation testing process in which an application is
tested with multiple sets of data with different preconditions as an
input to the script.