1. Docs
  2. Get started
  3. Quick Start
  4. Progress meters

Progress meters

Two meters show how far a project is: the setup guide checklist and the Setup Roadmap. They measure different things.

2 min read Updated CustomersAdmins

In short

On this page you can

  • Read the Setup n/3 checklist in the top bar and what its colours mean.
  • Understand why the setup guide is kept per browser and per project.
  • See the eight steps of the Setup Roadmap on the Discover page.
  • Check the formula behind each roadmap percentage, with a worked example.

How to use it

  1. Click Setup n/3 and tick each item once you have done it.
  2. Finish any one route to complete Teach your app.
  3. Open the Setup Roadmap tab in Discover for progress calculated by the server.
  4. A step unlocks the next one at 90%; unfinished steps show at most 99%.

Setup guide (top bar)#

The Setup n/3 button opens a checklist of three steps: Connect, Teach your app, Run & report. It is red with nothing done, amber when partly done and green when all three are done.

  • You tick the items yourself. The only item ticked automatically is “Add your start page URL”, when you add the first one.
  • Progress is kept in your browser, per project. Another browser or computer starts from 0/3.
  • “Teach your app” is done when any one route is fully ticked.

Setup Roadmap (Discover page)#

The roadmap is calculated by the server from what really exists in the project, so it is the same for everyone. It has eight steps: Connect, Describe the app, Split into modules, Write requirements, Write test cases, Build pipelines, Connect integrations, Install autonomous agents.

How each roadmap step’s percentage is calculatedUnfinished steps show at most 99%
Connect            web: 90% when the extension answers or pages exist; device: 90% with ≥1 host
                   100% once an AI assistant has used the MCP connection
Describe the app   40% + 60% × min(1, described pages ÷ (0.6 × pages))      done at ≥60% described
Split into modules pages assigned to a module ÷ pages
Write requirements 50% × (modules with a MAIN requirement ÷ modules) + 50% if any SUB exists
Write test cases   SUB requirements that have tests ÷ SUB requirements
Build pipelines    50% when a pipeline exists; done when one has a schedule
Integrations       mail (SMTP) 50% + 50%/3 for each of issue tracker, chat, repository
                   90% with SMTP + (tracker or chat); 100% with all four
Chain rule         a step cannot pass the previous one until that one reaches 90%

Example: 10 pages, 3 with a purpose written. 0.6 × 10 = 6 pages needed, 3 ÷ 6 = 0.5, so 40 + 60 × 0.5 = 70%. With 5 described it is 90%, which unlocks the next step. With 6 described it is done.

More detail on the Describe step is on the Discover page.

Didn’t find your answer?Write to support with your project name and what you see on screen.

info@smartestqa.ai