Hosted appAI searchHosted, in placesucceeded

Open-source AI search engine with search groups and model choice. Tested in place on its hosted instance without signing in.

Tested in place byDeepQA Teamatscira.aionSep 20, 2026

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

11 of 12 scenarios passed, 1 blocked, no issues after the audit.

Share on X
Scira in the browser during the run

By the numbers

11 of 12
scenarios passed, 1 blocked
180
browser actions
37
screenshots
159
model calls
9.5
minutes
12
scenarios
11
passed
0
failed
1
blocked
0
issues

Walkthrough

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

  1. S1
    Main research query with typical data

    3 steps, 2 screenshots

    pass
    S1-1.png
    S1 · Main research query with typical data
    S1-14.png
    S1 · Main research query with typical data
    • Entered query 'What is compaction engineering?' into the message input field.
    • Navigated to https://scira.ai/ where the home search interface was displayed with the Message input textbox.
    • Typed 'What is compaction engineering?' into the Message input textbox and submitted via Enter key.
    • The application processed the query, transitioned to a thread view with a Messages region, and streamed the AI research response without throwing an error or prompting for authentication.
  2. S2
    Empty research query validation

    3 steps, 2 screenshots

    pass
    S2-1.png
    S2 · Empty research query validation
    S2-11.png
    S2 · Empty research query validation
    • Attempting to submit an empty or whitespace-only query on the Scira home and Research tab does not trigger any form submission or crash, preventing empty query execution as expected.
    • The application prevents submission when attempting to press Enter on an empty query input.
    • When whitespace only is typed and Send is clicked or Enter is pressed, submission is also prevented and the application does not submit, crash, or hang.
  3. S3
    Whitespace-only research query validation

    3 steps, 2 screenshots

    pass
    S3-1.png
    S3 · Whitespace-only research query validation
    S3-6.png
    S3 · Whitespace-only research query validation
    • Entered multiple whitespace characters into the Message input and pressed Enter and Send; the application treated the input as empty and did not submit or generate a query.
    • Navigated to https://scira.ai/ and entered whitespace-only input into the Message textbox.
    • Pressed Enter and clicked the Send button. The application correctly rejected the submission, treating the whitespace input as empty without triggering any search, prompt generation, or server errors.
  4. S4
    AI model selection

    4 steps, 4 screenshots

    blocked
    S4-1.png
    S4 · AI model selection
    S4-3.png
    S4 · AI model selection
    S4-11.png
    S4 · AI model selection
    S4-13.png
    S4 · AI model selection
    • Navigated to scira.ai homepage with model selector combobox visible.
    • Selecting any alternative AI model from the model selector triggers a 'Sign in required' modal, directing users to the /sign-in page which offers Google, GitHub, X, and Microsoft third-party authentication.
    • Navigated to https://scira.ai/ where the home search interface is displayed with a model selector combobox.
    • Clicked the model selector combobox, which opened the model selection dialog containing various models and providers.
    • Attempted to select alternative models (including Ministral 3 8B, GPT 5.4 Nano, and Laguna S 2.1), and all presented a 'Sign in required' modal stating 'Sign in required for [Model Name]'.
    • Navigated to the sign-in modal's 'Sign in' link which led to /sign-in offering OAuth providers: Google, GitHub, X, and Microsoft.
    • Model switching requires an account and cannot be completed without signing in.
  5. S5
    Web sources filter application

    4 steps, 4 screenshots

    pass
    S5-1.png
    S5 · Web sources filter application
    S5-3.png
    S5 · Web sources filter application
    S5-6.png
    S5 · Web sources filter application
    S5-10.png
    S5 · Web sources filter application
    • Opened the Sources dropdown menu displaying available source filters (Web, X, Stocks, Code, Academic, Reddit, GitHub, Crypto, Prediction, YouTube, Spotify).
    • Selected Reddit as the source filter, updating the button label to 'Sources: Reddit'.
    • Navigated to https://scira.ai/ and confirmed the Sources filter button was present displaying 'Sources: Web'.
    • Clicked the Sources button to open the filter menu showing options such as Web, X, Stocks, Code, Academic, Reddit, GitHub, Crypto, Prediction, YouTube, and Spotify.
    • Selected 'Reddit' and deselected 'Web', verifying that the filter button updated its label to 'Sources: Reddit'.
    • Submitted a search query 'best open source llm models' with the modified source filter.
    • The query executed successfully and the chat session displayed the active 'Sources: Reddit' filter.
  6. S6
    Extra-long query input boundary

    3 steps, 4 screenshots

    pass
    S6-1.png
    S6 · Extra-long query input boundary
    S6-3.png
    S6 · Extra-long query input boundary
    S6-6.png
    S6 · Extra-long query input boundary
    S6-9.png
    S6 · Extra-long query input boundary
    • Loaded scira.ai home page with search input ready.
    • Filled the Message input textbox with 5000 characters.
    • Pressed Enter to submit 5000 character message; application transitioned smoothly to chat response view without crashing.
    • Navigated to scira.ai home page and pasted a 5000-character string into the Message input textbox.
    • Submitted the 5000-character query by pressing Enter.
    • The application handled the large input gracefully, transitioned to the chat response view, and processed the request without crashing or displaying server errors.
  7. S7
    More options button interaction

    2 steps, 2 screenshots

    pass
    S7-1.png
    S7 · More options button interaction
    S7-3.png
    S7 · More options button interaction
    • Clicked the 'More options' button next to the message input, which opened a menu/dialog showing 'Modes, uploads & more' with options for uploading files, sources, and web search settings.
    • The 'More options' button next to the input box was responsive and displayed a dialog menu containing options for 'Upload files or images', 'Sources', and 'Web search'.
  8. S8
    Global search modal launch

    2 steps, 2 screenshots

    pass
    S8-1.png
    S8 · Global search modal launch
    S8-3.png
    S8 · Global search modal launch
    • Clicked the 'Search everything…⌘K' button on the homepage and observed the Command menu modal overlay opening successfully.
    • Navigated to https://scira.ai/ and verified presence of the 'Search everything…⌘K' button.
    • Clicked the 'Search everything…⌘K' button and verified that the Command menu dialog / modal appeared with prompt to search threads and access conversations.
  9. S9
    Keyboard shortcuts reference

    2 steps, 2 screenshots

    pass
    S9-1.png
    S9 · Keyboard shortcuts reference
    S9-4.png
    S9 · Keyboard shortcuts reference
    • Clicked the Keyboard shortcuts button in the top navigation banner and observed the Keyboard shortcuts dialog render with categorized shortcut lists.
    • Navigated to https://scira.ai/ and clicked the 'Keyboard shortcuts' button in the top navigation bar.
    • The 'Keyboard shortcuts' modal opened immediately, displaying supported shortcut lists categorized under Global navigation, Chat history, Chat, Multi-search, Carousel, and Timezone, along with Mac/Windows modifiers and a Close button.
  10. S10
    Visual theme toggling

    4 steps, 3 screenshots

    pass
    S10-1.png
    S10 · Visual theme toggling
    S10-3.png
    S10 · Visual theme toggling
    S10-5.png
    S10 · Visual theme toggling
    • Initial home page loaded with Light mode active and Dark mode button available in sidebar.
    • Clicked Dark mode button in sidebar, successfully activating dark theme.
    • Clicked Light mode button in sidebar, successfully reverting theme to light mode without layout breakage.
    • The Dark mode and Light mode toggles in the sidebar function properly and update the visual theme without errors or layout distortion.
  11. S11
    Core static pages integrity

    3 steps, 3 screenshots

    pass
    S11-2.png
    S11 · Core static pages integrity
    S11-4.png
    S11 · Core static pages integrity
    S11-6.png
    S11 · Core static pages integrity
    • Navigated to /about; page loaded correctly with mission, product details, stats, testimonials, and FAQs without errors.
    • Navigated to /pricing; page loaded correctly with Free, Pro, and Max pricing tiers, feature comparison table, quota details, and FAQs.
    • Navigated to /blog; page loaded correctly with a list of 12 published blog posts and RSS link without errors.
    • The About page (/about) rendered with mission details, stats, workflow steps, integrations, testimonials, and FAQs.
    • The Pricing page (/pricing) rendered with Free, Pro, and Max plans, an interactive search usage calculator, model quota limits, and comparison tables.
    • The Blog page (/blog) rendered with 12 published articles and an RSS link.
    • All three core static pages loaded without HTTP errors, 404s, 500s, or blank screens.
  12. S12
    Legal and iOS pages integrity

    3 steps, 3 screenshots

    pass
    S12-2.png
    S12 · Legal and iOS pages integrity
    S12-4.png
    S12 · Legal and iOS pages integrity
    S12-6.png
    S12 · Legal and iOS pages integrity
    • Navigated to /terms and verified the Terms of Service page rendered fully with 15 sections including acceptance, service description, user conduct, intellectual property, third parties, pricing, quotas, cancellation, liability, disclaimers, and contact info.
    • Navigated to /privacy-policy and confirmed Privacy Policy rendered fully with 10 sections covering data collection, usage, AI inference providers, data sharing, security, user rights, children's privacy, data retention, changes, and contact.
    • Navigated to /ios and verified the iOS app landing page loaded completely with App Store link (id6773326789), system requirements (iOS 16.4+), feature highlights, and navigation links.
    • Terms of Service (/terms) rendered with complete text across 15 structured sections and interactive table of contents.
    • Privacy Policy (/privacy-policy) rendered with complete policy details across 10 sections including third-party data processing and user rights.
    • iOS page (/ios) rendered cleanly with iPhone app details, App Store download button, system requirements, and web navigation links.

Issues

No finding survived the audit. Nothing to fix from this run.

Environment limitations

These failures came from the test environment, not from the application: a credential the sandbox does not hold, a demo nobody may write to, a resource it cannot reach. They are not counted as issues.

  • S1 could not exercise this: Server errors (415 and 502) logged to console during query execution. The console logs HTTP 415 and 502 status errors, even though the UI handles it gracefully and streams a response. The audit recorded the test environment as the cause, so it is not counted as an issue.

Critic audit

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

0
findings reviewed
0
re-verified live
0
withdrawn
    • Scenario S1 encountered HTTP 415 and 502 console errors that the Tester overlooked, though they are likely environment or upstream API limitations.

    Report

    QA report: external/scira.ai at hosted

    All tested public features functioned as expected and no confirmed application issues were identified.

    Testing covered primary research search workflows, input validation for empty, whitespace, and extra-long queries, web source filters, global search modals, keyboard shortcut references, theme toggling, and core static pages. Across all 11 executed scenarios, the application handled interactions and boundary conditions gracefully without functional failures.

    The run did not cover authenticated capabilities, leaving AI model selection unverified because the hosted environment lacks test account credentials. Additionally, background server error codes (HTTP 415 and 502) observed in the console during query execution were attributed to test environment and upstream API limitations rather than defects in the application UI.

    Because no functional regressions or defects were found in the accessible surface area, the tested workflows are in a stable state for deployment.

    Run summary
    MetricCount
    Scenarios executed12
    Passed11
    Failed0
    Blocked1
    Findings raised0
    Issues after the audit0
    Withdrawn by the audit0
    Critical / high / medium / low0 / 0 / 0 / 0

    Target: https://scira.ai · Testing level: deep_feature · Stack: unknown

    Issues

    No issues survived the audit.

    Environment limitations

    These failures came from the test environment, not from the application: a credential the sandbox does not hold, a demo nobody may write to, a resource it cannot reach. They are not counted as issues. They record what this run could not exercise.

    • S1 could not exercise this: Server errors (415 and 502) logged to console during query execution. The console logs HTTP 415 and 502 status errors, even though the UI handles it gracefully and streams a response. The audit recorded the test environment as the cause, so it is not counted as an issue.
    Scenario results
    ScenarioPriorityResultIssues
    S1 Main research query with typical datahighpassnone
    S2 Empty research query validationhighpassnone
    S3 Whitespace-only research query validationhighpassnone
    S4 AI model selectionmediumblocked (needs an account, out of scope for a hosted run)none
    S5 Web sources filter applicationmediumpassnone
    S6 Extra-long query input boundarymediumpassnone
    S7 More options button interactionmediumpassnone
    S8 Global search modal launchmediumpassnone
    S9 Keyboard shortcuts referencelowpassnone
    S10 Visual theme togglinglowpassnone
    S11 Core static pages integritylowpassnone
    S12 Legal and iOS pages integritylowpassnone
    The audit

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

    • Scenario S1 encountered HTTP 415 and 502 console errors that the Tester overlooked, though they are likely environment or upstream API limitations.
    Coverage and caveats

    In scope: Main unauthenticated research query flow; Empty, whitespace, and boundary validation on the query input; Query configuration controls (Model selector, Sources filter, More options); UI controls on the main page (Theme toggle, Search shortcut, Keyboard shortcuts); Unauthenticated static page navigation.

    Not covered: Account registration and login via OAuth (/sign-in, /sign-up) - needs an account, out of scope for a hosted run; Protected routes like /settings, /apps, /library, /projects, and /lookout - needs an account, out of scope for a hosted run.

    • Assume the AI model selector and sources filter do not require an active authenticated session to interact with
    • Assume AI research responses might take several seconds to generate and complete
    • S4 could not be executed: needs an account, out of scope for a hosted run.
    By the numbers
    MetricValue
    Scenarios11 passed, 0 failed, 1 blocked of 12 (36 planned steps)
    Browser actions180 (30 clicks, 13 inputs, 33 navigations, 104 snapshots)
    Screenshots37 (4 explore, 33 scenario, 0 critic), 33 captioned
    Coverage11 pages, 3 forms, 4 flows, 0 console errors
    Audit0 findings, 0 re-verified live, 0 confirmed, 0 promoted, 0 withdrawn
    Model calls159
    Tokens979,799 input, 9,076 output, 12,403 thinking
    Time9 min
    StageCallsInputOutputThinkingSeconds
    explore29207,9102,3371,716112
    plan14,1711,8903,10739
    test127761,6034,3875,345397
    critique14,6582621,55115
    report11,4572006846

    Run log

    stagecallstokenstime
    Explore29212k1m 52s
    Plan19.2k39s
    Test127771.3k6m 37s
    Critique16.5k15s
    Report12.3k6s
    Total1591M9m 28s
    Intake
    Explore
    Plan
    Test
    Critique
    Report
    • 01:01:29Zexploreexplore started
    • 01:10:57ZexploreExplored / (33 controls, 0 forms)
    • 01:10:57ZexploreExplored /about (28 controls, 1 forms)
    • 01:10:57ZexploreExplored /pricing (33 controls, 0 forms)
    • 01:10:57ZexploreExplored /sign-in (11 controls, 0 forms)
    • 01:10:57ZexploreExplored /sign-up (11 controls, 0 forms)
    • 01:10:57ZexploreExplored /blog (29 controls, 0 forms)
    • 01:10:57ZexploreExplored /blog/compaction-engineering (46 controls, 0 forms)
    • 01:10:57ZexploreExplored /terms (38 controls, 0 forms)
    • 01:10:57ZexploreExplored /privacy-policy (34 controls, 0 forms)
    • 01:10:57ZexploreExplored /contact (15 controls, 0 forms)
    • 01:10:57ZexploreExplored /ios (14 controls, 0 forms)
    • 01:10:57ZexploreMapped 11 pages, 3 forms, 4 flows in 29 turns.
    • 01:10:57Zexploreexplore completed in 112s.
    • 01:10:57Zplanplan started
    • 01:10:57ZplanPlanned 12 scenarios (3 high, 5 medium, 4 low).
    • 01:10:57Zplanplan completed in 39s.
    • 01:10:57Ztesttest started
    • 01:10:57ZtestS1 executed (pass)
    • 01:10:57ZtestS2 executed (pass)
    • 01:10:57ZtestS3 executed (pass)
    • 01:10:57ZtestS4 executed (blocked)
    • 01:10:57ZtestS5 executed (pass)
    • 01:10:57ZtestS6 executed (pass)
    • 01:10:57ZtestS7 executed (pass)
    • 01:10:57ZtestS8 executed (pass)
    • 01:10:57ZtestS9 executed (pass)
    • 01:10:57ZtestS10 executed (pass)
    • 01:10:57ZtestS11 executed (pass)
    • 01:10:57ZtestS12 executed (pass)
    • 01:10:57ZtestExecuted 12 scenarios: 11 passed, 0 failed, 1 blocked, 0 findings.
    • 01:10:57Ztesttest completed in 397s.
    • 01:10:57Zcritiquecritique started
    • 01:10:57ZcritiqueReviewed 0 findings; 1 possible defect spotted in passed scenarios.
    • 01:10:57ZcritiqueAudit complete: 0 confirmed, 0 withdrawn, 0 promoted, 0 re-verified live.
    • 01:10:57Zcritique1 failure came from the test environment rather than the application. It is reported as an environment limitation, not an issue.
    • 01:10:57Zcritiquecritique completed in 15s.
    • 01:10:57Zreportreport started
    • 01:10:57ZreportReported 0 issues (0 critical, 0 high, 0 medium, 0 low) from 0 findings.
    • 01:10:57Zreportreport 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.