Deep Research

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

1. S1

   Page load and console error check

   2 steps, 1 screenshot

   high✓ pass

   

   • Navigated to https://research.u14.app/ and verified the main research workflow interface loaded completely.
   • The page at https://research.u14.app/ loaded cleanly with title 'Deep Research'.
   • All primary UI components rendered properly: banner, research workflow stages, topic input form, quick start templates, and stage placeholders.
   • No 403 Forbidden or fatal JavaScript exceptions prevented the page from loading and rendering correctly.
2. S2

   Apply quick start templates

   5 steps, 4 screenshots

   high✓ pass

   

   

   

   

   • Loaded the Deep Research homepage with the research workflow form visible and quick start templates available.
   • Clicked the 'Market map' template button and the research topics textarea populated with 'Map the current market landscape for [your topic]. Compare m...'.
   • Clicked the 'Technical deep dive' template button and the research topics textarea updated to 'Perform a technical deep dive on [your topic]. Explain archi...'.
   • Clicked the 'Compare options' template button and the research topics textarea updated to 'Compare the top solutions for [your topic]. Build a decision...'.
   • The quick start template buttons 'Market map', 'Technical deep dive', and 'Compare options' each properly populate and replace the '1.1 Research topics' textarea with their respective template prompts.
3. S3

   Reset research topic

   3 steps, 3 screenshots

   high✓ pass

   

   

   

   • Navigated to https://research.u14.app/ and verified initial research topic view.
   • Clicked the Market map template button, populating the '1.1 Research topics' textbox.
   • Clicked the reset research topic button; the '1.1 Research topics' textarea was completely cleared.
   • Clicking the 'Market map' template populates the '1.1 Research topics' textarea.
   • Clicking the reset button next to '1. Research Topics' completely clears the textarea.
4. S4

   Empty topic submission validation

   3 steps, 3 screenshots

   high✕ fail

   

   

   

   • Loaded the research workflow page with empty research topic textarea.
   • Clicking 'Start Thinking' with an empty topic input produces no feedback, error message, or visual indication.
   • Loaded https://research.u14.app/ with an empty research topic textarea.
   • Clicked the 'Start Thinking' button while the field remained blank.
   • Observed no validation error message, HTML5 validation popup, or visual indicator; the click failed silently.
5. S5

   Workflow initiation prompts for unconfigured API keys

   3 steps, 3 screenshots

   high✓ pass

   

   

   

   • Navigated to the Deep Research homepage with an empty research topics textarea.
   • Clicked 'Start Thinking' with no API keys configured, and the 'Setting' dialog modal automatically opened.
   • Entering a research topic and clicking 'Start Thinking' without configured API keys immediately opens the Setting dialog modal to prompt for required configuration.
6. S6

   Attach resource dropdown options

   3 steps, 2 screenshots

   medium✓ pass

   

   

   • Clicked the 'Add Resource' button and observed the dropdown menu displaying 'Knowledge', 'Local File', and 'Web Page' options.
   • The 'Add Resource' button on the research topic form opens a dropdown menu containing 'Knowledge', 'Local File', and 'Web Page' options as expected.
7. S7

   Navigate and save Application Settings

   5 steps, 4 screenshots

   medium✓ pass

   

   

   

   

   • Opened the Settings modal by clicking the settings button in the top navigation.
   • Switched to the System tab within the Settings modal, updating the active tabpanel to System.
   • Switched back to the Model tab within the Settings modal, updating the active tabpanel to Model.
   • Navigated to https://research.u14.app/ and clicked the Settings gear icon in the header.
   • The Settings modal opened displaying category tabs (Model, Search, System).
   • Switched tabs within the modal to 'System', then through 'Search' and back to 'Model', observing that the active tabpanel updated dynamically.
   • Clicked the 'Save' button in the Settings modal.
   • Observed the modal dismiss and return the view to the main application interface without errors.
8. S8

   Manage Local Knowledge Base modal

   4 steps, 4 screenshots

   medium✓ pass

   

   

   

   

   • Clicked the Local Knowledge Base button in the header; the Local Knowledge Base modal opened displaying the Create button, keyword search input, and tabpanel.
   • Clicked Create within the Local Knowledge Base modal; observed creation interface with title and markdown content editor.
   • Closed the Local Knowledge Base modal by clicking the Close button, returning to the main research page.
   • Navigated to https://research.u14.app/ and clicked the Local Knowledge Base header toggle button.
   • Observed the Local Knowledge Base modal open successfully with search controls, empty state indicator, and a Create button.
   • Clicked Create within the modal and observed the document creation view with title and Markdown editor.
   • Clicked the Close button; the modal closed properly and returned to the main research workflow page.
9. S9

   View and dismiss Research History

   3 steps, 3 screenshots

   medium✓ pass

   

   

   

   • Clicked the History button in the banner, which opened the History modal with search, import, and empty records state.
   • Pressed the Escape key, which successfully dismissed the History modal and returned focus to the main interface.
   • The History button toggles open the History modal containing search input, import button, and session history records list.
   • Pressing the Escape key while the History dialog is open immediately closes the dialog.
10. S10

    Keyboard shortcuts dialog behavior

    3 steps, 4 screenshots

    low✓ pass

    

    

    

    

    • The keyboard shortcuts dialog ('Power Shortcuts') opens properly showing all shortcut combinations, and closes cleanly when dismissed via Escape key or the Close button.
    • Navigated to https://research.u14.app/ and clicked the keyboard shortcuts toggle button.
    • The 'Power Shortcuts' modal dialog appeared listing all power shortcuts (settings, history, knowledge base, export session, import session snapshot, toggle shortcut help).
    • Dismissing the modal (via Escape / close action) cleanly closed the dialog and returned the user to the main research workflow view.
11. S11

    GitHub repository link integrity

    3 steps, 1 screenshot

    low✓ pass

    

    • Located GitHub repository links in the banner and footer: 'Deep Researchv0.11.0' and the GitHub icon link point to 'https://github.com/u14app/deep-research', and the footer link points to 'https://github.com/u14app/'.
    • The GitHub repository link in the top navigation banner correctly points to https://github.com/u14app/deep-research.
    • The footer link correctly points to https://github.com/u14app/.

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

mediumconfirmed ✓functionalF1 · S4

Empty research topic submission fails silently without validation feedback

I navigated to the application, left the '1.1 Research topics' textbox empty, and clicked the 'Start Thinking' button. The page did not update, and no validation error or feedback was displayed.

Expected

The application should display a validation error or visible indication that the research topic is required before proceeding.

Actual

The application suppresses the research workflow start but provides no error message, visual highlight, or feedback to the user explaining why submission was ignored.

Repro · 3 steps

1. Navigate to https://research.u14.app/.
2. Ensure the '1.1 Research topics' textarea is blank.
3. Click the 'Start Thinking' button.

S4-4.pngS4-7.png

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.

• S5 could not exercise this: API responds with 403 Forbidden during workflow initiation without configured keys. The server responds with a 403 status due to missing or invalid credentials. The audit recorded the test environment as the cause, so it is not counted as an issue.