Software Testing Techniques

White Box Testing Technique :

Also called ‘Structural Testing / Glass Box Testing’ is used for testing the code keeping the system specs in mind.

Inner working is considered and thus Developers Test..

Mutation Testing : Number of mutants of the same program created with minor changes and none of their result should coincide with that of the result of the original program given same test case.

Basic Path Testing : Testing is done based on Flow graph notation, uses Cyclometric complexity & Graph matrices.

Control Structure Testing : The Flow of control execution path is considered for testing. It does also checks :-

1. Conditional Testing : Branch Testing, Domain Testing.
2. Data Flow Testing.
3. Loop testing :Simple, Nested, Conditional, Unstructured Loops.

Black Box Testing :

Also called ‘Functional Testing’ as it concentrates on testing of the functionality rather than the internal details of code.

Test cases are designed based on the task descriptions.

Equivalence Class Testing : Test inputs are classified into Equivalence classes such that one input check validates all the input values in that class.

Boundary Value Testing : Boundary values of the Equivalence classes are considered and tested as they generally fail in Equivalence class testing.

Comparison Testing : Test cases results are compared with the results of the test Oracle.

Graph based Testing : Cause and effect graphs are generated and cyclometric complexity considered in using the test cases.

Incremental Testing:

Incremental Testing is a disciplined method of testing the interfaces between unit-tested programs to a given module or component one by one, and testing each result and combination.

There are two types of incremental testing :

1) Top-Down

2) Bottom-up

Thread Testing:

This test technique, which is often used during early integration testing, demonstrates key functional capabilities by testing a string of units that accomplish a specific function in the application. Thread testing and incremental testing are usually utilized together. For example, units can undergo incremental testing until enough units are integrated and a single business function can be performed, threading through the integrated components.

RELATED POST

SOFTWARE QUALITY ASSURANCE AND CONTROL

SOFTWARE QUALITY AND COST ASPECT

STABLE PROCESS OF SOFTWARE TESTING

STABLE PROCESS OF SOFTWARE TESTING PART TWO

DEFECTS IN SOFTWARE TESTING

REDUCTION OF DEFECTS IN SOFTWARE TESTING

SOFTWARE TESTING AND EFFECTING FACTORS

SCOPE OF SOFTWARE TESTING

TESTING LIFE CYCLE PART ONE

TESTING LIFE CYCLE PART TWO

TESTING LIFE CYCLE PART THREE

SOFTWARE TESTING AND CONSTRAINTS WITH IN IT

TESTING CONSTRAINTS PART TWO

LIFE CYCLE TESTING

TEST METRICS

Independent Software Testing

Test Process

Testing verification and validation

Functional and structural testing

Static and dynamic testing

V model testing

Eleven steps of V model testing

Structural testing

Execution testing technique

Recovery Testing technique

Operation testing technique

Compliance software testing technique

Security testing technique