Organize tests with projects and folders

Two structures keep your tests tidy:

• A project is the top-level container. Everything — tests, folders, test sets — lives inside a project.
• A folder is a tree inside one project. Folders can nest as deep as you want.

A test lives in exactly one project, and (optionally) one folder within it. If you want cross-cutting labels that ignore this hierarchy, use tags instead.

Create your first project

A new account starts with no projects — nothing is auto-created, so your first move is to make one.

1. Click the “New project” button (the + near the project picker in the Tests explorer).

2. Give it a name (required, up to 100 characters) and an optional description.

3. Save. The new project becomes your active project right away.

Switch between projects with the picker dropdown at the top of the explorer. Your choice is remembered per browser, so you land back where you left off.

Folders

Folders organize tests within the active project. Use the New folder button to create one at the root, or add a subfolder from a folder’s own menu — there’s no nesting limit, so mirror however your app is structured.

Rename or delete a folder from its context menu or the Folder Properties panel. To move a folder, drag it onto another folder (or onto the “move to root” zone) in the tree.

Move a test into a folder

Drag the test onto a folder in the explorer tree. Dropping it on the project (or the root zone) takes it out of any folder. Select several tests first to move them as a group.

Tests stay in their project

Moving a test changes its folder, not its project. There’s no in-app way to move a test from one project to another today — if you need a test in a different project, recreate it there (or export it and import the file).

Deleting a project — read this first

Deleting a project is permanent and asks you to type the project name to confirm. What happens to its contents is worth knowing:

• Tests and test sets are not deleted. They’re detached from the project and become unassigned — you keep them, they just no longer belong to a project.
• Folders are deleted. The folder tree belongs to the project, so it goes with it. The tests that were in those folders survive (now folder-less); the folders themselves don’t.

Deleting a folder (rather than the whole project) works the same way for its contents: subfolders are removed, the tests inside them survive and become folder-less.

Note

There’s no “you must keep at least one project” rule — you can delete your last project and land back on the empty state, ready to create a fresh one.

Projects and your team

Projects belong to your organization, not to you personally. In a solo workspace that’s just you. In a team org, who can see and change a project depends on each member’s role — see Organization roles and permissions.

Limits

Projects, folders, and test sets are all unlimited on every plan. The only structural caps are inside a single test (variables and data rows) — see Plan tier limits.

Related

• Organize and run tests with tags — cross-project labels
• Test sets — runnable groups within a project
• Organization roles and permissions — who can edit what in a team