Dynamic Testing

  Dynamic Testing: 

 It is a process of checking if the source code and the application are working as expected. Also called  dynamic testing or validation testing.

* Levels of dynamic Testing: dynamic testing will be carried out at 4 levels.

1) Unit Testing

2) Integration Testing

3) System Testing

4) User Acceptance Testing.

Unit Testing:  A smallest separatable portion in the source code of the application is called unit.
(functions, procedures, etc) Testing conducted on these units to check if the code behind the units
is working as expected or not is called unit testing.

 It is also called module testing or component testing

Integration Testing:  Once all units are tested the programmers will integrate all units and check interactions among the units which is called integration testing.

Note: Unit testing and Integration testing is collectively called white box testing.

White box Testing: Testing conducted on the source code by developers to check does the  source code is working as expected or not is called white box testing.

* What is the need of white box testing?

As the source code is visible, finding and rectifying the problems is easy for developers.The defects that are identified in white box testing are very economical to resolve. To reduce the defects as early as possible white box testing is helpful.
To ensure 100% code coverage.

***** White box testing is also called as glass box, structural, clear box testing.

Black box Testing:  Testing is conducted on the application by test engineers or by domain
experts to check whether the application is working according to customer requirements.

What is the need of Black Box Testing?

1) White box testing conducted by developer in a technical perception where as black box
testing is conducted by test engineers with end-user perception.

2) Programmers will conduct white box testing in a positive perception whereas tester will
conduct black box testing with a negative perception where there is a more chance of
finding more defects

The more defects you identify results in a quality system.

3) White box testing will not cover non functional areas. As functional requirements are
also very important for production system those are covered in black box testing.

4) The objective of white box testing is 100% coverage whereas the objective of black box
testing is 100% customer business requirement coverage.

5) Black Box Testing = System Testing + User Accepting Testing which is called as
requirement Based Testing (or) Specification Based Testing.

System Testing:  Validating the functional and non functional requirements of the system is
called system testing.

System testing broadly classified into two types i.e.

1) Functional system testing.

2) Non-functional system testing.

Functional system testing will be conducted both in a positive perception and also in a negative
perception.

Positive Testing (+ve ):  Testing conducted on the application in a positive approach to
determine what system suppose to do is called positive testing.

***Note :
Positive testing is helpful to check whether the customer requirements are justifying b y
the application or not.

Negative Testing (-ve): Testing a software application with a negative perception to check
what system not supposed to do is called negative testing.

***Note :
Negative testing is helpful to find defects from the software.