Difference Between Specification-based Testing, Structure-based Testing and Experience-based Testing Techniques.

Test Design Techniques

Test Design is creating a set of inputs for given software that will provide a set of expected outputs. The idea is to ensure that the system is working good enough and it can be released with as few problems as possible.

The purpose of a test design technique is to identify

→ Test conditions

→ Test cases

→ Test data.

There are three types of test design techniques:

→ Specification-based (Black-box) test design techniques

→ Structure-based (White-box) test design techniques

→ Experience-based test design techniques

Difference between Specification-based, Structure-based and Experience-based Testing

Specification-based Technique

Specification-based testing also known as black-box testing is a dynamic testing technique. In this 

testing only input and output are taken into considerations and internal software structure are not 

considered. The key characteristics of Specification-based testing is that the test are derived from

models either formal or informal that specify the problem to be solved by the software or its  

In this technique tester is concerned with about what the software does not how it does.

Types of Specification-based Technique

→ Equivalence Partitioning

→ Boundary Value Analysis

→ Decision Table

→ State Transition Diagram

Structure-based Testing Technique

Structure-based testing also known as white-box testing technique is a dynamic testing technique 

which  takes internal software structure into consideration. It tests how the decisions and conditions are 

executed,  unit tests are developed to exercise loops, decisions. Information about how the software is 

constructed is used to derive the test cases.

Types of Structure-based Testing Technique

→ Statement Testing and Coverage

→ Decision Testing and  Coverage

→ Condition Testing and  Coverage

→ Multiple Condition Testing  and Coverage.

Experience-based Testing Technique

In Experience-based testing technique, knowledge of testers, developers, users and other stakeholders  

are used to design test condition and test cases. Experience of both technical people and business 

people is considered as experienced people know where to test and how to test for maximum coverage. 

Types of Experience-based Technique

→ Error Guessing

→ Checklist Based Testing

→ Exploratory Testing

→ Attack Testing

Similarities Between Specification-based, Structure-based and Experience-based Testing Techniques

→ They are all dynamic test design techniques.

→ They execute code to find defects and bugs in the code.

→ They all help in the improvement of the code.

Comparison between experience-based testing and specification based testing can be done as:

1. Both are dynamic test design techniques.

2. Experience based testing can be performed in lack of proper specification and requirement documents

but specification based testing require proper specification.

3. Experience based testing is the responsibility of experts who had previous experience on testing

whereas specification based testing is done by professional software tester.

4. Testing is only performed with GUI for specification based test whereas experience based testing

can be performed both in GUI and code-level.

Difference Between Specification-based Testing, Structure-based Testing and Experience-based 

Testing Techniques

Specification-based	Structure-based	Experience-based
The main objective is to test  functionality behaviour of the  application.	The main objective is to test  the infrastructure of  application.	The main objective is to  complete testing in short  period  of time.
No knowledge of code is  required.	Knowledge of the code is  required.	This requires former testing  experience.
Test cases should be written  based on requirement  specification.	Test cases should be written  based on detailed design  documentation.	Test cases are written based  on former experience.
This is less time consuming  and exhaustive.	This is more time consuming  and exhaustive.	This is less time consuming.
Tester can identify missing  functionalities.	Tester can identify defects in  implementation feature.	Both kind of problems may be  identified.
The specification should be  clear to perform the test.	Specification should be clear  to  perform the test.	It can work in case of  inadequate specifications
→ Equivalence Paritioning → Boundary Value Analysis → Decision Table → State Transition Diagram	→ Statement Testing and  Coverage → Decision Testing and  Coverage → Condition Testing and  Coverage → Multiple Condition Testing  and Coverage.	→ Error Guessing → Checklist Based Testing → Exploratory Testing → Attack Testing