Performance testing basics in Testing Fundamentals - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Load Testing Purpose

What is the main goal of load testing in performance testing?

A To verify the correctness of business logic in the application

B To find the maximum number of users the system can handle before crashing

C To test the system's security against unauthorized access

D To check how the system behaves under expected normal user load

💡 Hint

Think about testing the system under typical usage conditions.

Load testing measures system behavior under expected normal user load to ensure it performs well during regular use.

❓ Predict Output

intermediate

Interpreting Response Time Measurement Code

What will be the output of this Python code snippet simulating a simple response time measurement?

Testing Fundamentals

import time
start = time.time()
time.sleep(0.5)
end = time.time()
response_time = end - start
print(round(response_time, 1))

A 5.0

B 0.05

C 0.5

D 0.005

💡 Hint

Consider how long time.sleep(0.5) pauses the program.

The code pauses for 0.5 seconds, so the response time measured will be approximately 0.5 seconds.

❓ assertion

advanced

Validating Throughput Assertion in Performance Test

Which assertion correctly checks that the throughput is at least 100 requests per second?

Testing Fundamentals

throughput = get_throughput()
# Insert assertion here

A assert throughput >= 100, f"Throughput too low: {throughput}"

B assert throughput > 100, f"Throughput too low: {throughput}"

C assert throughput < 100, f"Throughput too high: {throughput}"

D assert throughput == 100, f"Throughput mismatch: {throughput}"

💡 Hint

Think about including the minimum acceptable throughput value.

The assertion must allow throughput equal to or greater than 100, so using >= is correct.

🔧 Debug

advanced

Identifying Bottleneck in Performance Test Report

A performance test report shows high CPU usage but low memory usage and slow response times. What is the most likely bottleneck?

A Disk I/O is the bottleneck causing slow responses

B CPU is the bottleneck causing slow responses

C Network bandwidth is saturated causing slow responses

D Memory is insufficient causing slow responses

💡 Hint

High CPU usage often means the processor is overloaded.

High CPU usage with slow responses indicates the CPU is the bottleneck limiting performance.

❓ framework

expert

Choosing the Best Tool for Stress Testing

You need to perform stress testing on a web application to find its breaking point under extreme load. Which tool is best suited for this task?

A Apache JMeter, because it supports creating heavy load scenarios and detailed reports

B Postman, because it is designed for API functional testing with simple load

C Selenium WebDriver, because it automates browser actions for functional testing

D JUnit, because it is used for unit testing Java code

💡 Hint

Look for a tool that can simulate many users and measure performance under load.

Apache JMeter is designed for performance and stress testing with the ability to simulate heavy loads and generate reports.

Practice

1. What is the main goal of performance testing in software development?

easy

A. To find spelling mistakes in the user interface

B. To check how fast and stable the software works under heavy use

C. To test if the software installs correctly

D. To check if the software looks good on different screens

Solution

1. Step 1: Understand the purpose of performance testing

   Performance testing measures speed and stability when many users use the software at once.

2. Step 2: Compare options with this purpose

   Only To check how fast and stable the software works under heavy use talks about speed and stability under heavy use, matching the goal.

3. Final Answer:

   To check how fast and stable the software works under heavy use -> Option B

4. Quick Check:

   Performance testing = speed and stability check [OK]

Hint: Performance testing checks speed and stability under load [OK]

Common Mistakes:

• Confusing performance testing with UI or installation testing
• Thinking performance testing checks visual design
• Mixing performance testing with functional testing

2. Which of the following is a common tool used for performance testing?

easy

A. Photoshop

B. WordPress

C. Excel

D. JMeter

Solution

1. Step 1: Identify tools related to performance testing

   JMeter is a popular open-source tool designed for performance testing.

2. Step 2: Eliminate unrelated tools

   Photoshop is for images, Excel for spreadsheets, WordPress for websites, none for performance testing.

3. Final Answer:

   JMeter -> Option D

4. Quick Check:

   Performance tool = JMeter [OK]

Hint: Pick tools known for load testing like JMeter [OK]

Common Mistakes:

• Choosing unrelated software like Photoshop or Excel
• Confusing content management systems with testing tools
• Not knowing popular performance testing tools

3. Consider this scenario: A performance test runs 100 users simultaneously on a website. The average response time is 2 seconds, but 10 users experience 10 seconds delay. What does this indicate?

medium

A. The test is invalid because average time is low

B. The website handles load well with no issues

C. There is a performance bottleneck affecting some users

D. All users have the same experience

Solution

1. Step 1: Analyze the response times

   Most users get 2 seconds, but some have 10 seconds delay, showing inconsistency.

2. Step 2: Understand what inconsistent delays mean

   Long delays for some users suggest a bottleneck or problem under load.

3. Final Answer:

   There is a performance bottleneck affecting some users -> Option C

4. Quick Check:

   High delay for some = bottleneck [OK]

Hint: Look for slow responses in some users to spot bottlenecks [OK]

Common Mistakes:

• Ignoring slow user delays and trusting only average
• Assuming test is invalid without checking details
• Thinking all users have same experience

4. You wrote a performance test script but it always stops with an error after 5 users start. What is the most likely cause?

medium

A. The test script has a limit on concurrent users set too low

B. The website is too fast and closes the test

C. The test tool does not support more than 5 users ever

D. The internet connection is too slow

Solution

1. Step 1: Understand the error context

   The test stops after 5 users start, suggesting a limit reached in the script or tool settings.

2. Step 2: Evaluate options for cause

   The test script has a limit on concurrent users set too low explains a low user limit in the script, which matches the problem. Other options are unlikely causes.

3. Final Answer:

   The test script has a limit on concurrent users set too low -> Option A

4. Quick Check:

   Test stops early = user limit too low [OK]

Hint: Check user limits in script when tests stop early [OK]

Common Mistakes:

• Blaming website speed or internet without evidence
• Assuming tool cannot handle users without checking settings
• Ignoring script configuration for concurrency

5. You want to test a web app's performance under increasing load. Which approach best simulates real user behavior during the test?

hard

A. Gradually increase the number of virtual users over time while running typical user actions

B. Run 1000 users all clicking the same button at the exact same time once

C. Run a single user repeatedly refreshing the homepage for hours

D. Test only the database without simulating user actions

Solution

1. Step 1: Understand realistic load testing

   Real users increase gradually and perform varied actions, not all at once.

2. Step 2: Compare options to realistic behavior

   Gradually increase the number of virtual users over time while running typical user actions simulates gradual load increase with typical actions, matching real use best.

3. Final Answer:

   Gradually increase the number of virtual users over time while running typical user actions -> Option A

4. Quick Check:

   Realistic load = gradual increase + varied actions [OK]

Hint: Simulate real users by increasing load gradually [OK]

Common Mistakes:

• Testing all users clicking simultaneously unrealistically
• Using only one user repeatedly
• Ignoring user actions and testing only backend