Projects and test plans#

A project keeps a test plan together with the things it needs: the environments it runs against, the variables those environments set, and the CSV files the plan reads. Without one, every run starts with an upload.

Creating a project#

Projects → New project. A name and an optional description is all it takes. You need the project capability; see Accounts.

Putting a plan in it#

Open the project and add a file of kind Test plan. JMXPress checks that it really is a JMeter plan at the moment you upload it, rather than when somebody tries to run it — a project full of files that turn out not to be plans is only ever discovered at the worst moment.

Every upload becomes a version. The previous ones stay, so a plan that was changed can be compared with what it was and run as it was.

Test data#

Add CSV files as Test data. The bytes are stored exactly as uploaded, so a file exported from Excel on a Windows machine keeps its own encoding rather than being decoded as UTF-8 and filled with question marks.

Binding a CSV to a dataset#

A plan reads its CSVs by name through a CSV Data Set Config. JMXPress reads those names out of the plan and lets you bind each one to a file in the project, optionally per environment — so the same plan can use one set of accounts against staging and another against production.

Open the plan's file and choose Datasets.

Environments and variables#

An environment is a named set of variables: a host, a port, a base path, a credential reference. The Run page offers them, and the plan reads them as JMeter variables.

Keeping them here rather than in the plan means the plan does not have to change to point somewhere else, and a change to the host is made once.

Sharing a project#

A project belongs to the person who made it and to whoever is added to it. Members on the project page controls that.

A project is never visible outside its organisation, whatever is set here; see Accounts and access.

Run history#

Every run started from a project is recorded against it: the plan version, the environment, who started it, when, what the load settings were, and the headline figures afterwards. Execution → History lists them.

That record is what the reports and the APM metrics for a run hang from, so running from a project rather than from an upload is what makes a run findable later.