The Project tab
Tests in folders, tags, suites, Pages, Reusable steps, API collections and files — the whole project in one place.
The Project tab is the first tab of the left panel. It shows everything in the active project, in sections: Tests, Suites, Pages, Reusable steps, API and Files. The Filter field narrows every section at once; the open test is highlighted.
Tests
- Click a test to open it in the recorder. Tests not recorded in the app (written by hand, or generated by old Flows) open as code, with a
</>icon. - Hover a test and click ▶ to run it; Run all at the top runs every test (see Running tests).
- The Untitled row at the top holds your unsaved work.
- Next to each test, the result of its last run: ✓ passed, ✗ failed, – skipped. The icon fades when the test changed after that run. Hover it to see the last 10 runs as dots; click the ✗ to open the test on the failed step.
- An amber Flaky badge marks a test that sometimes passes and sometimes fails on the same browser without being changed, or passes only on a retry.
The test menu
Right-click a test:
| Item | What it does |
|---|---|
| Open, Run | Opens the test in the recorder / runs it. |
| Rename | Right in the list. The test keeps its suites, last result and breakpoints. |
| Duplicate | Creates <name>_copy, ready to rename. |
| Delete | Moves the test’s files to the Windows Recycle Bin, so they can be recovered; the test also leaves its suites. |
| Tags… | Labels such as @smoke or @regression, shown next to the name (see Tags). |
| Login test | Marks it as the project’s sign-in test (see Login test). |
| Move to folder | Moves it to a folder. |
| Add to suite | Adds it to a suite, or to a new one. |
| Show steps | Opens its steps in the Output tab, to set breakpoints. |
| Open failed step | Opens it on the step where the last run failed. |
| Show in Files | Shows its files in the Files section. |
Tests can’t be renamed while a run or a recording is in progress.
Test folders
- Organize tests by area (Login, Checkout…), also one inside another: New folder in the section header, then Move to folder from a test’s menu, or drag the test onto the folder.
- Each folder shows how many tests it holds, and a red ✗ if one of them failed its last run.
- ▶ Run folder runs all its tests, subfolders included; the Output tab shows Folder · Checkout.
- Rename, move or delete folders from their menu. Deleting a folder moves its tests one level up: no test is deleted.
- Folders only organize the list: the test files stay where they are. In the exported project a folder’s tests are in
tests/<Folder>/<name>/and can be run by folder.
Tags
Type a tag such as @smoke in the Filter field: the tests with that tag appear, with a button to run them all. Tags work in the command palette too, and stay in the exported project: npx playwright test --grep @smoke.
Login test: sign in once
Login test marks a test as the project’s sign-in test (key icon). In every run it goes first, and the other tests start already signed in — on several browsers and In-App too. If the login fails, the other tests are not run and the Output says so. A test tagged @logged-out starts signed out instead.
Suites
- Create a suite with ＋ in the Suites section, or from a test’s menu with Add to suite → New suite. A test can be in several suites.
- Click a suite to see its tests; ▶ runs it. Rename and delete it from its menu (the tests stay).
- Before the suite and After the suite pick a test to run before the suite’s tests (to prepare data) and one after (to clean up). The “after” test runs even if some tests fail.
Pages, Reusable steps, API, Files
- Pages — each Page with its number of elements and Used in N, a warning when its last Verify found broken elements, and ＋ New Page. See Pages.
- Reusable steps — with Used in N and ＋ to create new ones. See Reusable steps.
- API — the API collections.
- Files — the project folder (closed at first). Click a file to open a read-only preview in the File tab of the dock.
- Right-click: New file, New folder, Rename, Delete, Open Page, Open as Reusable steps, Load into recorder (on tests).
- Drag and drop moves your own files. Tests, Pages and Reusable steps are locked in place, because moving them would break the links between them; on a test, Rename and Delete act on the whole test.
- Videos and the app’s internal files are hidden.
support/actify-data.tsis written by the app: don’t edit it.
Overview and Getting started
The Overview icon next to the search icon opens the project at a glance: active environment, number of tests, suites, Pages and API requests; the results of the last runs (passed, failed, never run); tests that fail or are flaky, one click away from the failed step; Pages with elements no longer found; each suite with its ▶; and the latest runs.
In a new project, Getting started walks you through Record → Save → Organize → Suite → Run → Report → AI agent, each step with an explanation and a button to do it, ticked by itself when done. Hide it and pick it up again whenever you want.
Finding things fast
- Quick open (Ctrl+P, or Ctrl+E while recording): type a few letters of a test, suite, Page, Reusable steps, API request or file — even not next to each other (lgn finds Login). Tabs All / Tests / Suites / Pages / Reusable / API / Files narrow the list; Tab moves to the next.
- Search in project (Ctrl+Shift+F, or the search icon): finds a text inside the steps of every saved test (descriptions, values, URLs, locators, comments, API requests), in Page elements, Reusable steps and API collections. Results open in the Search tab of the dock; click one to open the test on that step. Passwords are never searched or shown.
Something unclear or missing? Write to info@actify-studio.com.