F3 · Swagger UI "Try it out": First: Swagger UI is a **showroom** auto-built from the spec file: instead of reading a car's technical specs on paper in a showroom, you can sit in
Swagger UI is a **showroom** auto-built from the spec file: instead of reading a car's technical specs on paper in a showroom, you can sit in the driver's seat and press the gas — Swagger UI lets you REALLY call every endpoint in the spec with the "Try it out" button, without writing any code, without setting up Postman. So why is this a separate tool when Postman already exists? Because Swagger UI is BORN from the spec itself — while in Postman you must set up a request by hand (you need to already know the endpoint, the fields), Swagger UI reads the spec and auto-prepares the form FOR YOU: it shows in advance which field is required, which values are valid (enum). The Java equivalent is a REPL (`jshell`) — an environment where you can TRY code directly without compiling and packaging. For QA, Swagger UI is the FIRST hands-on test tool in a tester's "understand first, automate later" flow when seeing an API for the first time — deep automation (GROUP G-I) comes AFTER this.
From a Form to a Real Request
Clicking an endpoint in Swagger UI reveals a `Try it out` button. Pressing it makes the fields EDITABLE, and the `Execute` button sends a REAL HTTP request — showing the result (status code, response body) exactly as you would see it in the DevTools Network panel (GROUP E).
Spec → Swagger UI → Try it out → Real Request
🎬 The First API Call Without Writing Code
"Try it out" clicked
The tester opens `/swagger-ui.html` — all endpoints from the spec appear in a visual list.
They press `Try it out` on `POST /api/v1/bugs` — the form is now EDITABLE.
They fill the fields the spec already knows (title, severity) — even enum values are PRE-LISTED.
Pressing `Execute` sends a REAL HTTP request to the server — this is not a simulation.
The lesson — the result (status + body) is the same as what you would see in DevTools; Swagger UI is a "real" first test without writing code, not a nicety.