Skip to content
Help Center
Browse documentation

Re-explore your app after it changes

Refresh your TestOptim knowledge base after your app changes: click Re-explore, or clear the old knowledge first, and decide what happens to test cases and issues.

Updated 4 min read

To re-explore your app in TestOptim, open Knowledge and click Re-explore. The new run updates your knowledge base and keeps what is already there. To start from an empty knowledge base, use Clear knowledge first.

Before you start

  • Owner, Admin, QA Lead and QA Engineer can clear and explore.
  • Re-exploring uses your monthly page budget again. See Track your usage.
  • The project must not be archived and no other job can be running.
  • A normal re-explore keeps the existing pages, flows and entities. What the agent finds again is updated with what it sees now, so a change you made by hand to such an item can be replaced. Rebuild everything on next run and Clear knowledge now remove the old knowledge. See below.

Steps to re-explore

  1. Open your project and click Knowledge.
  2. Click Re-explore. If the project has two or more credential profiles, the button reads Re-explore as.... Pick the profile the agent should log in with.
  3. Follow the run as described in Explore your app.

If an exploration was stopped or failed part way, whatever it saved is kept. Once it saved at least one page, the badge is Approved and you see Re-explore, Clear knowledge and Improve with AI, so you can simply run again. If it saved nothing, the badge stays Pending and the button reads Start exploration.

Start from an empty knowledge base

  1. Click Clear knowledge at the top right. A menu opens with two options.

    The Clear knowledge menu with Rebuild everything on next run and Clear knowledge now
    Rebuild everything is a checkbox, Clear knowledge now is a button

  2. Click Clear knowledge now. You see "Knowledge cleared. You can start fresh exploration."

  3. The badge goes back to Pending, the counters show 0 and the Start exploration button is back. Nothing has started yet.

    The Knowledge page after clearing: Pending badge, empty counters and the Start exploration button
    Cleared and waiting for a new exploration

  4. Click Start exploration (or pick a profile from Explore as...).

Note

Clear knowledge now deletes the pages, flows and entities. It does not start an exploration and does not touch your test cases or issues.

How often should I re-explore?

Re-explore after changes that add, remove or reshape pages or flows, such as a redesign, a new feature or a changed sign-in. Small copy or styling changes don't need it. Each exploration uses your monthly page budget, so on a small plan don't re-explore for every release.

What "Rebuild everything on next run" does

This is a checkbox in the Clear knowledge menu, not an action. It only takes effect when you click Re-explore afterwards. When the run starts:

  • Generated test cases are deleted permanently and can't be recovered. Test cases you added by hand are kept.
  • All of the project's issues are retired. They are removed from the Issues list and can't be restored.

When the run finishes, it also removes the pages, flows and entities that it didn't find again. If the run is stopped or fails, the old knowledge stays beside what it found, but the test cases and issues are already gone.

Use it when your app has changed so much that the old tests and issues are mostly noise. Then generate test cases again from the new knowledge base.

Warning

If you only want an up-to-date knowledge base, leave Rebuild everything on next run off. Without it, your existing test cases and issues are kept, and re-exploring only updates the knowledge base.

What happens next

  • The new run adds and updates pages, flows and entities. When it finishes you get the Exploration Complete dialog.
  • If you changed your app a lot, open Test cases and review them. Run changed only is a faster way to retest what moved.

Tip

You can have exploration run on every push to your repository. See Re-explore automatically on every GitHub push.