Skip to main content

Generate Steps For Your Test Case

Once your test cases are ready, the next step is to generate test steps—the detailed actions AutoTester will follow to test your feature.

This is where AutoTester turns your scenario, like a login flow or an error case, into a real, user-like interaction with your app.

To check whether the test passes or fails, you’ll add an assertion.

An assertion is a checkpoint that tells AutoTester what to look for. Assertions can be a message that appears, a button that changes, or a page that loads.

Adding assertions help confirm that your app behaves the way it should and that the right outcome was achieved.

👇Watch how to generate steps for your testcase

note

Assertions tell AutoTester what success or failure looks like. They’re things like:
✅ “Welcome back” after login
❌️ "Invalid email" when input is wrong

Without a clear assertion, AutoTester can’t verify if the test actually passed even if the steps were followed correctly.

⚠️If You Cannot Review Your Test Cases and Generate Steps​

  • Assertion message not validating properly?
    If the assertion message isn’t validating, make sure the message is correct and visible during the test run. AutoTester can’t detect it if it doesn’t appear or is hidden at that moment.

  • Selector not validating properly?
    Make sure the selector you’ve added matches an actual element in your app’s DOM. Or simply use the browser's dev tools to inspect the element and copy a valid selector.

  • Test steps aren’t generating?
    Revisit your test case and ensure it includes a valid scenario type and expected outcome. If using manual assertions, confirm that all required fields (selector, type, and message) are filled.

  • Test steps generated but incomplete?
    Retry by rephrasing the assertion message for clarity, or add missing steps manually using the “+” option from the existing recording flow.