Resource
Offline-first storage
The runner, the importer, the report generator — all of it works without an internet connection. The browser is the database. The extension is the application server. There is nothing else to configure.
Where things live
- Test cases — imported rows are stored in extension storage.
- Runs — every status change is written immediately, so a crash never costs more than the last keystroke.
- Screenshots — saved as base64 blobs, addressable by run + step.
- Defects — stored alongside their evidence references.
- Settings — shortcuts, theme, report branding.
Why it matters
- Run a regression suite on a plane or in an air-gapped lab.
- Test internal tools without exposing data to a SaaS vendor.
- No outage anywhere else can stop you mid-execution.
- Audit conversations are simple: nothing left the device.
Backups & portability
Because the data is local, you control the backup strategy. Use the built-in Export run action to save a JSON snapshot of any run (cases + statuses + screenshots + defects) and re-import it later or on another machine.
Capacity
Chrome's extension storage is generous, but screenshots add up. A status indicator in Settings → Storage shows current usage and lets you delete old runs in bulk to reclaim space without affecting current work.
No sync, by choice
QA Workspace deliberately does not sync runs across devices. Sync requires a server, and a server breaks the offline-first promise. Use the export action when you need to hand off work.