Black-box testing techniques in Software Engineering - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to identify the black-box testing technique that focuses on input-output behavior.

Software Engineering

The black-box testing technique that tests software by examining inputs and expected outputs is called [1] testing.

Drag options to blanks, or click blank then click option'

AWhite-box

BStructural

CFunctional

DUnit

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing black-box with white-box testing.

Choosing structural testing which is a white-box technique.

Functional testing is a black-box technique that tests the software based on its functional requirements, focusing on inputs and expected outputs without looking at internal code.

2fill in blank

medium

Complete the code to name the black-box testing technique that divides input data into valid and invalid classes.

Software Engineering

The black-box testing technique that groups inputs into classes to reduce test cases is called [1] partitioning.

Drag options to blanks, or click blank then click option'

ABoundary value

BDecision table

CState transition

DEquivalence

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing it with boundary value analysis which focuses on edge cases.

Choosing decision table which is a different technique.

Equivalence partitioning divides input data into classes where test cases from each class are expected to behave similarly, reducing the number of tests needed.

3fill in blank

hard

Fix the error in the statement about a black-box testing technique that uses tables to represent combinations of inputs.

Software Engineering

The black-box testing technique that uses [1] tables to represent input combinations and expected outputs is called decision table testing.

Drag options to blanks, or click blank then click option'

Adecision

Bstate

Cequivalence

Dboundary

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing decision tables with state tables.

Choosing boundary or equivalence which are different techniques.

Decision table testing uses decision tables to show combinations of inputs and their corresponding outputs, helping to test complex business rules.

4fill in blank

hard

Fill both blanks to complete the description of a black-box testing technique that tests software behavior based on states and transitions.

Software Engineering

In [1] testing, the software is modeled as a set of states and [2] between them to verify correct behavior.

Drag options to blanks, or click blank then click option'

AState transition

BEquivalence

Ctransitions

DBoundary

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing state transition with equivalence or boundary testing.

Using 'Boundary' instead of 'transitions' for the second blank.

State transition testing models software as states and transitions to test how the system moves from one state to another based on inputs.

5fill in blank

hard

Fill all three blanks to complete the code describing black-box testing techniques related to input values and conditions.

Software Engineering

The [1] value analysis technique focuses on testing at the edges of input ranges, while [2] partitioning groups inputs, and [3] table testing uses rules to test combinations.

Drag options to blanks, or click blank then click option'

ABoundary

BEquivalence

CDecision

DState

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up boundary and equivalence techniques.

Confusing decision table testing with state transition testing.

Boundary value analysis tests edge cases, equivalence partitioning groups inputs into classes, and decision table testing uses tables to test input combinations.

Practice

1. Which of the following best describes black-box testing?

easy

A. Testing software based on its functionality without looking at the code

B. Testing software by examining its internal code structure

C. Testing only the user interface of the software

D. Testing software performance under heavy load

Solution

1. Step 1: Understand black-box testing definition

   Black-box testing focuses on checking software behavior from the user's perspective without knowledge of internal code.

2. Step 2: Compare options with definition

   Testing software based on its functionality without looking at the code matches this definition exactly, while others describe different testing types.

3. Final Answer:

   Testing software based on its functionality without looking at the code -> Option A

4. Quick Check:

   Black-box testing = Functionality testing without code [OK]

Hint: Black-box tests check outputs, not code details [OK]

Common Mistakes:

• Confusing black-box with white-box testing
• Thinking black-box tests only UI
• Assuming black-box tests check performance

2. Which of these is a common technique used in black-box testing?

easy

A. Equivalence partitioning

B. Code coverage analysis

C. Static code review

D. Memory leak detection

Solution

1. Step 1: Identify black-box testing techniques

   Equivalence partitioning divides input data into groups to reduce test cases, a classic black-box method.

2. Step 2: Eliminate non-black-box options

   Code coverage and static code review require code knowledge; memory leak detection is performance testing.

3. Final Answer:

   Equivalence partitioning -> Option A

4. Quick Check:

   Black-box technique = Equivalence partitioning [OK]

Hint: Black-box uses input grouping like equivalence partitioning [OK]

Common Mistakes:

• Choosing code-based techniques for black-box
• Confusing static analysis with black-box testing
• Mixing performance tools with black-box

3. Consider a function that accepts an integer input from 1 to 100. Using boundary value analysis, which of the following is a valid boundary value?

medium

A. 0

B. 50

C. 1

D. 101

Solution

1. Step 1: Understand boundary value analysis

   This technique tests values at the edges of input ranges, such as minimum and maximum valid inputs.

2. Step 2: Identify valid boundary values

   Valid input range is 1 to 100, so boundaries are 1 and 100. Among options, 1 is a boundary value.

3. Final Answer:

   1 -> Option C

4. Quick Check:

   Boundary value = 1 [OK]

Hint: Test inputs at range edges, not middle or invalid [OK]

Common Mistakes:

• Choosing invalid inputs like 0 or 101 as boundaries
• Picking middle values instead of edges
• Confusing equivalence partitioning with boundary testing

4. A tester wrote these test cases for a login form: empty username, empty password, valid username and password, invalid username. What is missing for good black-box testing?

medium

A. Testing with SQL injection strings

B. Testing with boundary values for input length

C. Reviewing the source code for errors

D. Checking server logs for errors

Solution

1. Step 1: Analyze given test cases

   Tests cover empty and valid/invalid inputs but do not check input length boundaries.

2. Step 2: Identify missing black-box technique

   Boundary value analysis for input length is important to catch edge errors, missing here.

3. Final Answer:

   Testing with boundary values for input length -> Option B

4. Quick Check:

   Missing boundary tests = Testing with boundary values for input length [OK]

Hint: Check input length edges for thorough black-box tests [OK]

Common Mistakes:

• Confusing security tests with black-box functional tests
• Thinking code review is part of black-box testing
• Ignoring boundary value analysis

5. You have a form that accepts age between 18 and 60. Using black-box testing, which set of inputs covers equivalence partitioning and boundary value analysis?

hard

A. 18, 19, 59, 60

B. 18, 30, 60

C. 0, 18, 60, 100

D. 17, 18, 30, 60, 61

Solution

1. Step 1: Understand equivalence partitioning and boundary value analysis

   Equivalence partitioning divides inputs into valid and invalid groups; boundary value analysis tests edges of valid ranges.

2. Step 2: Check options for both techniques

   17, 18, 30, 60, 61 includes invalid low (17), valid boundaries (18, 60), valid middle (30), and invalid high (61), covering partitions and boundaries.

3. Final Answer:

   17, 18, 30, 60, 61 -> Option D

4. Quick Check:

   Both partitions and boundaries = 17, 18, 30, 60, 61 [OK]

Hint: Include invalid, boundary, and normal inputs for full coverage [OK]

Common Mistakes:

• Ignoring invalid inputs in test sets
• Testing only valid inputs without boundaries
• Confusing boundary values with just middle values