Tagged “Exploration”
13 articles
- Troubleshooting"Already in progress for this project" errorTestOptim runs one job per project at a time. See what "already in progress for this project" means, which jobs block each other, and how to proceed.
- Exploration & knowledgeExplore your app to build the knowledge baseStart an AI exploration of your web app in TestOptim, follow its progress live and stop it if needed. The result is your knowledge base.
- Getting startedHow TestOptim works: explore, generate, run, fixTestOptim tests your web app in five steps you start yourself. It explores your app, writes test cases, runs them, reports bugs and re-checks fixes.
- IssuesReview issues found by TestOptimSee where TestOptim issues come from, what severity and status mean, and how to filter, search and open an issue to read the steps to reproduce.
- ProjectsAdd login credentials so TestOptim can sign inGive TestOptim a test account so it can explore and test pages behind your login. Add one credential profile per role and see which one each run uses.
- Exploration & knowledgeReview what exploration found: pages, flows and entitiesWhat the Pages, Flows and Entities tabs on the Knowledge page mean, and how to tell if your knowledge base is good enough to generate test cases from.
- Exploration & knowledgeEdit the knowledge base and improve it with AIFix what the agent got wrong or add what it missed. Edit pages, flows and entities by hand, or describe the change and let AI refine one item for you.
- Integrations & APIRe-explore automatically on every GitHub pushConnect a GitHub repository so each push or merged pull request re-explores your app and refreshes its knowledge. It does not run your tests; use CI for that.
- Getting startedQuick start: find your first bugsGo from a new account to a list of real bugs in five steps. Create a project, explore your app, generate test cases, run a few tests and review the issues.
- Exploration & knowledgeRe-explore your app after it changesRefresh your TestOptim knowledge base after your app changes: clear the old knowledge, start a new exploration, and decide what happens to test cases.
- Exploration & knowledgeEnter a one-time code during explorationIf your app's login sends a one-time code, exploration pauses and emails you a link. Request the code and enter it within 5 minutes, or set a fixed test code.
- TroubleshootingExploration stopped, didn't finish, or found too littleWhy a TestOptim exploration ends early or maps few pages, what "Exploration didn't finish" means, and what to check for logins, unreachable sites and limits.
- TroubleshootingCan't start exploration, test case generation or a test runWhy Generate Test Cases or Start Test Run is greyed out, or you see "archived project", "No knowledge base" or "No test cases found", and how to fix each.