Review and apply exploration proposals

When an exploration finishes, the exploratory agent hands you proposals: new test cases, updates to existing ones and other changes to your suite. You accept, edit or reject each one, then apply the accepted proposals in one step.

Nothing is written to your test cases, plans or variables until you apply. Reviewing and applying need the Editor role or above. Every member can read the results.

Open Explore in the sidebar and click an exploration whose status is Ready for review, or choose Review proposals from its row menu. The Test Cases page also shows a banner, “N test suggestions from the exploratory agent waiting for review”, that links to the latest exploration with proposals still to review.

The exploration’s page has three parts:

• What the agent found: a short summary at the top, in plain English.
• Proposals, Coverage and Site map tabs.
• A bar at the bottom that counts what you accepted, rejected and still have to review, with the Apply button.

A good order is to look at Coverage first to see where the gaps are, then work through Proposals.

The Coverage tab groups your app into feature areas, such as the Toolshop’s product catalog, cart or contact pages, and compares each area with the tests you already have.

Each tile shows:

• the area’s name and its status: Covered, Partial or Not covered
• the paths the area covers, and a one-sentence note from the agent
• how many pages the agent visited there, how many of your existing tests cover it, and how many proposals it made for it

Click a tile to open Proposals filtered to that area. Click the selected tile again to clear the filter.

The Site map tab shows every page the agent visited. While the agent works, pages are grouped by the first part of their path; once the analysis is done, they are grouped by feature area. Each card has a screenshot, the page title, a page type such as Form or Detail, the path and what the page is for. Icons mark pages that require a login, show errors, or were probed in Interact mode.

Click a card to expand it:

Section	What it lists
Actions	The main things a user can do on the page.
Forms	Each form’s fields, with required fields marked *, and its submit button.
States	The states the agent noticed the page can be in.
Errors shown	Error messages visible on the page when the agent was there.
Observed behaviour	What the agent learned by interacting with the page. Only after an Interact exploration.

Open page opens the real page in a new tab. Below the cards, the exploration’s console and network logs appear when any were captured; see Console and network logs.

Every proposal is based on pages the agent visited. On a proposal card, click “N pages as evidence”, or the thumbnail, to jump to the site map with those pages highlighted.

The Proposals tab groups proposals by kind. This is what applying each kind does:

Proposal	What applying it does
New test case	Creates the test case, enabled, with its steps, and adds it to the plan shown on the card.
Update to existing test case	Replaces the name, steps, Expected Outcome, Start Path, login credential and tags of the case it targets.
Disable test case	Switches the case off. It is never deleted.
New test plan	Creates a plan with the listed test cases, plus test cases from this exploration once they are applied.
Add to test plan	Adds a test case to an existing plan.
New variable	Creates a project variable.
Recommendation	Nothing. It is advice to read.

Each card shows the proposal’s title, a category, its feature area, its status and the agent’s reason. A card that changes an existing test case names it after “Targets”. Collapsed test case cards also show the number of steps, the start path and the plan.

Narrow the list with the filters at the top: All areas, All categories (such as Coverage gap, Stale, Duplicate, Edge case or Negative path) and Any status.

1. Click Details on a card to read its steps and expected outcome.

2. Click Accept to keep it, Reject to leave it out, or Edit to change it first.

   The card’s status changes from To review to Accepted or Rejected.

3. To change your mind, click Undo. The card goes back to To review.

To decide on many at once, use the buttons on each group. Accept all and Reject all act only on cards that are still To review. Select all ticks every card in the group that is not applied yet; the bottom bar then shows how many are selected, with Reject and Accept.

Every proposed new test case comes with a plan, shown on the card as “plan” followed by one of your existing plans, or “new plan” followed by a name based on its feature area. When you apply, Testmode adds the test case to that plan. For a new plan, Testmode first looks for a plan with the same name, in case you created one since, and creates the plan only if there is none. If an existing plan was deleted in the meantime, the test case is created without a plan.

A card that shows “no plan yet” has no plan. Click Edit to choose one.

Edit is available on New test case and Update to existing test case proposals while they are To review. To edit one you already accepted, click Undo first.

The editor opens inside the card, with the same building blocks as the test case dialog:

Field	Notes
Name	Required.
Steps	At least one, none empty. Drag to reorder, or click Add Step.
Expected outcome	Required. Accepts variables.
Start path	Optional, such as /checkout.
Tags	Optional.
Login Credential	Optional. The login the test signs in with.
Test plan	New plan… (then type a name, such as Checkout), one of your plans, or No plan (not recommended).

Click Save and accept. Testmode saves your version, marks the proposal Accepted and shows “Proposal updated and accepted”. It is written to the project when you apply.

For wording advice, see Write effective steps.

With Propose updates to existing test cases switched on for the exploration, the agent also flags test cases whose steps no longer match the app, or that look stale.

• Update to existing test case cards compare the test side by side. Details shows Name, Steps in Current and Proposed columns with changed rows tinted, Expected outcome, Start path and Tags. If the test case is not in any plan today, the update also adds it to one, marked “(the case is not in a plan today)”.
• Disable test case cards give the agent’s reason. Applying one switches the test case off, so it stays in your project but is left out of runs. You can switch it back on from the Test Cases page.

Read these carefully. An update replaces the test case you have, so accept it only if the proposed version describes what your app should do.

Some findings are not changes to tests, such as an accessibility or quality issue the agent noticed on a page. The agent reports these as Recommendation cards, each with a high, medium or low priority badge and a short write-up.

• Mark reviewed records that you read it, and the card shows Reviewed. Dismiss sets it aside, and the card shows Dismissed. Mark all reviewed and Dismiss all do the same for every unread recommendation.
• To bring back a dismissed recommendation, click Undo. Marking a recommendation reviewed is final.
• Nothing is written to your project, whichever you choose.
• Recommendations have no checkbox and are never counted by Apply.

The Test Cases banner keeps counting a recommendation until you mark it reviewed or dismiss it.

1. Accept the proposals you want. The bottom bar counts them: accepted, to review and rejected.

2. Click Apply N accepted.

   Testmode writes every accepted proposal to the project and shows “Applied N proposals”, followed by how many test cases, test plans and variables were written.

After applying:

• Applied cards show Applied and an Open link. For test cases it opens the Test Cases page, for plans the plan, and for variables Settings > Variables.
• Applied proposals are final. They have no Undo, can’t be changed back, and are never applied a second time.
• The exploration’s status becomes Applied.
• The bottom bar stays. You can accept more proposals later and apply again.

Good to know:

• Apply writes every accepted proposal in the exploration. Ticked checkboxes do not limit it; they only drive bulk Accept and Reject. Reject or undo anything you don’t want applied.
• Some proposals can be skipped. If a proposal no longer fits the project, for example its target test case was deleted or a variable with the same name now exists, Testmode skips it, says how many were skipped and leaves it Accepted.
• Deleting the exploration later keeps what you applied.