Software Testing-Testing Types Interview Questions
Printed From: One Stop Testing
Category: Software Testing @ OneStopTesting
Forum Name: Beginners @ OneStopTesting
Forum Discription: New to the Club...!!! Don't Worry, We are here for you...!!! Learn the very basics of Software Testing and other pertinent Informations.
URL: http://forum.onestoptesting.com/forum_posts.asp?TID=3363
Printed Date: 07Sep2025 at 11:06pm
Topic: Software Testing-Testing Types Interview Questions
Posted By: tanushree
Subject: Software Testing-Testing Types Interview Questions
Date Posted: 27Oct2007 at 5:48am
1.What testing approaches do you know in Software Testing?
A: Each of the followings represents a different testing approach:
1. Black box testing
2. White box testing
3. Unit testing
4. Incremental testing
5. Integration testing
6. Functional testing
7. System testing
8. End-to-end testing
9. Sanity testing
10. Regression testing
11. Acceptance testing
12. Load testing
13. Performance testing
14. Usability testing
15. Install/uninstall testing
16. Recovery testing
17. Security testing
18. Compatibility testing
19. Exploratory testing
20. Ad-hoc testing
21. User acceptance testing
22. Comparison testing
23. Alpha testing
24. Beta testing
25. Mutation testing.
2. What is glass box testing in Software Testing?
A: Glass
box testing is the same as white box testing. It is a testing approach
that examines the application's program structure, and derives test
cases from the application's program logic.
3. What is open box testing in Software Testing?
A: Open
box testing is same as white box testing. It is a testing approach that
examines the application's program structure, and derives test cases
from the application's program logic.
4.What is black box testing in Software Testing?
A: Black
box testing a type of testing that considers only externally visible
behavior. Black box testing considers neither the code itself, nor the
"inner workings" of the software. You CAN learn to do black box
testing, with little or no outside help. Get CAN get free information.
Click on a link!
5. What is unit testing in Software Testing?
A: Unit
testing is the first level of dynamic testing and is first the
responsibility of developers and then that of the test engineers. Unit
testing is performed after the expected test results are met or
differences are explainable/acceptable.
6. What is system testing in Software Testing?
A: System
testing is black box testing, performed by the Test Team, and at the
start of the system testing the complete system is configured in a
controlled environment. The purpose of system testing is to validate an
application's accuracy and completeness in performing the functions as
designed. System testing simulates real life scenarios that occur in a
"simulated real life" test environment and test all functions of the
system that are required in real life. System testing is deemed
complete when actual results and expected results are either in line or
differences are explainable or acceptable, based on client input. Upon
completion of integration testing, system testing is started. Before
system testing, all unit and integration test results are reviewed by
Software QA to ensure all problems have been resolved. For a higher
level of testing it is important to understand unresolved problems that
originate at unit and integration test levels.
7. What is parallel/audit testing in Software Testing?
A:
Parallel/audit testing is testing where the user reconciles the output
of the new system to the output of the current system to verify the new
system performs the operations correctly.
8. What is functional testing in Software Testing?
A:
Functional testing is black-box type of testing geared to functional
requirements of an application. Test engineers *should* perform
functional testing.
9. What is usability testing in Software Testing?
A:
Usability testing is testing for 'user-friendliness'. Clearly this is
subjective and depends on the targeted end-user or customer. User
interviews, surveys, video recording of user sessions and other
techniques can be used. Programmers and developers are usually not
appropriate as usability testers.
10. What is integration testing in Software Testing?
A:
Upon completion of unit testing, integration testing begins.
Integration testing is black box testing. The purpose of integration
testing is to ensure distinct components of the application still work
in accordance to customer requirements. Test cases are developed with
the express purpose of exercising the interfaces between the
components. This activity is carried out by the test team.
Integration testing is considered complete, when actual results and
expected results are either in line or differences are
explainable/acceptable based on client input.
11. What is end-to-end testing in Software Testing?
A:
Similar to system testing, the *macro* end of the test scale is testing
a complete application in a situation that mimics real world use, such
as interacting with a database, using network communication, or
interacting with other hardware, application, or system.
12. What is regression testing in Software Testing?
A: The
objective of regression testing is to ensure the software remains
intact. A baseline set of data and scripts is maintained and executed
to verify changes introduced during the release have not "undone" any
previous code. Expected results from the baseline are compared to
results of the software under test. All discrepancies are highlighted
and accounted for, before testing proceeds to the next level.
13. What is sanity testing in Software Testing?
A: Sanity
testing is performed whenever cursory testing is sufficient to prove
the application is functioning according to specifications. This level
of testing is a subset of regression testing. It normally includes a
set of core tests of basic GUI functionality to demonstrate
connectivity to the database, application servers, printers, etc.
14. What is performance testing in Software Testing?
A:
Although performance testing is described as a part of system testing,
it can be regarded as a distinct level of testing. Performance testing
verifies loads, volumes and response times, as defined by requirements.
15. What is load testing in Software Testing?
A: Load
testing is testing an application under heavy loads, such as the
testing of a web site under a range of loads to determine at what point
the system response time will degrade or fail.
16. What is installation testing in Software Testing?
A:
Installation testing is testing full, partial, upgrade, or
install/uninstall processes. The installation test for a release is
conducted with the objective of demonstrating production readiness.
This test includes the inventory of configuration items, performed by
the application's System Administration, the evaluation of data
readiness, and dynamic tests focused on basic system functionality.
When necessary, a sanity test is performed, following installation
testing.
17. What is security/penetration testing in Software Testing?
A: Security/penetration testing is testing how well the system is
protected against unauthorized internal or external access, or willful
damage. This type of testing usually requires sophisticated testing
techniques.
18. What is recovery/error testing in Software Testing?
A:
Recovery/error testing is testing how well a system recovers from
crashes, hardware failures, or other catastrophic problems.
19. What is compatibility testing in Software Testing?
A:
Compatibility testing is testing how well software performs in a
particular hardware, software, operating system, or network
environment.
20. What is comparison testing?
A: Comparison testing is testing that compares software weaknesses and strengths to those of competitors' products.
21. What is acceptance testing in Software Testing?
A:
Acceptance testing is black box testing that gives the
client/customer/project manager the opportunity to verify the system
functionality and usability prior to the system being released to
production. The acceptance test is the responsibility of the
client/customer or project manager, however, it is conducted with the
full support of the project team. The test team also works with the
client/customer/project manager to develop the acceptance criteria.
22. What is alpha testing in Software Testing?
A: Alpha
testing is testing of an application when development is nearing
completion. Minor design changes can still be made as a result of alpha
testing. Alpha testing is typically performed by a group that is
independent of the design team, but still within the company, e.g.
in-house software test engineers, or software QA engineers.
23. What is beta testing in Software Testing?
A: Beta
testing is testing an application when development and testing are
essentially completed and final bugs and problems need to be found
before the final release. Beta testing is typically performed by
end-users or others, not programmers, software engineers, or test
engineers
24. What is stress testing in Software Testing?
A: Stress
testing is testing that investigates the behavior of software (and
hardware) under extraordinary operating conditions. For example, when a
web server is stress tested, testing aims to find out how many users
can be on-line, at the same time, without crashing the server. Stress
testing tests the stability of a given system or entity. It tests
something beyond its normal operational capacity, in order to observe
any negative results. For example, a web server is stress tested, using
scripts, bots, and various denial of service tools.
25. What is load testing in Software Testing?
A: Load
testing simulates the expected usage of a software program, by
simulating multiple users that access the program's services
concurrently. Load testing is most useful and most relevant for
multi-user systems, client/server models, including web servers. For
example, the load placed on the system is increased above normal usage
patterns, in order to test the system's response at peak loads.
26. What is the difference between performance testing and load testing in Software Testing?
A: Load testing is a blanket term that is used in many different ways
across the professional software testing community. The term, load
testing, is often used synonymously with stress testing, performance
testing, reliability testing, and volume testing. Load testing
generally stops short of stress testing. During stress testing, the
load is so great that errors are the expected results, though there is
gray area in between stress testing and load testing.
27. What is the difference between reliability testing and load testing in Software Testing?
A: Load testing is a blanket term that is used in many different ways
across the professional software testing community. The term, load
testing, is often used synonymously with stress testing, performance
testing, reliability testing, and volume testing. Load testing
generally stops short of stress testing. During stress testing, the
load is so great that errors are the expected results, though there is
gray area in between stress testing and load testing.
28. What is the difference between volume testing and load testing in Software Testing?
A: Load testing is a blanket term that is used in many different ways
across the professional software testing community. The term, load
testing, is often used synonymously with stress testing, performance
testing, reliability testing, and volume testing. Load testing
generally stops short of stress testing. During stress testing, the
load is so great that errors are the expected results, though there is
gray area in between stress testing and load testing.
29. What is incremental testing in Software Testing?
A:
Incremental testing is partial testing of an incomplete product. The
goal of incremental testing is to provide an early feedback to software
developers.
30. What is software testing?
A: Software testing is a
process that identifies the correctness, completenes, and quality of
software. Actually, testing cannot establish the correctness of
software. It can find defects, but cannot prove there are no defects.
31. What is automated testing in Software Testing?
A: Automated testing is a formally specified and controlled method of formal testing approach.
32. What is alpha testing in Software Testing?
A: Alpha
testing is final testing before the software is released to the general
public. First, (and this is called 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. Then, (and this is called second stage of alpha testing), the
software is handed over to us, the software QA staff, for additional
testing in an environment that is similar to the intended use.
33. What is beta testing in Software Testing?
A: Following
alpha testing, "beta versions" of the software are released to a group
of people, and limited public tests are performed, so that further
testing can ensure the product has few bugs. Other times, beta versions
are made available to the general public, in order to receive as much
feedback as possible. The goal is to benefit the maximum number of
future users.
34. What is the difference between alpha and beta testing in Software Testing?
A: Alpha testing is performed by in-house developers and software QA
personnel. Beta testing is performed by the public, a few select
prospective customers, or the general public.
35. What is clear box testing in Software Testing?
A:
Clear box testing is the same as white box testing. It is a testing
approach that examines the application's program structure, and derives
test cases from the application's program logic. You CAN learn clear
box testing, with little or no outside help.
36. What is boundary value analysis in Software Testing?
A: Boundary value analysis is a technique for test data selection. A
test engineer chooses values that lie along data extremes. Boundary
values include maximum, minimum, just inside boundaries, just outside
boundaries, typical values, and error values. The expectation is that,
if a systems works correctly for these extreme or special values, then
it will work correctly for all values in between. An effective way to
test code, is to exercise it at its natural boundaries.
37. What is ad hoc testing in Software Testing?
A: Ad hoc testing is a testing approach; it is the least formal testing approach.
38. What is gamma testing in Software Testing?
A: Gamma
testing is testing of software that has all the required features, but
it did not go through all the in-house quality checks. Cynics tend to
refer to software releases as "gamma testing".
39. What is functional testing in Software Testing?
A:
Functional testing is same as black box testing. Black box testing a
type of testing that considers only externally visible behavior. Black
box testing considers neither the code itself, nor the "inner workings"
of the software.
40. What is closed box testing in Software Testing?
A:
Closed box testing is same as black box testing. Black box testing a
type of testing that considers only externally visible behavior. Black
box testing considers neither the code itself, nor the "inner workings"
of the software.
41. What is bottom-up testing in Software Testing?
A:
Bottom-up testing is a technique for integration testing. A test
engineer creates and uses test drivers for components that have not yet
been developed, because, with bottom-up testing, low-level components
are tested first. The objective of bottom-up testing is to call
low-level components first, for testing purposes.
42. How do you perform integration testing in Software Testing?
A: First, unit testing has to be completed. Upon completion of unit
testing, integration testing begins. Integration testing is black box
testing. The purpose of integration testing is to ensure distinct
components of the application still work in accordance to customer
requirements. Test cases are developed with the express purpose of
exercising the interfaces between the components. This activity is
carried out by the test team. Integration testing is considered
complete, when actual results and expected results are either in line
or differences are explainable/acceptable based on client input.
43. What is integration testing? in Software Testing
A:
Integration testing is black box testing. The purpose of integration
testing is to ensure distinct components of the application still work
in accordance to customer requirements. Test cases are developed with
the express purpose of exercising the interfaces between the
components. This activity is carried out by the test team. Integration
testing is considered complete, when actual results and expected
results are either in line or differences are explainable/
44. When do you choose automated testing in Software Testing?
A: For larger projects, or ongoing long-term projects, automated
testing can be valuable. But for small projects, the time needed to
learn and implement the automated testing tools is usually not
worthwhile. Automated testing tools sometimes do not make testing
easier. One problem with automated testing tools is that if there are
continual changes to the product being tested, the recordings have to
be changed so often, that it becomes a very time-consuming task to
continuously update the scripts. Another problem with such tools is the
interpretation of the results (screens, data, logs, etc.) that can be a
time-consuming task. You can learn to use automated tools, with little
or no outside help.
45. What is the difference between system testing and integration testing in Software Testing?
A: System testing is high level testing, and integration testing is a
lower level testing. Integration testing is completed first, not the
system testing. In other words, upon completion of integration testing,
system testing is started, and not vice versa. For integration testing,
test cases are developed with the express purpose of exercising the
interfaces between the components. For system testing, on the other
hand, the complete system is configured in a controlled environment,
and test cases are developed to simulate real life scenarios that occur
in a simulated real life test environment. The purpose of integration
testing in Software Testing is to ensure distinct components of the
application still work in accordance to customer requirements. The
purpose of system testing, on the other hand, is to validate an
application's accuracy and completeness in performing the functions as
designed, and to test all functions of the system that are required in
real life.
46. What are the parameters of performance testing in Software Testing?
A: The term 'performance testing' is often used synonymously with
stress testing, load testing, reliability testing, and volume testing.
Performance testing is a part of system testing, but it is also a
distinct level of testing. Performance testing verifies loads, volumes,
and response times, as defined by requirements.
47. What is disaster recovery testing in Software Testing?
A: Disaster recovery testing is testing how well the system recovers
from disasters, crashes, hardware failures, or other catastrophic
problems
48. Which of the tools should learn?
A:Learn the most
popular software tools (i.e. LabView, LoadRunner, Rational Tools,
Winrunner, etc.) -- and you want to pay special attention to LoadRunner
and the Rational Toolset.
49.What is the objective of regression testing in Software Testing?
A: The objective of regression testing is to test that the fixes have
not created any other problems elsewhere. In other words, the objective
is to ensure the software has remained intact. A baseline set of data
and scripts are maintained and executed, to verify that changes
introduced during the release have not "undone" any previous code.
Expected results from the baseline are compared to results of the
software under test. All discrepancies are highlighted and accounted
for, before testing proceeds to the next level.
50.Is the regression testing performed manually in Software Testing?
A: It depends on the initial testing approach. If the initial testing
approach is manual testing, then, usually the regression testing is
performed manually. Conversely, if the initial testing approach is
automated testing, then, usually the regression testing is performed by
automated testing.
< ="text/">
< ="text/" ="http://pagead2.googlesyndication.com/pagead/show_ads.js">
< ="text/">
< ="text/" ="http://pagead2.googlesyndication.com/pagead/show_ads.js">
< ="text/">
< ="text/" ="http://pagead2.googlesyndication.com/pagead/show_ads.js">
< ="text/">
< ="text/" ="http://pagead2.googlesyndication.com/pagead/show_ads.js">
< ="text/">
< ="text/" ="http://pagead2.googlesyndication.com/pagead/show_ads.js">
|
|