Projects

A project is the unit everything else hangs off. It holds:

• one or more test plans (.jmx)
• the data files those plans read
• the history of every run, with its results

Projects are also how access is granted: you see the projects you have been given access to, and nothing else.

The project page

Results

Every run of this project, newest first. Each row shows when it started, how long it ran, and the peak number of concurrent users it reached. Click a run to open its dashboard.

You can give a run a name — click the name cell and type. This is worth doing when you run variations against each other, since SHOP-20260818-194201 tells you when a run happened but not what it was for. "Baseline, 500 users" is easier to find three weeks later.

Files

Upload, download and delete the project's files. See Test Files.

Run Test

Start a run. See Running a Test.

Choosing which plan runs

A project can hold several test plans. One of them is the project's default — the one used when you don't say otherwise.

When a project holds more than one .jmx, the Run Test tab shows a dropdown to pick between them, and remembers your last choice for that project. From the CLI, pass --jmx:

atlas run -p SHOP --jmx checkout-peak.jmx --servers 5

Creating a project

Projects are created by administrators. If you need one, ask — you'll need to say which account it belongs to, since that determines who can see it.