Dataset Editor: data-driven coverage without duplicating suites
Tags: dataset, dataset editor, csv, json, datatable, data driven, parameters
What it is Dataset Editor manages CSV/JSON test data so teams can expand coverage without duplicating suites. Why it’s needed - Duplicated suites create expensive maintenance. - Teams need repeatable inputs for BAU/regression. - Institutions often need controlled test data sets per environment. Benefits - More scenarios with less work. - Cleaner separation of concerns (logic vs data). - Easier environment management (dev/qa/stage/prod-like). How to use it in WebSureQTool Create datasets per environment or per scenario family (e.g., roles, products, regions). Keep datasets in secure storage and avoid placing secrets in plain text where policy forbids it. Use consistent column naming so suites remain reusable.