Software testing

6. Types of Testing
6.1Black box Testing
A method of software testing that verifies the functionality of an application without having specific knowledge of the application's code/internal structure. Tests are based on requirements and functionality.
It is performed by QA teams.

6.2 White box Testing
 Testing technique based on knowledge of the internal logic of an application’s code and includes tests
 Like coverage of code statements, branches, paths, conditions. It is performed by software developers.

6.3 Functional Testing
Type of black box testing that bases its test cases on the specifications of the software component under test. It is performed by testing teams.

6.4 Active Testing
 Type of testing consisting in introducing test data and analyzing the execution results. It is usually conducted by the testing teams.



6.5 Agile Testing
 Software testing practice that follows the principles of the agile manifesto, emphasizing testing from the
 perspective of customers who will utilize the system. It is usually performed by the QA teams.

6.6 Ad-hoc Testing
 Testing performed without planning and documentation - the tester tries to 'break' the system by
 randomly trying  the system's functionality. It is performed by the testing teams.

6.7 Alpha Testing
 Type of testing a software product or system conducted at the developer's site. Usually it is  performed
 by the end user.


6.8 Beta Testing
Final testing before releasing application for commercial purpose. It is typically done by end-users or others.

6.9 Acceptance Testing
Formal testing conducted to determine whether or not a system satisfies its acceptance criteria and to
 enable the customer to determine whether or not to accept the system. It is usually performed by the customer.

6.10 Big Bang Integration Testing
 Testing technique which integrates individual program modules only when everything is ready. It is performed by the testing teams.

6.11 Boundary Value Testing
 It is a technique to find whether the application is accepting the excepting range of values and rejecting
 the values which fall out of range.

6.12Compatibility Testing
 Testing technique that validates how well software performs in a particular hardware/software/operating system/network environment. It is performed by the testing teams.

6.13 Browser Compatibility Testing
Testing technique that validates how well a software performs in a particular browser.

6.14 Component Testing:
 Testing technique similar to unit testing but with a higher level of integration - testing is done in the
 context of the application instead of just directly testing a specific method. Can be performed by
testing or development teams.

6.15 Domain Testing:
White box testing technique which contains checking that the program accepts only valid input.
It is usually done by software development teams and occasionally by automation testing teams.

6.16 End-to-end Testing
 Similar to system testing, involves testing of a complete application environment in a situation that
mimics real-world use, such as interacting with a database, using network communications, or
 interacting with other hardware, applications, or systems if appropriate. It is performed by QA teams.

6.17 Endurance Testing
Type of testing which checks for memory leaks or other problem that may occur with prolonged
 execution. It is usually performed by QA Engineer.

6.18 Equivalence Partitioning Testing
 In this type of testing we divide the input into different types. And verify the application or software
 for a single  value among different types. If that single value is able to run the application then it is ok
 else there is a bug

6.19 Fuzz Testing
Software testing technique that provides invalid, unexpected, or random data to the inputs of a
 program - a special area of mutation testing. Fuzz testing is performed by testing teams.

6.20 GUI software Testing
 The process of testing a product that uses a graphical user interface, to ensure it meets its written specifications. This is normally done by the testing teams.

6.21Globalization Testing
 Testing method that checks proper functionality of the product with any of theculture/locale settings
 using every  type of international input possible. It is performed by the testing team(I5lam.com).

6.22 Integration Testing
 In integration testing the individual tested units are grouped as one and the interface between them is tested. Integration testing identifies the problems that occur when the individual units are combined i.e it detects the problem in interface of the two units. Integration testing is done after unit testing.
There are mainly three approaches to do integration testing.
Top down approach:
Top down approach tests the integration from top to bottom, it follows the architectural structure.
Example: Integration can start with GUI and the missing components will be substituted by stubs and integration will go on.
Bottom up approach testing:
In bottom up approach testing takes place from the bottom of the control flow, the higher level
components are substituted with drivers

6.23 Internationalization Testing
The process which ensures that product’s functionality is not broken and all the messages are properly externalized when used in different languages and locale. It is usually performed by the testing teams.

6.24 Localization Testing
 Part of software testing process focused on adapting a globalized application to a particular
 culture/locale. It is normally done by the testing teams.

6.25 Manual-Support Testing
 Testing technique that involves testing of all the functions performed by the people while preparing the data and using these data from automated system. It is conducted by testing teams.

6.26 Negative Testing
 Also known as "test to fail" - testing method where the tests' aim is showing that a component or system does not work. It is performed by manual or automation testers.

6.27 Parallel Testing
 Testing technique which has the purpose to ensure that a new application which has replaced its older version has been installed and is running correctly. It is conducted by the testing team.

6.28 Regression Testing
 Type of software testing that seeks to uncover software errors after changes to the program (e.g. bug
 fixes or new functionality) have been made, by retesting the program. It is performed by the testing
teams.

6.29 Requirements Testing
 Testing technique which validates that the requirements are correct, complete, unambiguous, and
 Logically  consistent and allows designing a necessary and sufficient set of test cases from those requirements. It is  performed by QA teams.

6.30 Sanity Testing
 Testing technique which determines if a new software version is performing well enough to accept it
for a major testing effort. It is performed by the testing teams.

6.31 Smoke Testing
 Testing technique which examines all the basic components of a software system to ensure that they
 work properly. Typically, smoke testing is conducted by the testing team, immediately after a software build is made .

6.34 Stress Testing
 Testing technique which evaluates a system or component at or beyond the limits of its specified requirements.  It is usually conducted by the performance engineer.

6.35 System Testing
 The process of testing an integrated hardware and software system to verify that the system meets its specified requirements. It is conducted by the testing teams in both development and target environment.

6.36.Unit Testing:
 Software verification and validation method in which a programmer tests if individual units of source
code are fit  for use. It is usually conducted by the development team.

6.37 Usability Testing:
Testing technique which verifies the ease with which a user can learn to operate, prepare inputs for, and interpret outputs of a system or component. It is usually performed by end users.