Hosted appNewsArc Testnetsucceeded

The center of news

Tested in place byDeepQA TeamonArc Testnetatarctimes.net/onSep 17, 2026

Run #1model gemini-balanced (vertex)took 11m

All 10 scenarios passed, 1 low functional issue after the audit.

Share on X
ARC Times in the browser during the run

By the numbers

10 of 10
scenarios passed
76
browser actions
20
screenshots
77
model calls
11
minutes
10
scenarios
10
passed
0
failed
0
blocked
1
issues
low1

Walkthrough

Every scenario DeepQA drove in the browser, in plan order, with the 16 screenshots it captured along the way. A passing scenario is evidence too.

  1. S1
    View homepage news listing

    2 steps, 1 screenshot

    pass
    S1-1.png
    S1 · View homepage news listing
    • Loaded https://arctimes.net/ and observed the 'ARC TIMES' header, 8 featured news articles with thumbnails and titles, and project statistics ($222M investment, 104K+ followers, etc.).
    • The homepage rendered completely with the 'ARC TIMES' header.
    • Multiple news articles with titles, dates, thumbnails, and 'READ MORE' links were visible.
    • The project statistics sidebar displayed investment, follower count, testnet addresses, total blocks, and total transactions correctly.
  2. S2
    Open article from homepage

    2 steps, 2 screenshots

    pass
    S2-1.png
    S2 · Open article from homepage
    S2-3.png
    S2 · Open article from homepage
    • Loaded the homepage at https://arctimes.net/ displaying the Arc Network Funding Breakthrough article with a READ MORE button.
    • Clicked the READ MORE button and successfully navigated to news-detail.php?slug=arc-network-funding-breakthrough displaying the full article heading, metadata, content, and share buttons.
    • Navigating to the homepage loads the news list with article summaries and 'READ MORE' links.
    • Clicking 'READ MORE' on the 'Arc Network Funding Breakthrough' article navigates to news-detail.php?slug=arc-network-funding-breakthrough with the full article text and metadata rendered properly.
  3. S3
    Return to homepage via BACK link

    2 steps, 2 screenshots

    pass
    S3-2.png
    S3 · Return to homepage via BACK link
    S3-4.png
    S3 · Return to homepage via BACK link
    • Navigated to the article detail page at /news-detail.php?slug=arc-network-funding-breakthrough and observed the BACK navigation link.
    • Clicked the BACK link on the news detail page and successfully navigated back to the homepage at https://arctimes.net/.
    • The BACK navigation link on the news detail page successfully routes the user back to the homepage (https://arctimes.net/).
  4. S4
    Open and close photo lightbox

    5 steps, 3 screenshots

    pass
    S4-1.png
    S4 · Open and close photo lightbox
    S4-3.png
    S4 · Open and close photo lightbox
    S4-5.png
    S4 · Open and close photo lightbox
    • Clicked on the photo gallery thumbnail and observed the photo lightbox modal open displaying the full image and a close button.
    • Clicked the modal close button and observed the lightbox close cleanly, restoring the default page view.
    • Navigated to the home page and scrolled to the PHOTOS section.
    • Clicked a photo thumbnail in the gallery, which successfully triggered the lightbox modal displaying the full image and a close button.
    • Clicked the close button and confirmed the lightbox modal closed properly.
  5. S5
    Navigate directly between related articles

    3 steps, 2 screenshots

    pass
    S5-2.png
    S5 · Navigate directly between related articles
    S5-4.png
    S5 · Navigate directly between related articles
    • Navigated to the article detail page for Arc Network Funding Breakthrough and observed the MORE ARTICLES section.
    • Clicked the 'Arc Token [redacted] Drops' link under MORE ARTICLES and successfully navigated to the article detail page showing the corresponding content.
    • Navigating to an article from the MORE ARTICLES section loads the correct target article detail page and updates title, ID, views, and content accordingly.
  6. S6
    Verify social share links

    2 steps, 1 screenshot

    pass
    S6-2.png
    S6 · Verify social share links
    • Navigated to news detail page and verified Twitter (intent/tweet) and Telegram (t.me/share/url) share links are present with valid intent endpoints and parameters.
    • Navigated to https://arctimes.net/news-detail.php?slug=arc-network-funding-breakthrough.
    • Verified the presence of the 'SHARE THIS ARTICLE' section containing Twitter and Telegram share links.
    • Inspected the Twitter share link and confirmed it points to a valid Twitter sharing intent URL (https://twitter.com/intent/tweet?text=...).
    • Inspected the Telegram share link and confirmed it points to a valid Telegram sharing intent URL (https://t.me/share/url?url=...).
  7. S7
    Trigger Copy Link functionality

    2 steps, 2 screenshots

    pass
    S7-2.png
    S7 · Trigger Copy Link functionality
    S7-4.png
    S7 · Trigger Copy Link functionality
    • Navigated to the news detail page for 'Arc Network Funding Breakthrough' and located the COPY LINK button.
    • Clicked the 'COPY LINK' button; the page handled the action cleanly without throwing uncaught errors or breaking the UI.
    • The 'COPY LINK' button on the news detail page executes gracefully without causing fatal JavaScript errors, alert popups, or layout breakdown.
  8. S8
    Handle missing slug parameter

    1 step, 1 screenshot

    pass
    S8-2.png
    S8 · Handle missing slug parameter
    • Navigated to /news-detail.php without a slug parameter and observed an automatic redirect to the homepage (https://arctimes.net/).
    • Directly accessing /news-detail.php without a query parameter gracefully redirects the user to the homepage (https://arctimes.net/) without PHP warnings or server errors.
  9. S9
    Handle invalid slug parameter

    1 step, 1 screenshot

    pass
    S9-4.png
    S9 · Handle invalid slug parameter
    • Navigated to /news-detail.php?slug=this-is-a-fake-article-slug-999 and verified that the application gracefully redirects to the home page (https://arctimes.net/) instead of crashing or showing broken/empty UI.
    • Navigated to https://arctimes.net/news-detail.php?slug=this-is-a-fake-article-slug-999 and confirmed the server gracefully redirects to the home page (https://arctimes.net/) rather than crashing, displaying database errors, or rendering broken empty templates.
    • Navigated to https://arctimes.net/news-detail.php without a slug parameter and confirmed it also safely redirects to the home page.
    • Navigated to a valid slug (https://arctimes.net/news-detail.php?slug=arc-network-funding-breakthrough) and confirmed valid news detail pages load and render full article content as expected.
  10. S10
    External sidebar links integrity

    2 steps, 1 screenshot

    pass
    S10-1.png
    S10 · External sidebar links integrity
    • Observed sidebar external links for Twitter, Discord, Web Site, Faucet, Explorer, Ecosystem, and Arc World, all pointing to valid fully qualified URLs.
    • The homepage sidebar displays outbound links for Twitter (https://x.com/arc), Discord (https://discord.com/invite/buildonarc), Web Site (https://www.arc.network), Faucet (https://faucet.circle.com/), Explorer (https://testnet.arcscan.app), Ecosystem (https://www.arc.network/ecosystem), and Arc World (https://arcworld.io/).
    • All external resource links are present and correctly formatted with fully qualified URLs.

Issues

Findings that survived the Critic's audit. Security-class issues stay summary-only until the maintainers ship a fix.

lowpromoted ↑functionalF1 · S7

Unhandled promise rejection on Copy Link action

Surfaced by the audit of S7, which the Tester passed, and reproduced live: Navigated to a news detail page and clicked the 'COPY LINK' button. No graceful error handling, toast, or user feedback was displayed on the page, confirming the lack of a proper UI response for the clipboard rejection. The page reported 1 console error during the scenario.

Expected

The application gracefully handles the clipboard API permission denial or rejection.

Actual

An uncaught console error is thrown regarding clipboard write permission.

Repro · 2 steps
  1. Navigate to a news detail page.
  2. Click the COPY LINK button.

Wallet activity

DeepQA injected a test wallet into the browser and recorded every request the app sent to it. Testnet funds only.

address
0xB412E2…Ab62A6
chain
Arc Testnet
browsers opened
3
read requests forwarded
0
signing requests
0

Critic audit

An adversarial second pass over every finding before it reaches the report.

0
findings reviewed
1
re-verified live
0
withdrawn
  • F1promoted ↑

    Surfaced by the audit of S7, which the Tester passed, and reproduced live: Navigated to a news detail page and clicked the 'COPY LINK' button. No graceful error handling, toast, or user feedback was displayed on the page, confirming the lack of a proper UI response for the clipboard rejection.

  • Scenario S7 encountered a clipboard permission error, indicating the test harness may need clipboard-write permissions explicitly enabled to accurately test this feature.

Report

QA report: external/arctimes.net at hosted

The application is functional across all primary flows with one low-severity unhandled promise rejection on the Copy Link action.

Testing covered 10 scenarios on arctimes.net, exercising article browsing, photo lightbox interactions, related article navigation, social sharing, invalid slug error handling, and external links.

All 10 scenarios passed functional checks, though auditing confirmed a low-severity functional issue (F1) where clicking the Copy Link button causes an unhandled promise rejection when clipboard write permissions fail.

The core reading and navigation workflows operate as expected, with this minor clipboard error being the sole defect identified.

Run summary
MetricCount
Scenarios executed10
Passed10
Failed0
Blocked0
Findings raised0
Issues after the audit1
Withdrawn by the audit0
Critical / high / medium / low0 / 0 / 0 / 1

Target: https://arctimes.net/ · Testing level: deep_feature · Stack: unknown

Issues
Low severity
F1 · Unhandled promise rejection on Copy Link action

Severity: low · Type: functional · Verdict: promoted · Scenario: S7

Surfaced by the audit of S7, which the Tester passed, and reproduced live: Navigated to a news detail page and clicked the 'COPY LINK' button. No graceful error handling, toast, or user feedback was displayed on the page, confirming the lack of a proper UI response for the clipboard rejection. The page reported 1 console error during the scenario.

Expected: The application gracefully handles the clipboard API permission denial or rejection.

Actual: An uncaught console error is thrown regarding clipboard write permission.

Steps to reproduce:

  1. Navigate to a news detail page.
  2. Click the COPY LINK button.

Evidence: screenshots/critic-M1-1.png

Scenario results
ScenarioPriorityResultIssues
S1 View homepage news listinghighpassnone
S2 Open article from homepagehighpassnone
S3 Return to homepage via BACK linkhighpassnone
S4 Open and close photo lightboxmediumpassnone
S5 Navigate directly between related articlesmediumpassnone
S6 Verify social share linksmediumpassnone
S7 Trigger Copy Link functionalitymediumpassF1
S8 Handle missing slug parameterlowpassnone
S9 Handle invalid slug parameterlowpassnone
S10 External sidebar links integritylowpassnone
The audit

The Critic reviewed 0 findings and re-verified 1 of them live in the browser, replaying the reported steps on a fresh page.

  • Scenario S7 encountered a clipboard permission error, indicating the test harness may need clipboard-write permissions explicitly enabled to accurately test this feature.
What to fix first
  1. Add error handling to the Copy Link action to gracefully catch clipboard permission rejections (F1).
Coverage and caveats

In scope: Homepage news listing and layout; Article detail view and metadata rendering; Photo lightbox gallery interactions; Social sharing links and copy functionality; Cross-article navigation via related stories; Edge cases for missing or invalid article slugs.

Not covered: Wallet connection and transaction flows; Verification of external pages off-origin.

  • The application does not have interactive form submissions or authentication as none were mapped.
  • Automated browsers often deny clipboard write permissions by default; the copy link test assumes a console permission error is an acceptable outcome provided the page does not crash.
By the numbers
MetricValue
Scenarios10 passed, 0 failed, 0 blocked of 10 (22 planned steps)
Browser actions76 (15 clicks, 0 inputs, 23 navigations, 38 snapshots)
Screenshots20 (3 explore, 16 scenario, 1 critic), 16 captioned
Coverage3 pages, 0 forms, 3 flows, 1 console errors
Audit0 findings, 1 re-verified live, 0 confirmed, 1 promoted, 0 withdrawn
Model calls77
Tokens365,366 input, 5,605 output, 10,161 thinking
Time11 min
Wallet0 transactions, 0 signatures, 0 refusals on chain 5042002
StageCallsInputOutputThinkingSeconds
explore1160,3211,18478057
plan12,9601,6482,85437
test58275,6472,2643,686324
critique625,1563302,372261
report11,2821794696

Run log

stagecallstokenstime
Explore1162.3k57s
Plan17.5k37s
Test58281.6k5m 24s
Critique627.9k4m 21s
Report11.9k6s
Total77381.1k11m 25s
Intake
Explore
Plan
Test
Critique
Report
  • 17:12:04Zexploreexplore started
  • 17:23:29ZexploreExplored / (30 controls, 0 forms)
  • 17:23:29ZexploreExplored /news-detail.php (11 controls, 0 forms)
  • 17:23:29ZexploreMapped 3 pages, 0 forms, 3 flows in 11 turns.
  • 17:23:29Zexploreexplore completed in 57s.
  • 17:23:29Zplanplan started
  • 17:23:29ZplanPlanned 10 scenarios (3 high, 4 medium, 3 low).
  • 17:23:29Zplanplan completed in 37s.
  • 17:23:29Ztesttest started
  • 17:23:29ZtestS1 executed (pass)
  • 17:23:29ZtestS2 executed (pass)
  • 17:23:29ZtestS3 executed (pass)
  • 17:23:29ZtestS4 executed (pass)
  • 17:23:29ZtestS5 executed (pass)
  • 17:23:29ZtestS6 executed (pass)
  • 17:23:29ZtestS7 executed (pass)
  • 17:23:29ZtestS8 executed (pass)
  • 17:23:29ZtestS9 executed (pass)
  • 17:23:29ZtestS10 executed (pass)
  • 17:23:29ZtestExecuted 10 scenarios: 10 passed, 0 failed, 0 blocked, 0 findings.
  • 17:23:29Ztesttest completed in 324s.
  • 17:23:29Zcritiquecritique started
  • 17:23:29ZcritiqueReviewed 0 findings; 1 possible defect spotted in passed scenarios.
  • 17:23:29ZcritiqueRe-verified a possible defect in S7: reproduced.
  • 17:23:29ZcritiqueAudit complete: 0 confirmed, 0 withdrawn, 1 promoted, 1 re-verified live.
  • 17:23:29Zcritiquecritique completed in 261s.
  • 17:23:29Zreportreport started
  • 17:23:29ZreportReported 1 issue (0 critical, 0 high, 0 medium, 1 low) from 0 findings.
  • 17:23:29Zreportreport completed in 6s.

Put an agent team on your next pull request.

Connect a repo, dispatch a Run, and read an audited, evidence-backed report the same day.