Morphic

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

1. S1

   Search query requires authentication

   3 steps, 2 screenshots

   high✓ pass

   

   

   • Submitted query 'What is Morphic?' and observed 'Continue with Morphic' sign-in prompt modal displayed with Sign Up and Sign In links.
   • The 'Continue with Morphic' sign-in prompt modal appeared immediately upon submitting the search query 'What is Morphic?', prompting the user to sign in or sign up before continuing.
2. S2

   Suggestion chips require authentication

   2 steps, 3 screenshots

   high✓ pass

   

   

   

   • Clicked the Troubleshoot suggestion chip; the input field was populated with 'Troubleshoot' and the submit button became active, with no sign-in prompt modal displayed immediately.
   • Submitted the query and the 'Continue with Morphic' sign-in prompt modal was displayed with Sign Up and Sign In options.
   • Loaded the homepage at https://chat.morphic.sh/ with suggestion chips visible.
   • Clicking the 'Troubleshoot' chip populated the search input with 'Troubleshoot'.
   • Submitting the form displayed the 'Continue with Morphic' modal dialog requesting sign-in to continue.
3. S3

   Adaptive mode requires authentication

   2 steps, 2 screenshots

   high✓ pass

   

   

   • Navigated to home page and observed Adaptive mode button in the search form.
   • Clicked on Adaptive mode button and observed the 'Continue with Morphic' sign-in prompt modal prompting the user to Sign In or Sign Up.
   • Clicking 'Adaptive mode' when unauthenticated displays a 'Continue with Morphic' modal dialog explaining that Adaptive mode requires an account while Quick mode remains available without one.
   • The modal provides links to 'Sign Up' (/auth/sign-up) and 'Sign In' (/auth/login), as well as a Close button.
4. S4

   Submit feedback

   4 steps, 4 screenshots

   high✓ pass

   

   

   

   

   • Opened the Give feedback dialog from the home page header.
   • Entered 'Looks good' into the feedback field and selected a sentiment rating, enabling the Submit button.
   • Submitted feedback successfully; the modal closed and a toast notification 'Thank you for your feedback!' appeared.
   • Navigated to the home page and clicked the Feedback button to open the Give feedback modal.
   • Filled in feedback text, selected a rating option to enable Submit, and submitted the form.
   • The modal closed and displayed a confirmation toast with 'Thank you for your feedback!'.
5. S5

   Login form requires credentials

   3 steps, 2 screenshots

   high✓ pass

   

   

   • Navigated to the login page at /auth/login with empty Email and Password fields.
   • Clicked Sign In with empty fields; form submission was blocked by required field validation without submitting empty credentials or reloading the page.
   • The login form inputs for Email and Password have HTML5 'required' attributes and block form submission when empty, remaining on /auth/login without reloading or transmitting empty credentials.
6. S6

   Cancel feedback submission

   3 steps, 3 screenshots

   medium✓ pass

   

   

   

   • Opened the Give feedback modal showing feedback textbox, reaction buttons, Cancel, Submit, and Close buttons.
   • Clicked Cancel button in the Give feedback modal and verified that the dialog closed completely without submitting.
   • Navigated to https://chat.morphic.sh/ and clicked the 'Feedback' button in the top banner.
   • The 'Give feedback' modal dialog opened properly with feedback options, textarea, Submit, and Cancel buttons.
   • Clicked the 'Cancel' button in the dialog.
   • Verified that the feedback dialog closed immediately and the main page remained intact without any errors or submissions.
7. S7

   Login form validates email format

   4 steps, 3 screenshots

   medium✓ pass

   

   

   

   • Navigated to the login page at /auth/login.
   • Attempted to submit the login form with an invalid email address ('invalid-email'); HTML5 email validation on input type=email prevented form submission.
   • The login form uses type='email' required on the Email field, blocking form submission on invalid email format ('invalid-email').
   • No network submission was triggered with the invalid email format, remaining on /auth/login.
8. S8

   Sign Up form requires fields

   3 steps, 2 screenshots

   medium✓ pass

   

   

   • Navigated to /auth/sign-up page displaying email, password, and repeat password fields marked as required.
   • Clicked Sign Up with empty fields; HTML5 form validation blocked submission and kept the user on /auth/sign-up.
   • The Sign Up form at /auth/sign-up marks Email, Password, and Repeat Password fields as required, and submitting empty credentials is blocked by form validation without submitting to the server.
9. S9

   Forgot password form requires email

   3 steps, 2 screenshots

   medium✓ pass

   

   

   • Navigated to the Forgot Password page with an empty required Email field.
   • Clicked 'Send reset email' with empty Email field; form validation blocked submission and kept the user on the reset page.
   • Navigated to /auth/forgot-password where the email field is marked required.
   • Attempting to submit the form without entering an email blocks submission via HTML5 form validation.
10. S10

    Navigate between auth flows

    4 steps, 3 screenshots

    medium✓ pass

    

    

    

    • Navigated to /auth/login and observed the login form with Forgot password link.
    • Clicked 'Forgot password?' and successfully navigated to /auth/forgot-password with the password reset form.
    • Clicked 'Login' link on the reset password page and successfully navigated back to /auth/login.
    • Navigated from /auth/login to /auth/forgot-password via the 'Forgot password?' link.
    • Observed the password reset page with email input and 'Send reset email' button.
    • Navigated back to /auth/login via the 'Login' link on the reset page.
11. S11

    Open side menu

    2 steps, 2 screenshots

    low✓ pass

    

    

    • Clicked the 'Open menu' button and observed the side/dropdown menu open with options Sign In, Theme, and Links.
    • The 'Open menu' button expands the menu correctly, revealing menu items 'Sign In', 'Theme', and 'Links'.

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: Unauthenticated search query results in 401 console error. The search request fails with a 401 Unauthorized status, triggering a sign-in modal and halting the core functional flow. The audit recorded the test environment as the cause, so it is not counted as an issue.