Performance testing tools overview in Testing Fundamentals - Build an Automation Script

Basic Load Test Using Apache JMeter

Preconditions (2)

Step 1: Open Apache JMeter

Step 2: Create a new Test Plan

Step 3: Add a Thread Group with 10 users and loop count 5

Step 4: Add an HTTP Request sampler targeting the test environment URL

Step 5: Add a View Results Tree listener

Step 6: Start the test

Step 7: Observe the results in the listener

✅ Expected Result: The test completes without errors, and the response times are recorded in the listener showing successful requests

Automation Requirements - Apache JMeter

Assertions Needed:

Verify all HTTP requests return status code 200

Verify average response time is below 2 seconds

Best Practices:

Use Thread Group to simulate concurrent users

Add assertions to validate response status

Use listeners to capture and analyze results

Avoid hardcoding URLs; use variables for flexibility

Automated Solution

Testing Fundamentals

Test Plan:
  Thread Group:
    Number of Threads (users): 10
    Loop Count: 5
    HTTP Request:
      Server Name or IP: example.com
      Path: /api/test
    Response Assertion:
      Field to Test: Response Code
      Pattern Matching Rules: Equals
      Patterns to Test: 200
    Summary Report Listener

# Explanation:
# This JMeter test plan simulates 10 users sending 5 requests each to the target URL.
# The Response Assertion checks that each HTTP response returns status code 200.
# The Summary Report Listener collects metrics including average response time.
# This setup helps verify the server handles load and responds correctly within expected time.

This test plan uses Apache JMeter to simulate multiple users accessing a web service.

The Thread Group controls how many users and how many times they send requests.

The HTTP Request sampler defines the target URL to test.

The Response Assertion ensures the server responds with status code 200, meaning success.

The Summary Report Listener collects performance data like response times.

This setup helps check if the server can handle the load and respond quickly.

Common Mistakes - 3 Pitfalls

Not adding assertions to verify response status codes

Using too few users or loops, not simulating real load

Hardcoding URLs directly in HTTP Request sampler

Bonus Challenge

Now add data-driven testing with 3 different URLs to test performance on multiple endpoints

Show Hint