Scribd
Upload
20 views

Black Box Testing and White Box Testing

Uploaded by

zhyvaga612
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
20 views

Black Box Testing and White Box Testing

Uploaded by

zhyvaga612
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

Black Box Testing and White Box Testing according to ISTQB Foundation Level 4.

0:

Aspect Black Box Testing White Box Testing

Definition Testing based on functional specifications without Testing based on analysis of internal code
regard to the internal code structure. structure.

Focus Focuses on what the software is supposed to do Focuses on how the software works (internal
(functional requirements). logic and structure).

Techniques Techniques include equivalence partitioning, boundary Techniques include statement testing, branch
value analysis, decision table testing, and state transition testing, path testing, and condition testing.
testing.

Test Basis Specifications, requirements, user stories, and functional Source code, detailed design, and architecture.
design documents.

Test Coverage Focuses on functional coverage (e.g., input Focuses on code coverage (e.g., statements,
combinations). branches, paths).

Test Case Based on functional requirements and specifications. Based on code structure and design.
Design

Knowledge Requires knowledge of the functionality of the Requires knowledge of the programming
Required application but not the code. languages and code structure.

Examples of Equivalence partitioning, boundary value analysis, Control flow testing, data flow testing, and
Techniques decision tables, state transition diagrams. branch testing.

Detection of Detects missing functionalities, interface errors, and Detects logic errors, coding mistakes, and design
discrepancies from the specifications. errors.

Testers Testers are usually not the developers of the code and Testers are often developers or require detailed
Involved might not have programming knowledge. knowledge of the code.

When Used Typically used during higher levels of testing (e.g., Typically used during lower levels of testing
system testing, acceptance testing). (e.g., unit testing, integration testing).

Advantages Allows for testing from the user's perspective, helping Allows for thorough testing of the internal
ensure the system meets user requirements. workings of the application, ensuring all paths are
executed.

Disadvantages May miss some internal errors that only become Can be time-consuming and requires detailed
apparent under specific conditions not covered by knowledge of the code, which might not always
functional tests. be available.

You might also like