Skip to main content

Add Assertion Step Manually

To verify whether your test passes or fails, you need to add at least one assertion step before executing the test case. Assertions tell AutoTester what to check for during the test — they define what success or failure actually looks like in your app.

Without an assertion, AutoTester has nothing to validate. So adding this step gives your test a clear pass/fail outcome, not just a list of actions.

👇Watch how to add an assertion step manually in AutoTester

You can add multiple assertion steps within a single test case. Especially when you want to check several things at once like a success message + a page redirect + confirmation button.

note

A good assertion checks for something visible and meaningful, like a success message, confirmation text, or an on-screen change.
When in doubt, keep your assertions simple, easy to spot, and tied to real user outcomes.

⚠️If the Assertion Step Doesn’t Add Properly​

  • Can’t see the ‘Add Assertion Step’ button?
    Make sure you're in the step view and have clicked “See Steps” first.

  • Message not saving?
    Double-check that you've selected both an assertion type and a success/error status.

  • Selector issue?
    Try using a more specific CSS class, ID, or XPath to help AutoTester locate the element.

  • Assertion step added but not visible?
    Refresh the page or collapse/expand the step panel again.

  • Assertion step keeps failing?
    Make sure the message you entered appears visibly in your app when the test runs.
    If the message doesn’t exist or is hidden, the test will fail. Also, ensure the element selector matches what’s visible on-screen at the moment the assertion runs.