[{"data":1,"prerenderedAt":21},["ShallowReactive",2],{"blog-post-en-qa-browser-reset-workflow":3},{"slug":4,"lang":5,"title":6,"summary":7,"date":8,"tags":9,"tag_slugs":13,"thumbnail_url":17,"translations":18,"body":19,"asset_base":20},"qa-browser-reset-workflow","en","Build a Browser QA Reset Workflow Step by Step","Learn how to build a no-code Broma workflow that resets browser-based QA test data between regression runs, with safe steps and verification.","2026-11-12",[10,11,12],"browser automation","qa testing","no-code workflow",[14,15,16],"browser-automation","qa-testing","no-code-workflow","https:\u002F\u002Fblog-api.bromaapp.com\u002Fapi\u002Fblog\u002Fposts\u002Fqa-browser-reset-workflow\u002Fthumbnail.svg?lang=en",[5],"## Why QA Test Data Resets Matter\n\nRegression tests are only trustworthy when each run starts from a known state. A smoke test can pass, but if it leaves an order marked paid or a user profile changed, the next test can fail for the wrong reason.\n\nA browser workflow can reset that state before tests run. Broma runs on the user's own computer, so the QA tester controls the profile. No public API is needed.\n\n### Pick a Dedicated Reset Target\n\nCreate a test account or sandbox dataset. Keep it separate from real data. Use a dedicated Broma browser profile so cookies and logins do not leak between tests.\n\n- New profile for QA automation.\n- Use test credentials.\n- Reset only fields the workflow owns.\n\n## Step 1: Open the Page in the Right Profile\n\nStart from a clean Broma profile. Open the application under test.\n\n1. Open Broma.\n2. Go to Profiles.\n3. Create a new profile for QA.\n4. Add the test login.\n5. Open the target page.\n\n## Step 2: List the State the Workflow Must Reset\n\nDescribe the task in plain language. For example: clear the customer phone number, set invoice status to draft, remove test line items.\n\nWrite the steps in execution order.\n\n- Open Settings.\n- Open Test Data.\n- Clear field.\n- Type value.\n- Click Save.\n\nIf the reset touches multiple pages, split into sub-steps or use a loop if the same action repeats.\n\n### Choose Selectors That Survive Page Changes\n\nAvoid deeply nested CSS selectors. Prefer stable attributes.\n\n- `data-testid`\n- Accessible name\n- Stable text\n\n```\ndocument.querySelector('[data-testid]')\n```\n\nIf Broma uses JavaScript expressions, keep them short.\n\n## Step 3: Add Reset Actions and Waits\n\nUse open, click, type, wait, branch, loop, read text, screenshot.\n\nExample sequence:\n- Open `\u002Fsettings`\n- Wait for `[data-testid=test-data]`\n- Clear `[data-testid=phone]`\n- Type `555-0100`\n- Select `[data-testid=status]`\n- Choose `draft`\n- Click `[data-testid=save]`\n- Wait for `[data-testid=success]`\n\nIf the reset repeats over rows, use a loop with an explicit count. Keep the count explicit.\n\n### Add Branching for Known States\n\nIf save fails, branch to screenshot and log.\n\n```\nif error then screenshot\n```\n\n## Step 4: Verify the Reset\n\nRead text after save. Take screenshot. Check expected value.\n\n```\ntextContent `[data-testid=status]`\n```\n\nIf mismatch, branch.\n\n## Step 5: Run Before Regression and After Failures\n\nAdd workflow to pre-test checklist. Run manually or scheduled. Review run logs.\n\nRunning this workflow manually before each regression is simple. For a solo operator, schedule it or run it from a saved checklist. For a team, keep one shared reset flow and version it. The goal is not to test the reset itself forever, but to remove noise from the real regression.\n\n## Building the Reset Flow Step by Step in Broma\n\nStart in the Broma app and describe the reset in plain language. The agent or manual builder should create steps in order.\n\n- Open the target page.\n- Click the settings or admin area.\n- Clear fields.\n- Type known test values.\n- Select statuses.\n- Save.\n- Wait for success.\n\nThen add checks. The flow should read text after save and take a screenshot. If the expected state is not present, branch to a failure path.\n\nUse plain language for each action. For example, type means clear then type or set value. Select means choose option. Wait means pause until element exists or condition is true. Branch means if error then screenshot and stop or continue.\n\n## Handling Async Saves\n\nBrowser saves can be slow. A reset flow should not click and immediately read.\n\n- Wait for the save button to be enabled.\n- Wait for a success element.\n- Wait for the status text to update.\n\nThis prevents flaky resets.\n\n## Using Profiles for Isolation\n\nKeep QA reset profiles separate from daily automation profiles. Each profile can have its own cookies, logins, proxy, and extensions. For QA, use a dedicated test profile.\n\n## Why Reset Flows Break\n\nBrowser pages change often. A reset flow can fail when selectors move, async calls finish late, or saved state differs.\n\n- Use waits for elements.\n- Use stable selectors.\n- Branch on failure.\n- Verify.\n\nStart with the smallest reset that removes ambiguity. If the app stores state in local storage or a backend, clear it through the browser only when the product allows. Avoid touching production accounts.\n\n## How to Describe a Reset in Plain Language\n\nWrite instructions like:\n\nOpen the settings page.\nWait for the test data panel.\nClear the phone field.\nType 555-0100.\nSelect draft.\nClick save.\nWait for success.\n\nKeep one action per line.\n\n## How to Check the Reset Without Guesswork\n\nAfter save, read text. Take screenshot. Compare expected. If mismatch, branch to failure path.\n\n```\nread text status\nscreenshot reset\n```\n\nRead text can return the current status. Screenshot can capture evidence. Use these in the flow before branching. This makes the reset auditable.\n\n## Real-World Example: Resetting an E-Commerce Test Order\n\nBefore a release regression, a QA tester needs a clean order state. The workflow opens the admin dashboard, finds the test order, resets status, quantity, and price, then saves.\n\n- Open Orders.\n- Open test order.\n- Set status to pending.\n- Set quantity to 1.\n- Set price to 0.\n- Save.\n- Verify.\n\nThis avoids flaky tests caused by leftover data. For example, before testing checkout, reset cart to one item, clear coupon, set shipping to test zone. Then run smoke test. The reset flow should be reusable for different test cases by changing typed values.\n\n## When to Use a Reset Workflow\n\nUse a reset workflow when tests depend on clean state. Examples include form fills, order status checks, user profile edits, and dashboard data. Do not use it to bypass security or test real users.\n\n## Troubleshooting Broken Resets\n\n- Selector changed: update selector.\n- Save button disabled: wait for enabled.\n- Wrong profile: check profile.\n- State not cleared: clear via JS if safe.\n\n## Checklist for Reliable QA Reset Flows\n\n- Dedicated profile.\n- Stable selectors.\n- Explicit waits.\n- Branch on failure.\n- Verify state.\n- Log runs.\n\nKeep reset actions separate from test assertions. The reset flow should set state. The test should verify behavior. Mixing them can make failures harder to read.\n\nReview run logs after failures. A failed reset often means a wait was missing or a selector was wrong. Add the missing wait and rerun.\n\n## Keep the Reset Workflow Useful\n\nSave steps, name clearly, version. Document expected state. Review run history. This makes the reset repeatable for solo operators and teams alike.\n","https:\u002F\u002Fblog-api.bromaapp.com\u002Fapi\u002Fblog\u002Fposts\u002Fqa-browser-reset-workflow\u002Fassets",1794729620685]