Record here (Local replay)

This section describes operations when adding or changing steps to an existing scenario.

1. Overview

Autify's ability to create "scenarios" by recording is attractive, but to add a step, you must follow the "scenario" until the screen you want to add appears.

If the position you want to add is later in the "scenario," you will need to advance through the screens, which is very time-consuming. The "Local Replay" function solves this problem.
When you start "Record here," the operation automatically proceeds to the point you want to add, which is called "Local Replay" or "Replay".
Also, since a local replay is not a test run, it does not consume any number of executions or credits.

2. Basic Operation

2-1. Basic Operation

For example, to add a step between steps 1 and 2 of the following scenario, click the "+" between steps 1 and 2.

After that, select "record here" to launch the recording window and proceed automatically up to step 1.

The following dialog will appear while the local replay is running.

If the operation up to the point where you want to add a step is successfully replayed, the following dialog will be displayed, and the operation such as clicking and inputting will be recorded as in the case of new recording, and you will be able to add various assertions.

For more information on how to deal with interrupted local replays, please refer to the article on what to do in case of an error at the bottom of this page.

2-2.How to abort Local Replay

How to abort

If you wish to abort Local Replay for whatever reason, you can do so by clicking [Abort and proceed manually] in the dialogue.

How to record after aborting Local Replay

Immediately after aborting, the following "Aborting replay" message will appear. You cannot record any actions while this message is visible, so please wait until it disappears.

Once the message disappears, manually perform all the actions, such as clicks and going to another page, until just before the step you want to record.
When you are ready to resume recording, click on the pause icon on Autify Recorder (second button from the left). You can now record new actions.
A message on Autify Recorder will tell you where the new step will be inserted (In the figure below, new actions will be recorded after step 3).

By enabling recording, you can record actions just like when you record a new scenario. As shown in the figure below, a blinking red ● indicates that recording is enabled.

2-3. How to check the status during local replay

The window displayed during replay shows the number of steps currently in operation (7 in the figure below) and the number of steps to be replayed (8 in the figure below).
The number of steps to be replayed includes the number of steps in the step group. Therefore, if Step 1 is "Record Here" after Step 4 in a scenario that includes a Step Group with 3 Steps, the number of Steps to be replayed will be displayed as 8 instead of 4, as shown in the figure below.

2-4. If you do not need "Local Replay"

If you do not need the automatic operation by "Local Replay" for some reason, such as "there are many steps to the part you want to add and you want to omit the intermediate steps," please select "Record here without replay" instead of "Record here" to start additional recording.

3. What "Local Replay" does not allow you to do and what you need to be aware of

Local Replay is a feature to help update "scenarios", not a test run. Therefore, it may behave differently from a test run or may fail, and Local Replay cannot be used in place of a test run.

3-1. Actions and functions that are not performed during local replay

3-1-1. steps to be ignored

• Assertion Step
• The "confirm that the appearance of the target is unchanged" step. 2.

3-1-2. Steps that result in errors

• File Upload Step
• The step where the target element was not found in the operation step (click or input)
• The step in which the content described in the JS step is inappropriate. 3.

3-1-3. Actions not performed

• Element update (Elements explored during replay are not automatically maintained for the scenario)

3-2. behavior different from test execution

3-2-1. Detailed Timing

The timing to determine the completion of page loading and the waiting time before and after the operation are different. Because replay is fast, an operation may fail because it is performed in the middle of loading. In this case, add a wait step before the step that fails and replay it again. Or, for the steps that do not work, operate manually and "Continue Replay/Retry" to proceed to the target screen.

3-2-2. Site Compatibility

The replay process may not work due to compatibility issues with the site.
In this case, proceed to the target screen manually. 3-2-3.

3-2-3. time zone

Local replays are executed in the time zone of the customer's terminal where the replay will be executed.

3-2-4. Custom Host Name

During replay, the custom host name set in the workspace will not be resolved.

4. What to do when an error occurs

If an error occurs during local replay, the following dialog appears

Local replay can be restarted or interrupted in any of the following ways

4-1. Retry

Click "Retry" in the upper right corner of the dialog screen to retry replaying a failed step.

4-2. Abort

You can interrupt a local replay by clicking "Abort" in the lower left corner of the dialog screen. Refer to "How to record after interruption" in 2-2 above to continue recording in the subsequent steps.

4-3. Continue

Click "Continue" in the lower right corner of the dialog screen to resume replay from where you left off. Ignore the failed step or manually perform the operation equivalent to the failed step to resume replay.
When manually performing an operation equivalent to the failed step, the replay dialog can be moved, so move it accordingly before performing the operation.

Errors during local replay are also described in this article.

5. Others

The bar that appears at the top of the browser when "Local Replay" starts ("Autify Recorder" started debugging this browser message) may appear during recording. This is due to the Chrome browser's display. If necessary, close it with the X button before recording starts.