Professional Documents
Culture Documents
(CO5I-A / CO5I-B)
Unit1:-
1. What is software testing?
ANS:- Software testing is a process, to evaluate the functionality of a
software application with an intent to find whether the developed
software met the specified requirements or not and to identify the
defects to ensure that the product is defect-free in order to produce a
quality product.
ANS:-
4. Write difference between white box testing and black box testing.
ANS:-Black box testing and White box testing.
Implementation expertise is required. It is not necessary to have any prior experience with
implementation.
ANS:-
6. Explain V Model
ANS:- V Model is a highly disciplined SDLC model which has a testing
phase parallel to each development phase. The V model is an extension of
the waterfall model wherein software development and testing is
executed in a sequential way. It is known as the Validation or Verification
Model.
SDLC: SDLC is Software Development Life Cycle. It is the sequence of
activities carried out by Developers to design and develop high-quality
software.
ANS:- Inception: This is the first phase of the requirements analysis process. This
phase gives an outline of how to get started on a project. In the inception phase, all
the basic questions are asked on how to go about a task or the steps required to
accomplish a task. A basic understanding of the problem is gained and the nature of
this phase is the foundation as to what has to be done further. Overall in the
engineers:
Whenever we do the testing by boundary value analysis, the tester focuses on,
while entering boundary value whether the software is producing correct
output or not.
Boundary values are those that contain the upper and lower limit of a variable.
Assume that, age is a variable of any function, and its minimum value is 18
and the maximum value is 30, both 18 and 30 will be considered as boundary
values.
The basic assumption of boundary value analysis is, the test cases that are
created using boundary values are most likely to cause an error.
There is 18 and 30 are the boundary values that's why tester pays more
attention to these values, but this doesn't mean that the middle values like 19,
20, 21, 27, 29 are ignored. Test cases are developed for each and every value
of the range.
Unit 2:-
1. Explain top down integration process
ANS:- Top down Integration testing is a part of incremental approach, in which the
testing is done by joining two or more modules that are logically related. This process
is usually carried out by using dummy programs called, Stubs and drivers and is used
in order to stimulate the behaviour of the lower level modules that are not yet
integrated.
In the top-down integration testing, if breadth-first approach is adopted,
then we will integrate module M1 first, then M2, M6. Then we will
integrate module M3, M4, M5, and at last M7.
Advantages OF Top Down Integration Testing
The basic functionality of the software is tested at the end of the cycle.
ANS:-
Advantages:
1. This approach is useful is useful for very large projects having several
projects. When development follows a spiral model and module itself is as
large as a system.
2. Both top down and bottom up approach starts at the start of the schedule.
3. It needs more resources and big teams for performing both, methods of
testing at a time or one after the other.
Disadvantages:
Component Testing: One need to define the approach and test plan for
testing client and server individually. When server is tested there is need of
a client simulator, whereas testing client a server simulator, and to test
network both simulators are used at a time.
Integration testing: After successful testing of server, client and network,
they are brought together to form system testing.
Performance testing: System performance is tested when number of clients
is communicating with server at a time. Volume testing and stress testing
may be used for testing, to test under maximum load as well as normal load
expected. Various interactions may be used for stress testing.
Concurrency Testing: It is very important testing for client-server
architecture. It may be possible that multiple users may be accessing same
record at a time, and concurrency testing is required to understand the
behavior of a system in this situation.
Alpha testing involves both the Beta testing commonly uses black-
Alpha Testing Beta Testing
Alpha testing may require a long Beta testing requires only a few
execution cycle. weeks of execution.
Multiple test cycles are Only one or two test cycles are
organized in alpha testing. there in beta testing.
Unit 3:-
1. What is test plan?
ANS:- A test plan is a document that consists of all future testing-related
activities. It is prepared at the project level and in general, it defines
work products to be tested, how they will be tested, and test type
distribution among the testers. Before starting testing there will be a test
manager who will be preparing a test plan. In any company whenever a
new project is taken up before the tester involves in the testing the test
manager of the team would prepare a test Plan.
1. To determine the scope and the risks that need to be tested and that are
not to be tested.
2. Determine the strategy.
3. Making sure that the testing activities have been included.
4. Deciding Entry exit criteria.
5. Evaluating the test estimate.
6. Planning when and how to test and deciding how the test results will be
evaluated and defining
7. The test artifacts delivered as part of test execution.
8. Defining the management information, including the metrics required and
defect resolution and risks issues.
9. Ensuring that the test documentation generates repeatable test assets.