Workspaces: what's inside and how to back it up
Tags: workspace, projects, reports, runs, drivers, config
What it is A Workspace is the folder-based ‘automation home’ that stores suites, datasets, run outputs, logs, and configuration. Why it’s needed - Teams need a single, governable location for automation artifacts. - Backups and retention are easier when everything is folder-based and explicit. - Separating Workspaces avoids cross-project pollution and conflicting drivers. Benefits - Simple backups (copy the folder). - Cleaner audits (clear evidence trail per project). - Works well with network shares, encrypted volumes, and enterprise storage policies. How to use it in WebSureQTool Recommended structure (conceptual): - /projects (suites + datasets) - /drivers (Chrome/Edge drivers) - /runs (run.json, junit.xml, etc.) - /reports (report.html and related assets) - /logs (execution logs) Backups: snapshot the Workspace folder on your normal cadence (per sprint/release is common).
