Assets
Store and organize project files (images, PDFs) that your tests reference by handle.
Last updated
Was this helpful?
⌘Ctrlk
Store and organize project files (images, PDFs) that your tests reference by handle.
The Asset Library is where a project keeps the files its tests reference — baseline screenshots, fixtures, PDFs, and other inputs. Open it from Settings → Assets, under Project.
Each asset has a stable handle. Reference it from a step with asset://<name>, for example asset://login.png. The handle stays valid no matter how you organize the library, so tests do not break when you move files around.
Assets live in a folder tree. Use the breadcrumb to move up and the subfolder list to drill down, and project-wide search to find a file by name across every folder. An asset's full handle is the folder path plus its name (for example asset://baselines/login.png).
Upload images, PDFs, and other fixtures into the current folder. Uploaded files become available to tests by their asset:// handle immediately.
Toggle between list and tile views; tiles show real image thumbnails. Click an image to open it full screen in a lightbox.
Select multiple assets to delete or move them between folders in one action. Deleting an asset breaks any test that references its handle until you re-upload it.
When you import a feature from a PDF, the page screenshots captured during the import are promoted into the library automatically, filed under an Imports/<name> folder so they stay grouped and out of the asset root.
Last updated
Was this helpful?
Was this helpful?