Test Step Suggestions help you improve your AI-generated test steps by flagging potential issues and offering a better alternative. Suggestions appear automatically when you open a Test Case and update as you manually edit steps.

How It Works

When you open a Test Case, Thunders evaluates your AI-generated steps in the background and displays suggestions where it detects an issue. Suggestions also update when you manually edit a step.

There are two categories of suggestions:

Suggestions you can apply directly

Rewrite: the card shows Consider rewriting this step. Thunders suggests a clearer or more specific version of your step. A suggested update is shown, and you can apply it in one click.
Split: the card shows Consider breaking this step into parts. The step covers too much in one action. Thunders suggests splitting it and shows the proposed steps. You can apply the split directly.
Visual only: the card shows Consider finding this element only visually. This suggestion appears after a failed Test Run, when the step targets an element drawn on a canvas. Under Suggested setting:, the card shows Find the element using only visual processing and the reason. The step text does not change. To learn what this setting does, read how to edit the steps of a Test Case.

Suggestions that require a manual update

Wrong step type: the card shows Consider changing this step type. The step cannot be executed as an AI step but works as another step type. To see what an AI step supports, read Supported AI Actions.
Unsupported action: the card shows This step cannot be executed. The action described isn't supported by Thunders. You'll need to rethink the approach.
Missing context: the card shows Consider being more specific. Thunders doesn't have enough information about your application to suggest an exact fix. A best practice example is provided to guide you. It is not an exact rewrite. Update the step yourself based on the example, or ignore it.

A suggestion card for a step: Consider rewriting this step, with the suggested update and the Ignore and Apply this update buttons

Viewing Suggestions

The lightbulb button, on the left of the bar below the step list, toggles suggestions on and off. You can also use Cmd+S (Mac) or Ctrl+S (Windows/Linux).

The lightbulb button with its Hide suggestions tooltip and the Cmd S shortcut

When suggestions are visible, each flagged step shows the suggestion inline below the step content. Right-clicking a step also lets you view its suggestion directly.

A step with an underlined suggestion and the Right-click to view suggestion hint

Applying or Ignoring a Suggestion

For rewrite, split and visual-only suggestions, two actions are available:

Apply this update: replaces the step with the suggested version, if the card shows one. If the card shows Suggested setting:, it also turns on Find the element using only visual processing in the Advanced settings of the step.
Ignore: dismisses the suggestion.

For all other suggestion types, only Ignore is available. Update the step manually based on the guidance shown. If one of these cards also shows Suggested setting:, it offers Apply this update too, to turn on that setting.

The Consider breaking this step into parts card, with the two suggested steps and the Ignore and Apply this update buttons

The step list after the split is applied, with two new steps in place of the old one

Better Suggestions After Running Your Test Case

Running your Test Case unlocks more targeted suggestions. When a step fails, Thunders analyzes the actual content of your website at that moment and generates suggestions specific to what it found, not only on the step text.

After a failed run, the Consider being more specific card with only the Ignore button

Suggestions on the Test Run page

This works for every failed Test Run, not only for the runs you start from the editor. A run from a Test Set, a Schedule, or your CI pipeline through the API also produces suggestions. Open the failed Test Run: each AI step that has a suggestion shows its text underlined in the steps list. Right-click the step text to view the suggestion, then apply or ignore it as described above.

A suggestion from a Test Run shows only while the step is still the one that ran. When you edit the step after the run, its suggestion no longer shows. When the step changed after the page loaded, clicking Apply this update or Ignore shows Test case modified. Select Refresh to reload the page with the current steps, then check the step again.

When Suggestions Don't Appear

Suggestions are only generated for AI-type steps. They do not appear for:

Steps generated by the Thunders AI Chat, until one of them fails in a Test Run. Thunders assumes these steps are already well-formed.
Steps of a reused Test Case, in a run of the Test Case that reuses it.
Any step other than an AI step.

Troubleshooting

I don't see any suggestions.

Make sure the lightbulb toggle is on. If the button is greyed out, Thunders evaluated your steps and found nothing to flag. Its tooltip then shows No suggestions available.

Suggestions disappeared after I restored a version.

Thunders re-evaluates steps after a version restore. Suggestions will reappear once the new evaluation completes.

I got "Consider being more specific" but I'm not sure what to change.

Use the best practice example shown as a starting point. Add more detail about the element, action, or expected outcome so Thunders can understand exactly what to do.