Arguments
One or more dashboard paths to import. A path can be either a test path (e.g.
tests/checkout/happy-path) or a folder path using the slash-separated cloud
folder hierarchy (e.g. auth/onboarding). When omitted, every test, module,
and environment in the project is imported.How folder import works
- Folder paths are resolved against the dashboard’s folder tree
case-insensitively.
auth/onboardingmatches the cloud folder namedOnboardingnested underAuth. - All tests and modules inside the folder are imported, including those in any nested subfolders.
- The cloud folder hierarchy is recreated on disk. A test in cloud folder
Auth/Onboardinglands atauth/onboarding/<test-name>.test.yamlrelative to the project root. Folder names are slugified the same way test names are. - If a test or module already exists locally with the same id, it keeps its current on-disk location; existing flat layouts are not reshuffled.