Network condition testing in Testing Fundamentals - Framework Patterns

Framework Mode - Network condition testing

Folder Structure for Network Condition Testing Framework

network-testing-framework/
├── tests/
│   ├── test_slow_network.py
│   ├── test_offline_mode.py
│   └── test_flaky_connection.py
├── utils/
│   ├── network_simulator.py
│   └── logger.py
├── config/
│   ├── environments.yaml
│   └── network_profiles.yaml
├── reports/
│   └── latest_report.html
├── conftest.py
└── README.md

Test Framework Layers

• Test Layer: Contains test scripts that simulate different network conditions like slow speed, offline mode, or unstable connections.
• Utility Layer: Includes helper modules such as network_simulator.py to apply network throttling or disconnections, and logger.py for logging test steps and results.
• Configuration Layer: Holds environment settings and network profiles in YAML files to easily switch between different network scenarios and test environments.
• Reporting Layer: Generates human-readable test reports stored in the reports/ folder for easy review.
• Test Runner & Fixtures: conftest.py manages setup and teardown, applying network conditions before tests run and cleaning up after.

Configuration Patterns

• Environment Configurations: Use environments.yaml to define URLs, credentials, and other environment-specific data.
• Network Profiles: Define profiles like slow 3G, offline, or flaky in network_profiles.yaml with parameters such as latency, bandwidth, and packet loss.
• Dynamic Loading: Load configurations at test start to apply the correct network simulation and environment settings automatically.
• Secrets Management: Store sensitive data securely and avoid hardcoding credentials in test scripts.

Test Reporting and CI/CD Integration

• Test Reports: Generate HTML or XML reports summarizing test results, including passed and failed tests under different network conditions.
• Logging: Detailed logs capture network simulation steps and errors for easier debugging.
• CI/CD Integration: Integrate tests into pipelines (e.g., GitHub Actions, Jenkins) to run network condition tests automatically on code changes.
• Alerts: Configure notifications for test failures to quickly inform the team about network-related issues.

Best Practices for Network Condition Testing Framework

1. Isolate Network Simulation: Keep network simulation code separate from test logic to reuse and maintain easily.
2. Use Realistic Profiles: Model network conditions based on real user environments for meaningful test results.
3. Automate Setup and Cleanup: Ensure network conditions are applied before tests and reset after to avoid side effects.
4. Parameterize Tests: Use data-driven testing to run the same test under multiple network profiles efficiently.
5. Integrate Early: Run network condition tests regularly in CI to catch issues early in development.

Self-Check Question

Where in this folder structure would you add a new network profile for "4G LTE with high latency"?

Key Result

Organize tests, utilities, configs, and reports clearly to simulate and validate app behavior under various network conditions.

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