BlinqIO Documentation

Reuse Existing Steps and Scenarios in the Recorder ​

You can reuse steps from previously recorded tests or AI Test Engineer scenarios in the Recorder. Reusing existing steps and scenarios reduces duplication, simplifies maintenance, and promotes consistency across your test suite.

reuse-step

Reusing Steps in Recording Mode ​

In Recording Mode, running an existing step or scenario adds it to the current test being recorded. This is useful when your current test reuses actions from previously recorded tests.

Example Use cases

  1. Reuse the "Login" step.

    Avoid re-recording the login process across multiple tests. This helps standardize the login flow and simplifies updates if the login logic changes later.

  2. Reuse the "Navigate to Dashboard" step.

    Ensure consistent navigation when multiple tests require starting from the dashboard.

To reuse an existing step or scenario in Recording Mode:

  1. Navigate to the page where you want to reuse a step or scenario.

  2. Ensure the application is in the correct state to receive the reused steps and actions.

    Example:

    • Existing Step - Login: Dismiss cookies, enter username, and enter password.

    • If the cookies popup has already been dismissed, the reused step might fail as the popup is no longer displayed.

  3. In Recording Mode, click the Add and run existing step/scenario icon at the bottom left. reuse-1

  4. Find the step/scenario you want to run. You can filter steps by name to narrow down the search.

    • If the step includes parameters, you will have the option to modify parameter values before running the step.
    • You can Add, Run or Play and Add step.

    existingStepParams

  5. The step will execute and be added to your current recording.

    Recorder

Reusing Steps in Paused Mode ​

In Paused Mode, running an existing step only executes it without adding it to the current recording. This is useful when you want to run steps but don't need to include them in the recorded test.

Example Use cases

  1. Run the "Logout" step in paused mode to reset the application state without adding it to the recorded test.

    • The user may need to log out for verification purposes but doesn't want this action recorded in the current test.

  2. Run the "Clear Cache" step in paused mode to ensure a clean testing environment without adding it to the current recording.

    • The user wants to clear the cache during testing but doesn't need this action in the final test flow.

reuse-step-pause-mode

NOTE

Don't forget to Generate code and Save after finalizing all your steps.