2Under your repository name, click Insights.accurate
VerdictKane followed the doc's exact words and reached the goal.
What Kane did
Literal passedaction · 15.3 cr · 119s
  1. navigate: Navigate to https://github.com/expressjs/express
  2. click: Clicking Insights link
  3. wait: PRIMARY: wait for the Insights page heading to be visible
  4. analyze: ANALYZE(textual_visual, 'the main heading of the page you end on is stored as {{
  5. wait: Waiting after the verified Insights heading extraction
opened Insights on github.com
Clicked, per the evidence pack: Insights
Follow these steps literally, one at a time, from the current page. Click only what each step names. Never type a URL, search, or take another route. 1. Click the element whose visible label is exactly 'Insights'. Then store the main heading of the page you end on as 'landed_on'.
3In the left sidebar, click Code frequency.accurate
VerdictKane followed the doc's exact words and reached the goal.
What Kane did
Literal passedaction · 17.4 cr · 66s
  1. navigate: Navigate to https://github.com/expressjs/express/pulse
  2. click: Clicking Code frequency link in Insights navigation
  3. wait: PRIMARY: wait for the Code frequency page heading to load
  4. analyze: ANALYZE(textual_visual, 'The main heading of the page you end on is stored as {{
  5. wait: Waiting after checkpoint verification
opened the Code frequency view on GitHub
Clicked, per the evidence pack: Code frequency
Follow these steps literally, one at a time, from the current page. Click only what each step names. Never type a URL, search, or take another route. 1. Click the element whose visible label is exactly 'Code frequency'. Then store the main heading of the page you end on as 'landed_on'.