Network condition testing in Testing Fundamentals - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to simulate a network delay of 2 seconds in a test.

Testing Fundamentals

def test_network_delay():
    import time
    time.[1](2)
    assert True

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

Asleep

Bwait

Cdelay

Dpause

Attempts:

3 left

💡 Hint

Common Mistakes

Using non-existent functions like time.wait or time.delay.

The time.sleep() function pauses the program for the given number of seconds, simulating network delay.

2fill in blank

medium

Complete the code to check if the network is reachable by pinging 'example.com'.

Testing Fundamentals

import subprocess

def is_network_reachable():
    response = subprocess.run(['ping', '-c', '1', '[1]'], capture_output=True)
    return response.returncode == 0

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

Alocalhost

Bexample.com

C192.168.1.1

Dgoogle.com

Attempts:

3 left

💡 Hint

Common Mistakes

Using local or private IP addresses that may not reflect internet connectivity.

Using 'example.com' as the target host checks general network reachability.

3fill in blank

hard

Fix the error in the code to simulate packet loss by dropping 30% of packets in a test.

Testing Fundamentals

import random

def simulate_packet_loss():
    if random.random() [1] 0.3:
        return 'Packet dropped'
    else:
        return 'Packet sent'

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

A<

B<=

C==

D>

Attempts:

3 left

💡 Hint

Common Mistakes

Using > 0.3 which causes 70% packet loss instead of 30%.

Using < 0.3 means 30% chance to drop the packet, as random.random() returns a float between 0 and 1.

4fill in blank

hard

Fill both blanks to create a test that retries a network request up to 3 times if it fails.

Testing Fundamentals

def retry_request():
    attempts = 0
    while attempts [1] 3:
        success = make_request()
        if success:
            return True
        attempts [2] 1
    return False

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

A<

B<=

C+=

D++

Attempts:

3 left

💡 Hint

Common Mistakes

Using <= 3 causes 4 attempts, using ++ is invalid in Python.

The loop runs while attempts is less than 3, and attempts is incremented by 1 each time using +=.

5fill in blank

hard

Fill all three blanks to create a dictionary comprehension that maps URLs to their response times if response time is less than 500ms.

Testing Fundamentals

response_times = {url[1]: time for url, time in results.items() if time [2] 500 and url [3] 'http://example.com'}

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

A.upper()

B<

C!=

D.lower()

Attempts:

3 left

💡 Hint

Common Mistakes

Using .upper() instead of .lower(), using > instead of <, using == instead of !=.

The URL keys are converted to lowercase with .lower(), times less than 500 are filtered with <, and URLs not equal to 'http://example.com' are included with !=.

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