Assignment 2

Module 2:- Verification, Validation & V-Model

1. Explain the different Levels of Testing?

Ans:- Level of testing is basically during the creation of software to identify the defect at an
early stage. There are 4 level of testing Unit testing, Integration testing, system testing and
acceptance testing.

Level of testing:-

1. Unit Testing
Smallest piece of independent and executable code that can perform some
functionality is called as Unit.
This testing is done by developer to ensure that each unit is working properly.
Here each and every part of the code is tested.
This testing can done by two approaches. Developer test using white box testing
where as testing team test using black box testing.
It also called as Module testing or component testing.
For this testing we refer the low level design document.

2. Integration Testing
Since each piece or module is tested in unit testing and certified to be correct
doesn't mean an integration of the modules will be correct this is due to the fact
that intercommunication between each module's interfaces becomes important.
Integration testing test the interaction between module or component.
It is done between two similar units of two different module of same system.
This testing done by testing team
This test done by following approaches.
1. Top-down approach
In Top-down approach programmer will prepare dummy modules for the
bottom most module is called stub.
Stub is also called as Called program.
Test stub is a program that simulates the activity of missing subsystem
using fake data.
It check interaction between top most and bottom most module.

Example. In following diagram login, s/w testing & java module are developed.
Where as assign sub and quizzes module are not yet developed but for testing
programmer use dummy module which called stub.
2. Bottom-up
up approach
In Bottom-upup approach programmer will prepare dummy modules for the
top most modules is called driver.
Driver is also called as Calling program.
It check interaction between bottom most to top most module.
module
Functional issues will be identified at early stage, at unit testing.

Example. In following diagram only

only assign sub and quizzes module developed.
Where as login, s/w testing & java module are not yet developed but for testing
programmer use dummy module which called driver.

3. Big-bang
bang approach
In Big-Bang
Bang approach actual module is created & test without stub & driver
 Here the entire modules must be developed before testing.
Generally it is time-consuming and difficult to trace the cause of failures.
It also increases risk.

3. System Testing
Test for functional and non-functional requirements of the system.
Testing whole product in production environment.
This is the final phase of testing before release of software.
System testing done by testing team only.

4. Acceptance Testing
It is done by client by checking final product.
It is a formal activity.
Client will check whether requirement is getting fulfil or not?
User acceptance test (UAT) is done by end user by checking two form of UAT
UAT validates functional as well as non-functional requirement.
Alpha test:- Internally conducted in production environment. End-user of the
product checks the product. Developer observes and records error and usage
problems.
Beta test:- Externally conducted in live environment. It cannot be controlled by
developer. Application usage problems are reported to developer at regular interval.

2. Which are the different verification techniques?

Ans:- Verification is a process to evaluate work-product to check whether it fulfil
requirement phase. It is done by manually reading work-product. It is also called static
technique. There are three verification techniques which are:-

1. Walkthrough
Once documents prepared by Author the document checked by colleagues.
Colleagues observe the document and give the requirement feedback & suggestion
to the Author.
Author gives explanation if required, and takes down the necessary actions.
It is also called buddy testing.
It is informal meeting process.

2. Inspection
It is a semi-formal process & done by domain expert.
Here we compare product with RTM which is nothing but requirement traceability
matrix.
In RTM the requirement mapped with trace cases.
Inspection team involves:
Moderator:- Is the activity leader which co-ordinate with other member and assign
task to the team member.
Author:- who will submit the work-product.
 Inspector/reviewer:- Who is the domain expert. Inspector check document and
give required feedback & suggestion.
Reader:- who reads the document in meeting.
Recorder:-note down suggestion given by inspector

3. Review
It is a formal process.
Here final decision is made to baseline the document.
Freeze the document by project manager.

3. What is White box testing ? What is Black box testing ?

Ans:- White box testing:-

White box testing means inspecting and testing internal components in isolation from
the whole product.
Hence here logic will be check because here we are interested in what is happening
'inside the box'.
Here we require the knowledge of how the software is implemented, that is, how it
works. For example, a structural technique may be concerned with exercising loops in
the software. Hence, this testing is done by programmer.

We see the code. We can read it. We can infer what its supposed to do. We can
mentally execute it and identify possible issues.
The code is in a transparent box. Or a glass box. Hence, it is also called as glass
box testing.
It is also called structural testing.

Black box testing:-

Black box testing is testing from the outside of the product. I.e. Imagine the product is
a black box you can't look inside of. You can only interact with its user controls and
outputs. You use those to assess if the product works as expected.
 This is a box that takes some input and gives some output. We dont know whats
going on inside.
The tester is concentrating on what the software does, not how it does it.
Here only functionality of software is checked hence it is also called as functional
testing.
It is done as per input output specification which is nothing but SRS document.
Black box test design techniques:-

1. Equivalence Class Partitioning

Here we create partition for similar group i.e valid and invalid & test the group by
only one test case because behaviour of partition is same. Hence, not required to
test all data.
Possibility of getting is high because it does not cover boundary value.

2. Boundary Value Testing

Here we test boundary value between partitions both valid boundary partition and
invalid boundary partition.
A boundary value is an input or output value on the border of an equivalence
partition, includes minimum and maximum values at inside and outside
boundaries.

3. Error Guessing
Negative condition are check to break the code
It is done by experience person & knowledgeable person who has knowledge of
product
 4 What is the Difference between Static and Dynamic testing?
Ans:-

Static testing Dynamic Testing

1. Here testing is done without executing
the program.
2. It is about prevention of defects.
3. It gives assessments of documentation &
code.
4. It covers the structural and statement
coverage testing.
5. Cost of finding defects and fixing is less
6. Return on investment will be high as this
process involved at early stage.
7. More review, comments are highly
recommended for good quality.
8. Requires lots of meeting.
9. This testing does verification process.
10. Static testing techniques:
Walkthrough
Inspection
Review
1. Here testing is done by executing the
program.
2. It is about finding and fixing the defects.
3. It gives bugs in software system.
4. It covers executable file of the code.
5. Cost of finding and fixing defects is high
6. Return on investment will be low as this
process involved after the development
phase.
7. More defect are highly recommended for
good quality.
8. Comparatively requires lesser meetings.
9. This testing does validation process.
10. Dynamic testing techniques:-
Unit/component testing
Integration testing
System testing
Acceptance testing

5. What is Unit, Integration, System testing & Acceptance testing?

Ans:-

5. Unit Testing
Smallest piece of independent and executable code that can perform some
functionality is called as Unit.
This testing is done by developer to ensure that each unit is working properly.
Here each and every part of the code is tested.
This testing can done by two approaches. Developer test using white box testing
where as testing team test using black box testing.
It also called as Module testing or component testing.
For this testing we refer the low level design document.

6. Integration Testing
Since each piece or module is tested in unit testing and certified to be correct
doesn't mean an integration of the modules will be correct this is due to the fact
that intercommunication between each module's interfaces becomes important.
Integration testing test the interaction between module or component.
It is done between two similar units of two different module of same system.
This testing done by testing team
 Thiss test done by following approaches.
4. Top-down
down approach
In Top-down
down approach programmer will prepare dummy modules for the
bottom most module is called stub.
Stub is also called as Called program.
Test stub is a program that simulates the activity of missing
missin subsystem
using fake data.
It check interaction between top most and bottom most module.
module

Example. In following diagram login, s/w testing & java module are developed.
Where as assign sub and quizzes module are not yet developed but for testing
programmer use dummy module which called stub.

5. Bottom-up
up approach
In Bottom-upup approach programmer will prepare dummy modules for the
top most modules is called driver.
Driver is also called as Calling program.
It check interaction between bottom most to top most module.
module
Functional issues will be identified at early stage, at unit testing.

Example. In following diagram only assign sub and quizzes module developed.
Where as login, s/w testing & java module are not yet
yet developed but for testing
programmer use dummy module which called driver.

6. Big-bang
bang approach
In Big-Bang
Bang approach actual module is created & test without stub & driver
 Here the entire modules must be developed before testing.
Generally it is time-consuming
time and difficult to trace the cause of failures.
It also increases risk.

7. System Testing
Test for functional and non-functional
non functional requirements of the system.
Testing whole product in production environment.
This is the final phase of testing
testi before release of software.
System testing done by testing team only.

8. Acceptance Testing
It is done by client by checking final product.
product
It is a formal activity.
Client will check whether requirement is getting fulfil or not?
User acceptance test (UAT) is done by end user by checking two form of UAT
UAT validates functional as well as non-functional
non functional requirement.
Alpha test:- Internally
nternally conducted in production environment.
environment End-user of the
product checks the product. Developer observes and records error er and usage
problems.
Beta test:- Externally conducted in live environment. It cannot be controlled by
developer. Application usage problems are reported to developer at regular interval.