Black-box vs white-box testing in Testing Fundamentals - Practice Questions

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Black-box Testing Focus

Which statement best describes the main focus of black-box testing?

A Testing internal code structure without knowing the program's inputs or outputs

B Testing the software by reviewing the source code line by line

C Testing software functionality based only on inputs and expected outputs without knowledge of internal code

D Testing the software performance by analyzing memory usage

💡 Hint

Think about testing without looking inside the program.

Black-box testing focuses on checking software behavior by providing inputs and verifying outputs without any knowledge of internal code.

🧠 Conceptual

intermediate

White-box Testing Characteristics

Which of the following is a key characteristic of white-box testing?

A It requires knowledge of the internal code and logic to design test cases

B It is performed only after black-box testing is complete

C It ignores the program's internal structure and focuses on output correctness

D It tests the software only through its user interface

💡 Hint

White-box testing means looking inside the program.

White-box testing involves understanding and testing the internal workings of the software, such as code paths and logic.

❓ Predict Output

advanced

Output of Black-box Test Case Result

Given a function that returns the sum of two numbers, what will be the output of this black-box test case if inputs are 3 and 5?

Testing Fundamentals

def add(a, b):
    return a + b

# Black-box test case
input1 = 3
input2 = 5
result = add(input1, input2)
print(result)

A TypeError

B 8

C 35

D None

💡 Hint

Think about what adding 3 and 5 returns.

The function adds two numbers and returns their sum. 3 + 5 equals 8.

❓ assertion

advanced

Correct Assertion for White-box Testing Coverage

Which assertion best verifies that a specific function branch was executed during white-box testing?

Testing Fundamentals

def is_even(num):
    if num % 2 == 0:
        return True
    else:
        return False

result = is_even(4)

A assert result == 4 # Incorrect output check

B assert 'if' in is_even.__code__.co_names # Checks code contains 'if' keyword

C assert result is not None # Checks function returns something

D assert result == True # Checks output correctness only

💡 Hint

White-box testing checks internal logic by verifying outputs for specific inputs.

The assertion checks that the function returns True for input 4, confirming the 'if' branch was executed.

🔧 Debug

expert

Identify the Testing Approach Causing a Bug Miss

A tester uses only black-box testing on a function that has a hidden division by zero error in an internal branch never triggered by normal inputs. What is the most likely outcome?

A The bug will be missed because black-box testing does not examine internal code paths

B The bug will be fixed automatically by black-box testing

C The bug will cause a syntax error during black-box testing

D The bug will be detected because black-box testing covers all internal branches

💡 Hint

Think about what black-box testing can and cannot see.

Black-box testing only tests visible inputs and outputs, so hidden internal errors in untested branches can be missed.

Practice

1. Which testing type focuses on testing software without knowing its internal code?

easy

A. Integration testing

B. Black-box testing

C. Unit testing

D. White-box testing

Solution

1. Step 1: Understand black-box testing concept

   Black-box testing examines software functionality without looking at the code inside.

2. Step 2: Compare with white-box testing

   White-box testing requires knowledge of the internal code structure, unlike black-box testing.

3. Final Answer:

   Black-box testing -> Option B

4. Quick Check:

   Black-box = no code knowledge [OK]

Hint: Black-box ignores code, tests only inputs and outputs [OK]

Common Mistakes:

• Confusing black-box with white-box testing
• Thinking unit testing is always black-box
• Assuming integration testing is black-box by default

2. Which of the following is a correct statement about white-box testing?

easy

A. It tests software without any knowledge of internal code.

B. It ignores the program's internal logic.

C. It only tests the user interface.

D. It requires access to the source code to design test cases.

Solution

1. Step 1: Recall white-box testing definition

   White-box testing involves looking inside the code to create test cases.

2. Step 2: Evaluate each option

   It requires access to the source code to design test cases. correctly states the need for source code access; others describe black-box or incorrect ideas.

3. Final Answer:

   It requires access to the source code to design test cases. -> Option D

4. Quick Check:

   White-box = code access needed [OK]

Hint: White-box needs code access; black-box does not [OK]

Common Mistakes:

• Mixing up white-box and black-box definitions
• Thinking white-box only tests UI
• Believing white-box ignores internal logic

3. Consider this scenario: A tester writes test cases based on the program's code paths and conditions. What type of testing is this?

medium

A. White-box testing

B. Black-box testing

C. System testing

D. Acceptance testing

Solution

1. Step 1: Identify testing based on code paths

   Testing that uses knowledge of code paths and conditions is white-box testing.

2. Step 2: Eliminate other options

   Black-box ignores code; system and acceptance testing focus on overall system or user needs, not code paths.

3. Final Answer:

   White-box testing -> Option A

4. Quick Check:

   Code path testing = white-box [OK]

Hint: Code path knowledge means white-box testing [OK]

Common Mistakes:

• Choosing black-box because of 'test cases' mention
• Confusing system testing with white-box
• Ignoring code path clues

4. A tester tries to perform white-box testing but does not have access to the source code. What is the main problem here?

medium

A. White-box testing only tests the user interface.

B. Black-box testing requires source code access.

C. White-box testing cannot be done without source code access.

D. Source code access is optional for white-box testing.

Solution

1. Step 1: Understand white-box testing requirements

   White-box testing needs access to source code to examine internal logic.

2. Step 2: Analyze options

   White-box testing cannot be done without source code access. correctly states the problem; others are false or contradict white-box principles.

3. Final Answer:

   White-box testing cannot be done without source code access. -> Option C

4. Quick Check:

   White-box needs code access [OK]

Hint: No code access means no white-box testing [OK]

Common Mistakes:

• Thinking black-box needs code access
• Believing white-box tests only UI
• Assuming code access is optional

5. A software team wants to improve test coverage by combining black-box and white-box testing. Which approach best achieves this?

hard

A. Use black-box testing to check user inputs and outputs, and white-box testing to verify internal code paths.

B. Only perform black-box testing since it covers all code paths.

C. Use white-box testing exclusively because it tests the interface.

D. Skip testing and rely on user feedback after release.

Solution

1. Step 1: Understand strengths of black-box and white-box testing

   Black-box tests functionality without code knowledge; white-box tests internal code paths.

2. Step 2: Combine both methods effectively

   Using black-box for inputs/outputs and white-box for code paths covers more test cases and improves quality.

3. Final Answer:

   Use black-box testing to check user inputs and outputs, and white-box testing to verify internal code paths. -> Option A

4. Quick Check:

   Combine black-box + white-box for best coverage [OK]

Hint: Combine black-box for UI and white-box for code paths [OK]

Common Mistakes:

• Relying on only one testing type
• Confusing white-box with UI testing
• Ignoring testing before release