1.

Differentiate between verification and validation

Verification Validation

It includes checking documents, It includes testing and validating the

design, codes and programs. actual product.

Verification is the static testing. Validation is the dynamic testing.

It does not include the execution of

the code. It includes the execution of the code.

Methods used in verification are Methods used in validation are Black

reviews, walkthroughs, inspections Box Testing, White Box Testing and
and desk-checking. non-functional testing.

It checks whether the software meets

It checks whether the software the requirements and expectations of
conforms to specifications or not. a customer or not.

It can only find the bugs that could

It can find the bugs in the early stage not be found by the verification
of the development. process.

2. Differentiate between defect testing and validation testing

3. Explain Any 5 inspection checks

A software inspection checklist is a list of items that are

reviewed during a software inspection.
1. Code readability: Is the code easy to read and
understand? Are variable and function names meaningful
and consistent?
2. Code maintainability: Is the code easy to maintain? Are
there areas where the code could be refactored to make it
more maintainable?
3. Code efficiency: Is the code efficient? Are there areas
where the code could be optimized to improve
performance?
4. Code functionality: Does the code meet the requirements
of the project? Are there any defects or bugs in the code?
5. Code security: Is the code secure? Are there any potential
security vulnerabilities in the code?
6. Code commenting: Are there comments in the code? Are
the comments meaningful and useful?

4. Explain the 4 types of testing

Unit Testing
During this first round of testing, the program is
submitted to assessments that focus on specific
units or components of the software to
determine whether each one is fully functional.
The main aim of this endeavor is to determine
whether the application functions as designed.

Integration Testing

Integration testing allows individuals the

opportunity to combine all of the units within a
program and test them as a group. This testing
level is designed to find interface defects between
the modules/functions.

System Testing

System testing is the first level in which the

complete application is tested as a whole. The
goal at this level is to evaluate whether the system
has complied with all of the outlined requirements
and to see that it meets Quality Standards.

Acceptance Testing

The final level, Acceptance testing (or User

Acceptance Testing), is conducted to determine
whether the system is ready for release.
5. Different approaches towards integration testing
1.Big-Bang Integration Testing – It is the simplest integration testing
approach, where all the modules are combined and the functionality is
verified after the completion of individual module testing.
2. Bottom-Up Integration Testing – In bottom-up testing, each module at
lower levels is tested with higher modules until all modules are tested.
3. Top-Down Integration Testing – Top-down integration testing technique
is used in order to simulate the behaviour of the lower-level modules that are
not yet integrated. In this integration testing, testing takes place from top to
bottom.
4. Sandwich Integration Testing – A sandwich integration testing is also
called mixed integration testing. A sandwich integration testing follows a
combination of top down and bottom-up testing approaches. In top-down
approach, testing can start only after the top-level module have been coded
and unit tested. In bottom-up approach, testing can start only after the
bottom level modules are ready

6. Short note on component testing

Component Testing is a type of software testing in which

usability of each individual component is tested.

Along with the usability test, behavioral evaluation is also done

for each individual component.

To perform this type of testing, each component needs to be in

independent state and also should be in controllable state.

Each component of the software should be user

comprehensible.

Component testing is also referred to as Unit testing,Program

testing or Module testing.

7. Explain partition testing

Equivalence Partitioning Method is also known as
Equivalence class partitioning (ECP). It is a software
testing technique or black-box testing that divides input
domain into classes of data, and with the help of these
classes of data, test cases can be derived. An ideal test
case identifies class of error that might require many
arbitrary test cases to be executed before general error is
observed.
In equivalence partitioning, equivalence classes are
evaluated for given input conditions. Whenever any input is
given, then type of input condition is checked, then for this
input conditions, Equivalence class represents or describes
set of valid or invalid states.
8. Explain path testing
Path Testing is a method that is used to design the test
cases.
In path testing method, the control flow graph of a program
is designed to find a set of linearly independent paths of
execution.
In this method Cyclomatic Complexity is used to determine
the number of linearly independent paths and then test
cases are generated for each path.
It give complete branch coverage but achieves that without
covering all possible paths of the control flow graph.
McCabe’s Cyclomatic Complexity is used in path testing.
It is a structural testing method that uses the source code
of a program to find every possible executable path.
9. Advantages and disadvantages of automated testing
Automated Testing has the following advantages:
Automated testing improves the coverage of testing as automated
execution of test cases is faster than manual execution.

Automated testing has less chances of error hence more reliable.

As with automated testing test engineers have free time and can focus on
other creative tasks.
Automated Testing has the following disadvantages:
Automated testing is very much expensive than the manual testing.

It has limited to some organisations as many organisations not prefer test

automation.

Automated testing would also require additionally trained and skilled

people.