Teating knowledge

Testing Types

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.

Integration testing – The phase in software testing in which individual software modules are combined and tested as a group. It is usually conducted by testing teams.
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.
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.
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.
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.
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.
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.
Load testing – Testing technique that puts demand on a system or device and measures its response. It is usually conducted by the performance engineers.
Stress testing – System is stressed beyond its specifications to check how and when it fails. Performed under heavy load like putting large number beyond storage capacity, complex database queries, continuous input to system or database load.
Performance testing – Functional testing conducted to evaluate the compliance of a system or component with specified performance requirements. It is usually conducted by the performance engineer.
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.
Install/uninstall testing - Quality assurance work that focuses on what customers will need to do to install and set up the new software successfully. It may involve full, partial or upgrades install/uninstall processes and is typically done by the software testing engineer in conjunction with the configuration manager.
Recovery testing – Testing technique which evaluates how well a system recovers from crashes, hardware failures, or other catastrophic problems. It is performed by the testing teams.
Security testing – A process to determine that an information system protects data and maintains functionality as intended. It can be performed by testing teams or by specialized security-testing companies.
Compatibility testing – Testing technique that validates how well a software performs in a particular hardware/software/operating system/network environment. It is performed by the testing teams.
Comparison testing – Testing technique which compares the product strengths and weaknesses with previous versions or other similar products. Can be performed by tester, developers, product managers or product owners..
Alpha testing – Type of testing a software product or system conducted at the developer’s site. Usually it is performed by the end user.
Beta testing – Final testing before releasing application for commercial purpose. It is typically done by end-users or others.
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.
Exploratory Testing: Black box testing technique performed without planning and documentation. It is usually performed by manual testers.
Globalization Testing: Testing method that checks proper functionality of the product with any of the culture/locale settings using every type of international input possible. It is performed by the testing team.
Non-functional Testing: Testing technique which focuses on testing of a software application for its non-functional requirements. Can be conducted by the performance engineers or by manual testing teams.
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.

 http://www.testingknowledge.com