samanhappy/mcphub

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

1. S1

   Primary Resource Creation

   12 steps, 4 screenshots

   high✓ pass

   

   

   

   

   • Logged in successfully as admin and arrived at Dashboard.
   • Saved the new resource file:///app/config.json with name App Config, and verified it appears in the resources list with Active status.
   • Navigated to /login and authenticated as admin.
   • Navigated to /resources and clicked Add Resource.
   • Filled out the modal form with Resource URI 'file:///app/config.json', Name 'App Config', Description 'Main application configuration', MIME Type 'application/json', Content '{}', and Enabled checked.
   • Clicked Save, observed modal close, and verified the resource appeared in the list with URI, Name, Description, MIME type, and Active status.
2. S2

   Resource Creation - Required Fields Only

   9 steps, 3 screenshots

   high✓ pass

   

   

   

   • Navigated to Resources page showing 1 built-in resource.
   • Opened the Add New Resource dialog.
   • Filled URI with 'file:///app/minimal.txt' and content with 'Minimal content', leaving name, description, and mime type empty.
   • Navigated to the /resources page which initially contained 1 resource.
   • Clicked Add Resource and opened the creation modal.
   • Provided the mandatory URI 'file:///app/minimal.txt' and Content 'Minimal content' while leaving Name, Description, and MIME Type empty.
   • Submitted the form with Save button; the resource saved cleanly without validation errors on the optional fields.
   • The new resource 'file:///app/minimal.txt' appeared in the Built-in Resources list with Active status, incrementing total resource count to 2.
3. S3

   Form Validation - Missing Resource URI

   8 steps, 4 screenshots

   high✓ pass

   

   

   

   

   • Navigated to /resources and observed the Built-in Resources page with an Add Resource button.
   • Opened Add New Resource modal with required Resource URI and Content fields.
   • Clicked Save with empty Resource URI; form submission was prevented by required field validation and modal remained open.
   • Navigated to /resources and opened the 'Add Resource' modal.
   • Left Resource URI empty while filling 'Content without URI' into Resource Content.
   • Clicked Save button; HTML form validation required the Resource URI field, preventing form submission.
   • Verified that no invalid resource was created and the resource list remained unchanged.
4. S4

   Form Validation - Missing Resource Content

   8 steps, 4 screenshots

   high✓ pass

   

   

   

   

   • Navigated to Resources page showing existing built-in resources.
   • Opened Add New Resource modal form.
   • Entered URI 'file:///app/no-content.txt' and left Resource Content empty.
   • Clicking Save with empty content field prevented submission; modal remains open and required validation triggered.
   • Navigated to the /resources page while signed in as admin.
   • Clicked Add Resource to open the modal creation form.
   • Entered 'file:///app/no-content.txt' in the Resource URI field and left Resource Content empty.
   • Attempted to submit the form by clicking Save.
   • Observed that the form was not submitted: the required validation on the Resource Content field blocked submission and kept the dialog open without creating the resource.
5. S5

   Security - Unauthenticated Access to Resources

   2 steps, 2 screenshots

   high✓ pass

   

   

   • Navigated directly to /resources while unauthenticated; the application redirected to /login and did not expose the resources interface or any data.
   • Logged out of the current session to ensure the visitor is unauthenticated.
   • Attempted direct navigation to /resources without an active session.
   • The application immediately redirected unauthenticated requests from /resources to /login, preventing unauthorized access to system resources and controls.
6. S6

   Record Lifecycle - Edit Built-in Resource

   7 steps, 4 screenshots

   medium✓ pass

   

   

   

   

   • Logged into MCPHub dashboard as admin.
   • Navigated to Built-in Resources page showing two existing resources.
   • Updated Resource Content field with new JSON content.
   • Verified that the resource content modification persisted correctly upon reopening the edit dialog.
   • Successfully navigated to /resources and identified existing resource 'App Config'.
   • Opened edit modal, changed Resource Content from '{}' to '{"version": "1.1", "updated": true}', and saved.
   • Reopened the resource edit modal and verified that the updated content was persisted accurately.
7. S7

   Record Lifecycle - Delete Built-in Resource

   6 steps, 3 screenshots

   medium✓ pass

   

   

   

   • Navigated to /resources and observed 2 built-in resources in the list: 'App Config' (file:///app/config.json) and 'file:///app/minimal.txt'.
   • Clicked the Delete button for resource 'file:///app/minimal.txt', opening the 'Delete Resource' confirmation modal.
   • Confirmed deletion in the modal; the resource 'file:///app/minimal.txt' was removed from the list and the resource count updated to 1.
   • Built-in resource list displayed existing resources properly.
   • Clicking the Delete button triggered a confirmation modal displaying the resource name and a warning that the action cannot be undone.
   • Confirming deletion successfully removed the resource 'file:///app/minimal.txt' permanently, with count decreasing from 2 to 1 and persisting across page reload.
8. S8

   Validation - Duplicate Resource URI

   9 steps, 3 screenshots

   medium⊘ blocked

   

   

   

   • Navigated to /resources page where existing built-in resources are displayed.
   • Created first resource with URI file:///app/duplicate.txt successfully.
   • Navigated to /resources and created a new built-in resource with URI file:///app/duplicate.txt and initial content.
   • Verified that the first resource saved successfully and appeared in the resources list.
   • Reopened the Add Resource modal to submit a duplicate resource with the exact same URI file:///app/duplicate.txt.
   • The scenario reached the tool call limit before submitting the duplicate form to observe whether the backend validates or rejects duplicate URIs.
9. S9

   Persistence - State Survives Reload

   6 steps, 4 screenshots

   medium✓ pass

   

   

   

   

   • The resource file:///app/persist.txt persists and remains visible in the resource list after page reload.
   • Logged in as admin and navigated to /resources.
   • Created a new resource with URI file:///app/persist.txt and verified it was added to the list.
   • Reloaded the page at /resources and verified the newly created resource remained visible with URI file:///app/persist.txt, Active status, and text/plain MIME type.
10. S10

    State Control - Disabled Resource Handling

    9 steps, 3 screenshots

    medium✓ pass

    

    

    

    • Created resource with URI file:///app/disabled.txt and unchecked Enabled status; the resource was successfully added with an 'Inactive' status indicator in the UI list.
    • Navigated to /resources and opened Add Resource dialog.
    • Filled URI file:///app/disabled.txt, content 'Disabled test', and unchecked the Enabled checkbox.
    • Saved the resource and observed the new item displayed with an 'Inactive' status indicator badge in the resources list.
11. S11

    Validation - Whitespace-only values

    8 steps, 4 screenshots

    medium✓ pass

    

    

    

    

    • Navigated to the Built-in Resources page with 4 existing resources.
    • Opened the Add New Resource dialog showing required URI and Content fields.
    • Clicked Save with whitespace-only values; form displayed validation error 'URI is required' and refused submission.
    • Navigated to /resources and opened the 'Add New Resource' dialog modal.
    • Entered whitespace-only strings into the Resource URI and Resource Content fields.
    • Attempted to save the form, and the application rejected the input, displaying the validation error 'URI is required' without persisting any blank resource.
12. S12

    Form Boundary - Large Resource Content

    8 steps, 4 screenshots

    low✓ pass

    

    

    

    

    • Navigated to /resources page showing list of built-in resources.
    • Opened the Add New Resource modal.
    • Filled in Resource URI with 'file:///app/large.txt' and Resource Content with 5,330 characters of text.
    • Navigated to the /resources page where 4 initial built-in resources were listed.
    • Opened the Add New Resource modal and filled URI with 'file:///app/large.txt' and content with 5,330 characters.
    • Submitted the form by clicking Save; the modal closed properly after saving.
    • The new resource 'file:///app/large.txt' appeared in the resources list, increasing total resources count to 5.
    • The resource list layout remained completely intact, usable, and gracefully rendered.