Skip to main content

Review Test Case Steps And Execute

Reviewing gives you full control over each test action in the test flow. You can edit input values, update selectors, or add actions, all without needing to re-record the entire flow.

Remember: When reviewing steps, new or modified steps will show a star ✱ icon. Be sure to check their input values and verify that the associated XPath or selector matches what’s in your app.

This ensures your test reflects how a real user interacts with the app. Also ensures it works reliably across different environments or input scenarios.

👇Watch how to review test case steps and execute in AutoTester

note

Editing steps are especially helpful when you're reusing a test across different environments (e.g., staging vs production) or input scenarios. Make sure to update inputs or selectors if your app's behaviour changes.

⚠️If Something Doesn’t Work During Review or Execution​

  • XPath not saving?
    Make sure you're editing the right part of the step (e.g., XPath vs CSS selector) and that the element still exists in your app. Or simply use the browser's dev tools to inspect the element and copy a valid Xpath.

  • Steps running, but assertion failing?
    Re-check the validation message and selector tied to your assertion step.

  • No steps appear after clicking ‘Run’?
    Make sure you have your app open in the same browser tab and that the extension is active. Or simply stop the execution and re-run.

  • Assertion step failed even after editing?
    Check if the expected message or element is visible at the exact moment the assertion runs. Also, verify that the selector hasn’t changed after your last UI update.