Software Testing Interview Questions
and Correct Answers. 100% 2024, Update.
What is Software engineering?
Software engineering is a systematic approach to the analysis, design, implementation
and maintenance of software.
What is test case?
- Test Case is a software engineering terminology
- Test Cases are also referred to as Test Scripts
- Collection of related test cases are referred to as Test Suite. e.g. regression test suite.
- Test Case contains a set of test steps and expected results
- Test Cases based on requirements. Test Cases can be written for Use cases also.
- Test Cases are usually documented and can be documented in word or excel or Test
management tools like HP Quality Center
- Test Case template usually contains below information
* Importance of the Test Case (High / Medium / Low)
* Complexity of the Test Case (High / Medium / Low)
* Test Case author
* Test Case reviewer
* Requirements covered by Test Case
* Test Case ID
* Test Case description
* Test steps and expected result for each step
* Actual result for each of the expected result
* Automated or Manual Test Case
* Test Case result (Pass or Fail)
* Comments / Remarks
What is the difference between Error, Bug and Defect ?
...
Why is V model called as V Model?
V Model is presented in V shape instead of being straight or linear like Waterfall model.
Name of the model has come because of the V Shape, similarly there are other models
that are named of their shape like Spiral model.
What is DFD (Data Flow Diagram)?
- DFD stands for Data flow diagram
- DFDs are used during Analysis and design phase of SDLC (Software Development
Life Cycle)
- DFDs are used for visualization of data flow and data processing in a information
system.
- DFD will show inputs, outputs, processing and where data will be stored.
- DFD will show communication or interaction between the system and external actors.
- Context-level DFD or 0 Level DFD is a diagram which is a highest level of view of the
,system.
- Context-level DFD indicates actors outside system interacting with the system.
What is Flow Chart?
A flowchart is a type of diagram that represents an algorithm or process, showing the
steps as boxes of various kinds, and their order by connecting these with arrows. This
diagrammatic representation can give a step-by-step solution to a given problem.
Process operations are represented in these boxes, and arrows connecting them
represent flow of control. Data flows are not typically represented in a flowchart, in
contrast with data flow diagrams; rather, they are implied by the sequencing of
operations. Flowcharts are used in analyzing, designing, documenting or managing a
process or program in various fields.
What is Regression Testing?
Regression testing is any type of software testing that seeks to uncover new software
bugs, or regressions, in existing functional and non-functional areas of a system after
changes, such as enhancements, patches or configuration changes, have been made
to them.
The intent of regression testing is to ensure that a change such as those mentioned
above has not introduced new faults.[1] One of the main reasons for regression testing
is to determine whether a change in one part of the software affects other parts of the
software.[2]
Common methods of regression testing include rerunning previously-completed tests
and checking whether program behavior has changed and whether previously-fixed
faults have re-emerged. Regression testing can be used to test a system efficiently by
systematically selecting the appropriate minimum set of tests needed to adequately
cover a particular change.
What is Retesting?
- Retesting is testing the same functionality on same build with config changes or
different build or version of the application with code changes or defect fixes.
- Retesting is usually done to verify defect fixes.
9. What is the difference between Regression Testing and Retesting?
a) Retesting is carried out to verify defect fix / fixes. Regression testing is done to check
if the defect fix / fixes have not impacted other functionality of the application that was
working fine before applying the code changes.
b) Retesting is planned based for the defect fixes listed in Build Notes. Regression
testing is generic and may not be always specific to any defect fix or code change and
can be planned as regional or full regression testing.
c) Retesting involves executing test cases that were failed earlier and regression testing
involves executing test cases that were passed earlier build i.e., functionality that was
working in earlier builds.
d) Retesting will involve rerunning failed test cases that are associated with defect(s)
, fixes being verified. Regression testing does not involve verifying defect fix but only
executing regression test cases.
e) Retesting always takes higher priority over Regression testing i.e., Regression testing
is done after completing Retesting. In some projects where there are ample testing
resources, Regression testing is carried out in parallel with retesting.
f) Though Retesting and regression testing have different objectives and priorities, they
equally important for project's success.
What are the different types of software testing? Explain them briefly.
Below is an exhaustive list of "types of software testing" and a brief description about
each type of software testing, like load testing, stress testing, unit testing, system
testing, acceptance testing, certification testing, performance testing, user acceptance
testing, penetration testing, automated testing, beta testing, compatibility testing,
security testing, benchmark testing, functional testing, negative testing, destructive
testing, integration testing, regression testing, alpha testing, end-to-end testing, path
testing, smoke testing, black box testing, stability testing, usability testing etc., and
many more, about 100 software testing types with descriptions are listed below.
Why there are so many types of software testing?
Quality of software is assessed in terms of 6 Quality factors (Functionality, Reliability,
Efficiency, Usability, Maintainability and Portability). Each of below listed type of
software testing is designed to validate software for one or more of the mentioned
quality factors. More types of software testing have evolved to keep up with the pace
with rapid increase in complexity of the software design, frameworks & Programming
languages, increased number of users with popularity of internet, advent of new
platforms and technologies. With increase in number of software testing types to be
performed, need for software testing tools has increased as well.
http://www.softwaretestingsoftware.com/all-types-of-software-testing/
Software testing is an investigation conducted to provide stakeholders with information
about the quality of the product or service under test.[1] Software testing can also
provide an objective, independent view of the software to allow the business to
appreciate and understand the risks of software implementation. Test techniques
include, but are not limited to, the process of executing a program or application with the
intent of finding software bugs (errors or other defects).
Software testing can be stated as the process of validating and verifying that a
computer program/application/product:
meets the requirements that guided its design and development,
works as expected,
can be implemented with the same characteristics,
and satisfies the needs of stakeholders.
and Correct Answers. 100% 2024, Update.
What is Software engineering?
Software engineering is a systematic approach to the analysis, design, implementation
and maintenance of software.
What is test case?
- Test Case is a software engineering terminology
- Test Cases are also referred to as Test Scripts
- Collection of related test cases are referred to as Test Suite. e.g. regression test suite.
- Test Case contains a set of test steps and expected results
- Test Cases based on requirements. Test Cases can be written for Use cases also.
- Test Cases are usually documented and can be documented in word or excel or Test
management tools like HP Quality Center
- Test Case template usually contains below information
* Importance of the Test Case (High / Medium / Low)
* Complexity of the Test Case (High / Medium / Low)
* Test Case author
* Test Case reviewer
* Requirements covered by Test Case
* Test Case ID
* Test Case description
* Test steps and expected result for each step
* Actual result for each of the expected result
* Automated or Manual Test Case
* Test Case result (Pass or Fail)
* Comments / Remarks
What is the difference between Error, Bug and Defect ?
...
Why is V model called as V Model?
V Model is presented in V shape instead of being straight or linear like Waterfall model.
Name of the model has come because of the V Shape, similarly there are other models
that are named of their shape like Spiral model.
What is DFD (Data Flow Diagram)?
- DFD stands for Data flow diagram
- DFDs are used during Analysis and design phase of SDLC (Software Development
Life Cycle)
- DFDs are used for visualization of data flow and data processing in a information
system.
- DFD will show inputs, outputs, processing and where data will be stored.
- DFD will show communication or interaction between the system and external actors.
- Context-level DFD or 0 Level DFD is a diagram which is a highest level of view of the
,system.
- Context-level DFD indicates actors outside system interacting with the system.
What is Flow Chart?
A flowchart is a type of diagram that represents an algorithm or process, showing the
steps as boxes of various kinds, and their order by connecting these with arrows. This
diagrammatic representation can give a step-by-step solution to a given problem.
Process operations are represented in these boxes, and arrows connecting them
represent flow of control. Data flows are not typically represented in a flowchart, in
contrast with data flow diagrams; rather, they are implied by the sequencing of
operations. Flowcharts are used in analyzing, designing, documenting or managing a
process or program in various fields.
What is Regression Testing?
Regression testing is any type of software testing that seeks to uncover new software
bugs, or regressions, in existing functional and non-functional areas of a system after
changes, such as enhancements, patches or configuration changes, have been made
to them.
The intent of regression testing is to ensure that a change such as those mentioned
above has not introduced new faults.[1] One of the main reasons for regression testing
is to determine whether a change in one part of the software affects other parts of the
software.[2]
Common methods of regression testing include rerunning previously-completed tests
and checking whether program behavior has changed and whether previously-fixed
faults have re-emerged. Regression testing can be used to test a system efficiently by
systematically selecting the appropriate minimum set of tests needed to adequately
cover a particular change.
What is Retesting?
- Retesting is testing the same functionality on same build with config changes or
different build or version of the application with code changes or defect fixes.
- Retesting is usually done to verify defect fixes.
9. What is the difference between Regression Testing and Retesting?
a) Retesting is carried out to verify defect fix / fixes. Regression testing is done to check
if the defect fix / fixes have not impacted other functionality of the application that was
working fine before applying the code changes.
b) Retesting is planned based for the defect fixes listed in Build Notes. Regression
testing is generic and may not be always specific to any defect fix or code change and
can be planned as regional or full regression testing.
c) Retesting involves executing test cases that were failed earlier and regression testing
involves executing test cases that were passed earlier build i.e., functionality that was
working in earlier builds.
d) Retesting will involve rerunning failed test cases that are associated with defect(s)
, fixes being verified. Regression testing does not involve verifying defect fix but only
executing regression test cases.
e) Retesting always takes higher priority over Regression testing i.e., Regression testing
is done after completing Retesting. In some projects where there are ample testing
resources, Regression testing is carried out in parallel with retesting.
f) Though Retesting and regression testing have different objectives and priorities, they
equally important for project's success.
What are the different types of software testing? Explain them briefly.
Below is an exhaustive list of "types of software testing" and a brief description about
each type of software testing, like load testing, stress testing, unit testing, system
testing, acceptance testing, certification testing, performance testing, user acceptance
testing, penetration testing, automated testing, beta testing, compatibility testing,
security testing, benchmark testing, functional testing, negative testing, destructive
testing, integration testing, regression testing, alpha testing, end-to-end testing, path
testing, smoke testing, black box testing, stability testing, usability testing etc., and
many more, about 100 software testing types with descriptions are listed below.
Why there are so many types of software testing?
Quality of software is assessed in terms of 6 Quality factors (Functionality, Reliability,
Efficiency, Usability, Maintainability and Portability). Each of below listed type of
software testing is designed to validate software for one or more of the mentioned
quality factors. More types of software testing have evolved to keep up with the pace
with rapid increase in complexity of the software design, frameworks & Programming
languages, increased number of users with popularity of internet, advent of new
platforms and technologies. With increase in number of software testing types to be
performed, need for software testing tools has increased as well.
http://www.softwaretestingsoftware.com/all-types-of-software-testing/
Software testing is an investigation conducted to provide stakeholders with information
about the quality of the product or service under test.[1] Software testing can also
provide an objective, independent view of the software to allow the business to
appreciate and understand the risks of software implementation. Test techniques
include, but are not limited to, the process of executing a program or application with the
intent of finding software bugs (errors or other defects).
Software testing can be stated as the process of validating and verifying that a
computer program/application/product:
meets the requirements that guided its design and development,
works as expected,
can be implemented with the same characteristics,
and satisfies the needs of stakeholders.
