Project Wizard & Explorer: organize suites, datasets, and outputs cleanly
Tags: project, wizard, explorer, tree, tabs, folders, workspace
What it is Project Wizard/Explorer helps teams organize suites, datasets, and outputs so the workspace stays maintainable at scale. Why it’s needed - Large programs need consistent naming and folder conventions. - Teams need to separate smoke/regression/BAU suites cleanly. - Without structure, automation becomes unreviewable and hard to reuse. Benefits - Cleaner suite organization (by feature area, release, or test type). - Faster onboarding—people can find the right suite quickly. - Supports governance (approvals, reviews, change control). How to use it in WebSureQTool Create a project folder per application/system. Use subfolders like /smoke, /regression, /bau, /api, /ui to keep intent clear. Keep datasets next to suites or in a /data folder with clear naming. Commit suites/datasets into Git if your institution allows it.
