Test Files

A project holds your test plan and every data file it reads. Upload them whenever they change — this is independent of running a test, and files stay in the project until you replace or delete them.

Uploading

From the Files tab, upload the .jmx and its data files. From the CLI:

atlas files upload -p SHOP ./checkout.jmx ./data/users.csv ./data/products.csv

Uploading a file whose name already exists replaces it.

How files are laid out

All of a project's files live together in one flat folder. There are no subdirectories: whatever you upload lands side by side, and when a test runs, the test plan and its data files sit in the same directory on every load generator.

So reference data files from your plan by a plain relative path:

./users.csv          ✅  recommended
users.csv            ✅  also works

Not by an absolute path, and not through a folder:

C:\Users\me\Data\users.csv      ❌  a Windows path cannot be found on a Linux generator
/home/me/data/users.csv         ❌  absolute paths won't exist there either
./data/users.csv                ❌  the folder structure is not preserved

A bad path silently empties a thread group

If a data file path can't be resolved, every thread in that thread group throws before issuing a single request. There are no failed samples, so the summary shows 0.00% errors and the dashboard simply omits that thread group while the others look healthy.

If a thread group is missing from your results, this is the first thing to check.

How data files are divided

When a test runs on several machines, Atlas divides your data files between them rather than giving every machine the whole file. With 1,000 rows across 5 generators, each gets roughly 200 rows, and no two machines use the same row.

This is what you usually want: a load test where 5 machines all replay the same 200 users isn't testing what you think it is.

Header rows are handled for you. If your plan's CSV Data Set Config says the file has a header, that header is copied to every machine's slice and only the data rows are divided.

Files are divided byte for byte — column order, quoting, embedded commas and newlines all survive exactly as uploaded.

To switch dividing off and send whole files to every machine, use --no-split (CLI) or clear the split option on the Run Test tab.

Which files get divided

.csv and .txt files are divided. .jmx and everything else is copied whole to every machine.

Downloading and deleting

atlas files list -p SHOP
atlas files download -p SHOP checkout.jmx
atlas files rm -p SHOP old-data.csv

In the web interface, the Files tab has a download and a delete action per file.

Before your first run

• Every file the plan references must actually be uploaded. Upload the plan and its data files together.
• Disable GUI listeners left switched on in the plan — View Results Tree, Aggregate Report, Simple Data Writer. They eat memory during a headless run, and Atlas collects results separately.

Full details in Test Plan Requirements.