Skip to content
Docs
Arcus
Popular questions
↑↓ to navigate↵ to selectesc to close
Book a demo

App knowledge graph

The App knowledge graph is the map Arcus builds of your application by walking through it in a browser. It shows every feature, page, and control Arcus has seen, and how much of each one your test cases cover. Test cases Arcus writes afterwards are based on screens it has visited.

The graph also lists orphan nodes: controls and journeys Arcus observed in the app that no test checks yet. Each orphan node is a gap in your coverage. Send Arcus to explore an orphan node, and it drafts the missing test cases.

The graph has 4 levels. Open a node to expand the level below it in place.

LevelWhat it isExample
FeatureAn area of the app, grouped by what it doesCheckout
PageA screen inside a feature. The page Arcus starts from is marked Entry point.Payment page
ComponentA group of related controls on a page, called a Control group in the orphan node listCard details form
ElementA single controlPay now button

Several features expanded at once, showing pages, the components inside them such as Form and Payment method toggle, and individual elements such as Credit / Debit Card and PayPal

Each feature shows its pages, its covered and total elements, and its open gaps, for example “3 pages · 0/35 · critical · 10 open”. Each page shows its open gaps, and when expanded, its states and elements, for example “2 states · 22 elements · 5 open”. The most important features are marked critical.

Explored in the graph means covered by a test case, not visited. Right after a crawl, the graph can show 0% explored even though Arcus has walked many screens. The percentage rises as test cases that touch those elements are automated.

Navigation, headers, and footers that repeat on most screens are counted once, as Shared UI.

The Travel Search & Discovery feature expanded on the graph, showing its pages: Hotel Search Results, Landing (marked Entry point), Stay Search Results, Hotel Detail, and Flight Search, each with its coverage and open gaps

The first time you open the graph, it reads “Arcus has not seen your app yet”.

QI Home with the App knowledge graph button, beside Context Management, highlighted

  1. In the left navigation, open QI Home.

  2. Click App knowledge graph.

    The App knowledge graph empty state, reading Arcus has not seen your app yet, with the What a crawl finds video and the Point Arcus at your app form highlighted

  3. In Application URL, enter the address of the app you want to map, for example https://staging.example.com.

  4. If the app needs a sign-in, turn on This app requires a login, then enter a Username and Password for a test account. Arcus signs in first, then explores everything behind it.

  5. (Optional) In Anything else Arcus should know?, describe test data to use and areas to leave alone, for example “Do not complete real payments.”

  6. Click Start exploring.

The Point Arcus at your app form with an application URL, and the This app requires a login toggle with the Username and Password fields highlighted

Arcus opens a browser on the app and starts mapping it. The Exploring panel on the right shows each action as it happens, the number of screens found, and the time used against the crawl’s 20-minute budget. Screens appear on the graph when the first pass finishes.

When the budget runs out, Arcus finishes its current pass and stops. The panel shows that the time limit was reached and how many screens were found. Click Hide to close the panel.

After the first crawl, a dialog introduces the 2 views of the graph. Click Open the map to see the Map view, or Got it to stay on the Graph view.

A single crawl rarely reaches every screen. To extend the graph:

  1. Click Explore more at the bottom of the graph.
  2. Enter the Application URL again.
  3. In Anything else Arcus should know?, say what to focus on, for example “Explore more of the booking and payment pages.”
  4. Click Start exploring.

Arcus keeps everything it has already mapped and looks for screens it hasn’t seen. New features, pages, and orphan nodes are added to the graph. Explore more is unavailable while a crawl is running.

The graph has 2 views. Switch between them with Graph and Map at the top.

  • Graph shows how the app is connected. Features are boxes, and lines show which controls lead from one feature or page to another. Use Expand all and Collapse all to open or close every node.
  • Map shows how much of each area is covered. Each feature is a tile sized by its number of elements and colored by coverage, from below 40% to 80% and above. Each tile lists its pages with their coverage. Click a tile to draw its connections to other features. Shared UI has its own strip at the bottom.

Open a page from the Map view to see its COMPONENT TEMPLATES: one card for each region of the page, named after that region, with the elements inside it and how many are covered. Controls that don’t belong to a region are listed under Ungrouped controls, and shared regions such as the top navigation are marked as shared UI. A breadcrumb at the top, for example The whole app > Travel Search & Discovery > Hotel Search Results, takes you back up a level.

The Hotel Search Results page in Map view, with component cards for Filter sidebar, Hotel listings and pagination, Search criteria bar, Top navigation header, and Ungrouped controls, with the COMPONENT TEMPLATES coverage count highlighted

To see the graph for one QI Home session, select it in Showing. The default is All runs. With a session selected, coverage reads “of this run explored” and the list shows only that session’s orphan nodes.

Click Legend for what each shape, color, and line means:

  • Nodes: Feature, Page, Component, and Element.
  • Elements: Covered, Unexplored, and Picked to explore.
  • Connections: Navigation (one control leads to the other end), Traced path, and Connected to what you point at.

The graph with the Legend open, listing node types, element states, and connection types

Click an element to open its details: its status, such as UNEXPLORED, the feature and page it belongs to, and the test cases that cover it. An element that no test case touches reads “No test case covers this element yet.”

The panel on the left lists orphan nodes, with the overall coverage at the top, for example “1% of the app explored · 2 of 339 elements”. Hover over the info icon beside ORPHAN NODES for a short definition. You can also open the list from a QI Home session: on the session overview, click View orphan nodes on the App knowledge graph card.

Each orphan node is one of 2 kinds:

  • Journey: a flow through the app, such as creating an account and reaching the dashboard.
  • Control group: a set of controls on one page, such as a filter sidebar.

Orphan nodes are sorted into 4 tabs:

TabWhat it holds
ActiveGaps no test case covers yet
ExploringGaps Arcus is exploring now
ExploredGaps an exploration has covered
DismissedGaps you’ve marked as not needing a test

The list is ranked by feature importance. To narrow it, click Filters and filter by Element type, Identified by, Feature, Page, or Kind.

Opening a node on the graph also limits the list to that node. The list then reads “Showing” with the node’s name, followed by a link that counts the orphan nodes outside that node.

Click an orphan node to expand it. It shows its status, such as “Observed, not walked”, and the page where Arcus saw it. Expand Evidence to see how Arcus identified it. For a journey, it also shows the route through the app and outlines it on the graph.

Click Traced path on an expanded orphan node. The panel shows:

  • KNOWN PATH: how Arcus can reach the node. No known path means the graph hasn’t found a route to it yet.
  • WHAT AN EXPLORATION WOULD DO: the steps Arcus would take and the test cases it would draft.
  • WHY IT WAS FLAGGED: why Arcus thinks the node needs a test.

Exploring sends Arcus to the node in a browser. Arcus uses its controls, records what opens, and drafts test cases for anything that has none.

  1. Click an orphan node to expand it.

  2. Click Explore. A dialog shows how many gaps will be explored and in how many runs. Gaps on the same page share one run.

    The Explore dialog for one gap on the Checkout Payment page, with Start campaign highlighted

  3. Click Start campaign.

  4. If Arcus asks where to start, enter the Application URL and click Start campaign again.

The node moves to the Exploring tab, first as Queued under “WAITING FOR A SESSION”, and then Running. Up to 5 runs happen at a time. Click Watch to follow the run in the side panel.

You are charged only for gaps Arcus verifies. Nothing is charged while a campaign waits for an answer from you.

When the run finishes, the node moves to Explored with a status such as “An exploration walked this node and saved 1 case, awaiting acceptance.” Click Path & cases to see what the exploration found, the test cases it saved, and the full run log.

Test cases from an exploration wait in Context Management until you add them to a sprint or an Adhoc session for review.

  1. In Path & cases, under SAVED TEST CASES, click the test case. Context Management opens on the Unlinked Test Cases tab, where the case is labeled “From gap exploration”.
  2. Click Link.
  3. Select the Project.
  4. Under Link to, select Sprint and choose the sprint and story, or select Adhoc and choose an existing session. To start a new session, click Create New Adhoc Session.
  5. Click Link. The case moves to Linked Test Cases.

Review the case in that session as you would any generated test case. See Generate test cases.

Coverage on the graph rises once the case is automated and saved to the library. To automate it, open the case in the session and click Learn with Copilot. The first time you open its Automated Steps tab, a dialog explains agentic learning. Click Start Agentic Learning to continue. Copilot runs the steps live, adds the screens it visits to the graph, and writes the automated steps. When learning completes, click Save and Run to save the case to the library with its automated steps. See Copilot.

A single automated case can cover more than one orphan node. Nodes it covers along the way move to Explored with the status “An exploration has walked past this node and its coverage is recorded in the knowledge graph.”

Dismiss a node when it doesn’t need a test.

  1. Click the orphan node to expand it.
  2. Click the arrow beside Explore.
  3. Under Dismiss as, select a reason: Intentionally untested, Out of scope, False positive, or Dead code.

The node moves to the Dismissed tab straight away, marked Dismissed. A dismissed node can’t be moved back to Active. To test it after all, open it on the Dismissed tab and click Explore anyway.

  1. Select the checkbox beside each orphan node you want to explore. To select every node on the tab, select the checkbox beside RANKED BY FEATURE IMPORTANCE.

  2. In the bar at the bottom, click the explore button, for example Explore 12 gaps.

    Three journey orphan nodes selected, with the select-all checkbox and the bar reading 3 gaps selected and Explore 3 gaps highlighted

  3. Click Start campaign.

Gaps on the same page share one run, so exploring them together costs less than exploring them one at a time. To clear the selection, click the close icon in the bar.

  • Each crawl has a 20-minute budget. Large apps need several Explore more passes.
  • Arcus can only map screens it can reach. Disabled links, screens behind data it doesn’t have, and actions you asked it to avoid stay unexplored.
  • Coverage counts test cases that touch an element. A crawl or exploration on its own doesn’t raise coverage until its test cases are automated and saved to the library.

Explored means covered by test cases, not visited. A crawl maps the app but doesn’t add test cases. Explore orphan nodes and automate the drafted cases to raise coverage.

Arcus didn’t reach them in the time budget, or couldn’t open them, for example because a link was disabled or needed a sign-in. Click Explore more and describe the area to focus on, or turn on This app requires a login.

The graph hasn’t found a route to that node from the screens it mapped. This is a routing gap in the graph, not a problem with the node. Exploring the node can find a route.

Crawls use the most: each Start exploring or Explore more pass is charged as Crawl, and adding what it finds to the graph is charged as Knowledge Graph Ingestion. Explorations are charged as Exploratory, and only for the gaps Arcus verifies. To see what each one cost, open Settings > Usage and Credits and click By feature.

Was this page helpful?