Projects, environments and export

Projects#

The project selector is on the right of the toolbar:

• The first dropdown switches the active project, or creates a new one (New project name…). Tests, Page Objects, Flows, Workspace and Runner always show the active project. Steps currently in the Action History are kept when you switch.
• The second dropdown selects the active environment.
• The gear opens Project settings.
• Switching is disabled while a test is running.

On disk each project is a folder inside Actify-Studio, containing tests\recordings, tests\flows, pages and flows.

Environments#

In Project settings → Environments, click Add and enter a name (e.g. dev) and its base address (e.g. http://localhost:3000). Click the check mark to set the active environment; the trash removes a row. Click Save.

Why it matters: when a test navigates to an address belonging to any of the project’s environments, the saved test keeps only the path (e.g. /login). At run time the path is combined with the active environment’s address. Record once against dev, then switch the dropdown to staging and run the same tests there. Addresses of other sites stay complete.

Rename or delete a project#

In Project settings, edit Name and click Save. Delete removes the project folder after confirmation; the last remaining project cannot be deleted.

Export as a standalone Playwright project#

In Project settings, click Export and choose a destination folder. The app creates a folder named after the project and opens it when done. It contains:

• tests/ — the tests with their steps, Gherkin files and reports (no videos, no recorder files);
• pages/ — the Page Object classes;
• flows/ — the reusable flow functions;
• playwright.config.ts — uses the active environment as base address;
• package.json — scripts test, test:headed, report;
• README.md — setup and run instructions.

The export runs anywhere Node.js is installed, without Actify Studio, for example in a CI pipeline.