Creación de una prueba HTTP básica

An HTTP test mimics a browser sending requests to a server — the same calls that fetch pages and assets. It's where performance testing usually begins.

The plan: simulate one user visiting a site. You'll add a Thread Group, fire an HTTP request, and view the server's response — the full mini-loop.

Launch JMeter and you'll see an empty Test Plan in the tree — the home for all your test elements. Rename it via right-click or the Name field.

A Thread Group represents your virtual users — each thread is one user. Add it under Test Plan via Add > Threads (Users) > Thread Group.

Keep it minimal: 1 thread (one user), a ramp-up of 0 (starts immediately), and loop count 1 (runs once). That's a single user, one pass.

The HTTP Request Sampler is what actually sends a web request. Add it under your Thread Group via Add > Sampler > HTTP Request.

Point the request at example.com: protocol https, server name example.com, path /. That targets the homepage.

To see results you need a Listener. Add a "View Results Tree" under your Thread Group — it logs each request and its response in detail.

Save your plan, then hit the green Start button. JMeter fires the request — watch View Results Tree fill in as it runs. 🚀

Nicely done — recall the four pieces you just wired together.

You built and ran your first test: a Test Plan, a Thread Group for one user, an HTTP Request to example.com, and a View Results Tree. This is the foundation for everything next.