7: Types of Testing - Part 1

Types of Testing

Specification-based (black-box, also known as behavioral techniques), structure-based (white-box or structural techniques) and experience-based.

Specification-based techniques include both functional and non-functional techniques

Functional testing is concerned with what the system does, its features or functions. Non-functional testing is concerned with examining how well the system does something, rather than what it does. Non-functional aspects (also known as quality characteristics or quality attributes) include performance, usability, portability, maintainability, etc

Black Box testing

White Box testing

Grey Box testing

Black- Box Testing

Testing without the internal knowledge of the system or software.

     1. Its done with the users perspective.

2. In black box testing the structure of the program is not considered at all.
3. Black box is carried out to check the functionality of the product.

     4. Here software is considered as a black box to which the defined inputs are given and from which defined outputs are obtained.

Testing either functional or non functional, without reference to the internal structure of the component or system.

Advantages

1. Unbiased testing as it is performed by testers, independent of developers.
2. No programming knowledge is expected from the tester.
3. Test is done from the point of view of user/customer and not developer.
4. Incorrect or missing functionality
5. Interface errors
6. Behavior or performance errors
7. Initialization and termination errors

Disadvantages

1. Testing every possible input stream is unrealistic as it would take inordinate amount of time.

White-box testing: Testing based on an analysis of the internal structure of the component or system.

1. In white box testing , the structure of the program is taken into consideration.
2. The objective is to ensure that each and every line of the code is tested.
3. Testing the product based on the internal system knowledge.

Black Box Testing Types

What’s the deliverable we are looking for the motive for testing?

Build Verification Test (BVT)

Is done on each new build of the SUT to verify, if the build is testable before the build is released into the hands of the test team. Any build that fails the build verification test is rejected, and testing continues on the previous build (provided there has been at least one build that has passed the acceptance test).Also known as Build Acceptance Test.

Ex

Team Structure: Development > Build team > Test Team