Analytical and Empirical Testing

Analytical testing compare results to mathematical solutions for simple cases.
Empirical testing compare results to experimental data. It is important that high-quality data be used as the basis for comparison along with complete and accurate information for developing a simulation
model that represents the test building or module as closely as possible.

Black Box Testing

In black box testing we check the functionality of the software using different inputs. Internal coding of the software is not tested. The test designer selects valid and invalid input and determines the correct output. There is no knowledge of the test object's internal structure. The implementation details of the components are not known (or, at least, are ignored), and only externally observable behavior or functionality is tested. This method of test design is applicable to all levels of software testing: unit, integration, functional testing, system and acceptance.
Black box testing is sometimes also called as "Opaque Testing", "Functional/Behavioral Testing" and "Closed Box Testing".

White Box Testing

In white box testing the emphasis is on coding. We execute and check each line of code atleast once to verify if it works fine without errors. Includes techniques such as Branch Testing and Path Testing.
Also known as Structural Testing , Glass Box Testing, or clear box testing.

Integration Testing

In this the units or modules are combined and tested as a group.
Modules are typically code modules, individual applications, client and server applications on a network, etc. Integration Testing follows unit testing and precedes system testing. There are two ways integration is performed. It is called Pre-test and Pro-test.
1) Pre-test:
The testing performed in Module development area is called Pre-test. The Pre-test is required only if the development is done in module development area.
2) Pro-test:
The Integration testing performed in baseline is called pro-test. The development of a release will be scheduled such that the customer can break down into smaller internal releases.

Usability Testing

Usability means that systems are easy and fast to learn, efficient to use, easy to remember, cause no operating errors and offer a high degree of satisfaction for the user. Usability means bringing the usage perspective into focus, the side towards the user. In short, we check how user friendly the software is. Software should be easy to understand. For example, checking the text alignment, font size, colors, etc). It is also called user interface testing, friendliness testing.

Security Testing

If your site requires firewalls, encryption, user authentication, financial transactions, or access to databases with sensitive data, you may need to test these and also test your site's overall protection against unauthorized internal or external access.

User Acceptance Testing

Testing to verify that the product meets customer specified requirements. A customer usually does this type of testing on a product that is developed externally. There are 2 types of user acceptance testing:-
1) Alpha Testing :
End-user i.e., client or 3rd party person on beahlf of the client does this type of testing. It is not done by programmers or testers. Testing of an application when development is nearing completion minor design changes may still be made as a result of such testing. In this, the client or 3rd party person tests the software before completion at our site (where software is developed).
2) Beta Testing :
When the Client tests the software at their own site or company it s called beta testing.