Manual Testing

Test which focus on the boundary or limit conditions of the software being tested. (Some of these tests are stress tests).

A testing phase where the tester tries to 'break' the system by randomly trying the system's functionality is called Ad Hoc testing. This can include negative testing also.

Functional testing is a way of checking software to ensure that it has all the required functionality that's specified within its functional requirements.

 Beta testing is testing of a release of a software product conducted by customers.

Testing based on an analysis of the specification of a piece of software without reference to its internal workings. The goal is to test how well the component conforms to the published requirements for the component.

An approach to integration testing where the lowest level components are tested first, then used to facilitate the testing of higher level components. The process is repeated until the component at the top of the hierarchy is tested.

The Capability Maturity Model for Software (CMM or SW-CMM) is a model for judging the maturity of the software processes of an organization and for identifying the key practices that are required to increase the maturity of these processes.

 A component is an identifiable part of a larger program or construction. Usually, a component provides a particular function or group of related functions

A combination of Black Box and White Box testing methodologies is called Gray box testing. Testing a piece of software against its specification but using some knowledge of its internal workings.

The generation of source code is called Coding.

Testing whether software is compatible with other elements of a system with which it should operate, e.g. browsers, Operating Systems, or hardware.

Gorilla Testing is a testing technique in which sometimes developers also join hands with testers to test a particular module thoroughly in all aspects.

Testing conducted to enable a user/customer to determine whether to accept a software product.

 Verifying a product is accessible to the people having disabilities (deaf, blind, mentally disabled etc.).

BVA is similar to Equivalence Partitioning but focuses on "corner cases" or values that are usually out of range as defined by the specification. This means that if a function expects all values in range of negative 100 to positive 1000, test inputs would include negative 101 and positive 1001.

Testing of all branches in the program source code is called Branch Testing.

When actual result deviates from the expected result while testing a software application or product then it results into a defect. Hence, any deviation from the specification mentioned in the product functional specification document is a defect. In different organizations it’s called a Bug.

Testing of individual software components is called Component testing.

When actual result deviates from the expected result while testing a software application or product then it results into a defect.

Testing 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 is called End-to-End testing.

Checks for memory leaks or other problems that may occur with prolonged execution.

A portion of a component's input or output domains for which the component's behaviour is assumed to be the same from the component's specification.

A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes.

White Box Testing is also known as Glass Box testing.