Network condition testing in Testing Fundamentals - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Network Latency Impact

Which of the following best describes the impact of high network latency on a web application's user experience?

A High latency improves security by slowing down data transmission.

B Pages load instantly but data updates slowly in the background.

C Network latency only affects the server, not the user's device or experience.

D User actions take longer to respond, causing delays in page loading and interactions.

💡 Hint

Think about what happens when the network takes longer to send or receive data.

High network latency means data takes longer to travel between the user and server, causing delays in loading pages and responding to user actions.

❓ Predict Output

intermediate

Simulating Network Throttling in Test Code

What will be the output of the following Python test code snippet simulating network delay?

Testing Fundamentals

import time
start = time.time()
time.sleep(2)  # Simulate 2 seconds network delay
end = time.time()
print(round(end - start))

A 2

B 0

C 3

D 1

💡 Hint

Look at how long the sleep function pauses the program.

The time.sleep(2) pauses execution for 2 seconds, so the printed rounded time difference is 2.

❓ assertion

advanced

Validating Timeout Behavior in Automated Tests

Which assertion correctly verifies that a network request times out within 5 seconds in a test?

Testing Fundamentals

response = make_network_request()
# Choose the correct assertion below

A assert response.status_code == 200

B assert response.status_code == 408

C assert response.elapsed.total_seconds() < 5

D assert response.elapsed.total_seconds() > 5

💡 Hint

Timeout means the request should not take longer than the limit.

Checking that the elapsed time is less than 5 seconds confirms the request timed out properly or completed quickly.

🔧 Debug

advanced

Identifying Network Condition Test Failure Cause

A test simulating 1 second network delay fails because the actual delay is 0 seconds. What is the most likely cause?

A The network simulation tool was not enabled during the test run.

B The test code has a syntax error causing it to skip the delay.

C The server responded with an error code instead of delaying.

D The test environment has too much bandwidth causing delay to be ignored.

💡 Hint

Think about what controls network delay simulation.

If the simulation tool is off, no artificial delay is added, so the test sees zero delay.

❓ framework

expert

Choosing the Best Tool for Network Condition Testing

Which testing framework or tool is best suited for simulating various network conditions like latency, bandwidth limits, and packet loss during automated UI tests?

A Selenium WebDriver alone without any network simulation plugins

B Using Chrome DevTools Protocol with Puppeteer to throttle network speed and simulate conditions

C JUnit for backend unit testing without network simulation features

D Postman for API testing without network condition simulation

💡 Hint

Look for a tool that integrates UI testing with network control features.

Puppeteer with Chrome DevTools Protocol allows controlling network conditions during UI tests, making it ideal for this purpose.

Practice

1. What is the main purpose of network condition testing in software testing?

easy

A. To check how an app behaves under different internet speeds and qualities

B. To test the app's user interface design

C. To verify database connections only

D. To check the app's installation process

Solution

1. Step 1: Understand network condition testing

   Network condition testing focuses on how software performs with various internet speeds and qualities.

2. Step 2: Compare options to the definition

   Only To check how an app behaves under different internet speeds and qualities matches this purpose; others focus on unrelated testing areas.

3. Final Answer:

   To check how an app behaves under different internet speeds and qualities -> Option A

4. Quick Check:

   Network condition testing = Check app behavior on different networks [OK]

Hint: Focus on internet speed and quality effects on app [OK]

Common Mistakes:

• Confusing network testing with UI testing
• Thinking it only tests database or installation

2. Which of the following is the correct way to simulate a slow network in a testing tool?

easy

A. Set network speed to 3 Mbps and add 200 ms latency

B. Set network speed to 100 Mbps with 0 ms latency

C. Disable network throttling completely

D. Increase CPU usage to 90%

Solution

1. Step 1: Identify how to simulate slow network

   Slow network simulation requires reducing speed and adding latency (delay).

2. Step 2: Evaluate options

   Set network speed to 3 Mbps and add 200 ms latency sets a low speed and adds latency, correctly simulating slow network. Others do not simulate slow network.

3. Final Answer:

   Set network speed to 3 Mbps and add 200 ms latency -> Option A

4. Quick Check:

   Slow network = low speed + latency [OK]

Hint: Slow network means low speed plus added delay [OK]

Common Mistakes:

• Choosing high speed as slow network
• Ignoring latency in simulation

3. Consider this pseudocode simulating network conditions: <pre>simulateNetwork(speedMbps, latencyMs) { if (speedMbps < 5) return "Slow Network"; else if (latencyMs > 100) return "High Latency"; else return "Good Network"; } What will be the output of simulateNetwork(10, 150)?

medium

A. "Slow Network"

B. "High Latency"

C. "Good Network"

D. Runtime Error

Solution

1. Step 1: Check speed condition

   Speed is 10 Mbps, which is not less than 5, so skip first condition.

2. Step 2: Check latency condition

   Latency is 150 ms, which is greater than 100, so return "High Latency".

3. Final Answer:

   "High Latency" -> Option B

4. Quick Check:

   Latency > 100 triggers "High Latency" [OK]

Hint: Check conditions in order, latency > 100 returns "High Latency" [OK]

Common Mistakes:

• Choosing "Slow Network" ignoring speed value
• Assuming good network despite high latency

4. You have this test code snippet to simulate network conditions:

networkSpeed = 2
latency = 50
if (networkSpeed > 5) {
  print("Fast Network")
} else if (latency > 100) {
  print("High Latency")
} else {
  print("Slow Network")
}

What is the output and is there any logical error?

medium

A. Output: "Fast Network"; Logical error in conditions

B. Output: "Slow Network"; Logical error in conditions

C. Output: "High Latency"; Logical error in conditions

D. Output: "Slow Network"; No logical error

Solution

1. Step 1: Evaluate conditions with given values

   networkSpeed=2 (not >5), latency=50 (not >100), so else block runs printing "Slow Network".

2. Step 2: Check for logical errors

   Conditions correctly cover cases; no error in logic.

3. Final Answer:

   Output: "Slow Network"; No logical error -> Option D

4. Quick Check:

   Speed low and latency low = "Slow Network" [OK]

Hint: Check conditions with given values carefully [OK]

Common Mistakes:

• Assuming latency triggers "High Latency" incorrectly
• Thinking there is a logical error when none exists

5. You want to test an app's behavior under unstable network conditions that randomly switch between fast and slow speeds. Which approach is best?

hard

A. Test only on a stable slow network

B. Test only on a stable fast network

C. Use a network simulation tool to alternate speeds during the test

D. Ignore network speed and focus on UI testing

Solution

1. Step 1: Understand unstable network testing

   Unstable network means changing speeds during use, so simulation must alternate speeds.

2. Step 2: Evaluate options for best fit

   Use a network simulation tool to alternate speeds during the test uses a tool to alternate speeds, matching unstable network testing. Others ignore instability.

3. Final Answer:

   Use a network simulation tool to alternate speeds during the test -> Option C

4. Quick Check:

   Unstable network = alternating speeds [OK]

Hint: Simulate speed changes to mimic unstable network [OK]

Common Mistakes:

• Testing only stable networks for unstable scenarios
• Ignoring network speed in testing