โ† Back to 30-Day Challenge

๐Ÿ—๏ธ Foundations ยท Days 1โ€“6

Day 1: Hello, Load

Objective

Install your chosen tool, record or script a single GET request, and run it once.

Scenario

Pick any public endpoint or your own dev server. Send one request with timing enabled. Look at the response time. You are already performance testing.

Metrics to Watch

response time (ms)status code

When It Clicks

A test is just a measured request - you can already see latency.

Solution

In JMeter: add a Thread Group (1 user, 1 loop), add an HTTP Request sampler pointing at your endpoint, add a View Results Tree listener, and press Run. In k6: write `export default function() { http.get('https://your-endpoint'); }` and run `k6 run script.js`. The response time in the results table is your first latency measurement.

Reflection

What surprised you about the response time of a single request?

Deliverable

A saved script for one GET endpoint.

โš ๏ธ Never run load tests against infrastructure you do not own or have explicit written permission to test. Always use a dedicated test environment. Unauthorized load injection can cause outages, trigger legal liability, and violate terms of service.