Testing

Front 1

Ad Hoc Testing

Back 1

A testing phase where the tester tries to 'break' the system by randomly trying the systems functionality. Can include negative testing as well. See also Monkey Testing.

Front 2

Black Box Testing

Back 2

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.

Front 3

Breadth Testing

Back 3

A test suite that exercises the full functionality of a product but does not test features in detail.

Front 4

Component Testing

Back 4

See Unit Testing.

Front 5

Dynamic Testing

Back 5

Testing software through executing it. See also Static Testing.

Front 6

End-to-End testing

Back 6

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.

Front 7

Exhaustive Testing

Back 7

Testing which covers all combinations of input values and preconditions for an element of the software under test.

Front 8

Functional Testing

Back 8

Testing the features and operational behavior of a product to ensure they correspond to its specifications. May be Black Box or White Box testing.

Front 9

Gray Box Testing

Back 9

A combination of Black Box and White Box testing methodologies: testing a piece of software against its specification but using some knowledge of its internal workings.

Front 10

Integration Testing

Back 10

Testing of combined parts of an application to determine if they function together correctly. Usually performed after unit and functional testing. This type of testing is especially relevant to client/server and distributed systems.

Front 11

Monkey Testing

Back 11

Testing a system or an Application on the fly, i.e just few tests here and there to ensure the system or an application does not crash out.

Front 12

Negative Testing

Back 12

Testing aimed at showing software does not work. Also known as "test to fail". See also Positive Testing.

Front 13

Performance Testing

Back 13

Testing conducted to evaluate the compliance of a system or component with specified performance requirements. Often this is performed using an automated test tool to simulate large number of users. Also know as "Load Testing".

Front 14

Positive Testing

Back 14

Testing aimed at showing software works. Also known as "test to pass". See also Negative Testing

Front 15

Regression Testing

Back 15

Retesting a previously tested program following modification to ensure that faults have not been introduced or uncovered as a result of the changes made.

Front 16

Sanity Testing

Back 16

Brief test of major functional elements of a piece of software to determine if its basically operational. See also Smoke Testing.

Front 17

Stress Testing

Back 17

Testing conducted to evaluate a system or component at or beyond the limits of its specified requirements. Often this is performance testing using a very high level of simulated load.

Front 18

Static Testing

Back 18

Testing software without executing it.

Front 19

System Testing

Back 19

Testing that attempts to discover defects that are properties of the entire system rather than of its individual components.

Front 20

Usability Testing

Back 20

Testing the ease with which users can learn and use a product.

Front 21

Unit Testing

Back 21

Testing of individual software components.

Front 22

White Box Testing

Back 22

Testing based on an analysis of internal workings of a piece of software.

Front 23

Workflow Testing

Back 23

Scripted end-to-end testing which duplicates specific workflows which are expected to be utilized by the end-user.