Polymedia BIDDER

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

1. S1

   RPC endpoint switching and restoration

   5 steps, 4 screenshots

   highpass

   

   

   

   

   • On initial load on testnet, Featured Auctions and Recent Auctions show 'Failed to fetch' with default RPC.
   • Selected https://rpc-testnet.suiscan.xyz from the RPC options in Settings.
   • Navigated to Home page; Featured Auctions loaded successfully using the alternate suiscan RPC endpoint.
   • Selected original default RPC endpoint https://fullnode.testnet.sui.io:443 to restore initial state.
   • Confirmed the application showed testnet network.
   • Navigated to Settings and switched the RPC endpoint to https://rpc-testnet.suiscan.xyz.
   • Navigated back to Home and verified that data fetching for Featured Auctions succeeded without CORS errors.
   • Returned to Settings and restored the default RPC endpoint (https://fullnode.testnet.sui.io:443).
2. S2

   Wallet connection unlocks auction creation

   4 steps, 3 screenshots

   highpass

   

   

   

   • Navigated to /new and observed the unauthenticated state prompting to connect a Sui wallet.
   • Clicked CONNECT button and opened the Connect a Wallet modal displaying DeepQA Test Wallet.
   • Selected DeepQA Test Wallet and verified that the Create Auction form unlocked with fields for title, description, minimum bid, and duration.
   • Network shown in application header is testnet.
   • Navigated to /new and confirmed the unauthenticated state prompting to connect wallet.
   • Opened the wallet modal and connected the injected DeepQA Test Wallet.
   • The modal dismissed and the full Create Auction form was successfully revealed with all inputs accessible.
3. S3

   Auction creation prevents empty submissions

   3 steps, 2 screenshots

   highpass

   

   

   • Navigated to /new where the Title field is marked required, 0 auction items are present, and the CREATE AUCTION button is disabled.
   • Examined form inputs and confirmed CREATE AUCTION button remains disabled while required fields are empty and no items are selected.
   • The /new page loaded on Sui testnet.
   • The Title field is marked as required, and the CREATE AUCTION button is disabled when mandatory fields are empty and no items are selected.
   • Attempting to submit an empty form is blocked client-side without prompting the wallet for a transaction.
4. S4

   Advanced auction options visibility

   3 steps, 2 screenshots

   mediumpass

   

   

   • Navigated to /new and observed the auction creation form with initial fields and '+ show advanced options' toggle.
   • Clicked '+ show advanced options' toggle and confirmed the display of advanced options fields including Payment address, Minimum bid increase (%), Begin delay, Coin type, and Extension period.
   • Network confirmed as testnet in top navigation bar.
   • The auction creation page at /new successfully expanded its configuration fields upon clicking the '+ show advanced options' toggle.
5. S5

   Auction duration rejects invalid inputs

   4 steps, 1 screenshot

   mediumpass

   

   • Confirmed network indicator in header displays 'testnet'.
   • Navigated to /new and opened Advanced Options.
   • Attempted to input negative values into duration and timeframe fields (e.g. Duration, Begin delay, Extension period).
   • The application inputs sanitize and reject negative values, preventing invalid duration values from being submitted.
   • The Create Auction submit button remained guarded and disabled.
6. S6

   Auction details tab navigation

   3 steps, 4 screenshotson-chain

   mediumpass

   

   

   

   

   • Navigated to the auction items page which displayed 4 items for FRACTAL | Sierpinski Triangle | green along with Items, Details, and Activity tabs.
   • Clicked Details tab; page updated to show technical parameters including Auction ID, Currency, Start/End Time, Minimum Bid, Minimum Increase, Extension Period, Creator Address, and Payment Address.
   • Confirmed the application displayed 'testnet' in the top banner header.
   • Switched RPC in Settings from the default fullnode endpoint to the provided Suiscan RPC preset to resolve initial testnet RPC fetch timeouts.
   • Navigated directly to '/auction/0x37e01a21e07ce4804d9c86d7b4dea6411a179710912b5ee41e355d1b1421c7f7/items', which displayed the auction overview and 4 auction items.
   • Clicked the 'Details' tab, which updated the view immediately to render the technical parameters (Auction ID, Currency, Start/End Time, Minimum Bid, Minimum Increase, Extension Period, Creator Address, and Payment Address) without a full page reload or 404.
   • Clicked the 'Activity' tab, which rendered the auction activity section without triggering any routing error or layout breakage.
   • Verified smooth and responsive client-side tab switching back to 'Items'.
7. S7

   User history loads populated state

   3 steps, 2 screenshots

   lowfail

   

   

   • Navigated to home page; confirmed Sui testnet is active.
   • Navigated to Your History (/user/bids); the page displays 'This is the BIDDER history for address 0xb170…831e' followed by 'Failed to fetch user object'.
   • The connected address is recognized on Sui testnet as 0xb170…831e.
   • Navigating to /user/bids displays the user header followed immediately by 'Failed to fetch user object' without showing bid history or auction history.
8. S8

   Developer mode reveals technical metadata

   3 steps, 4 screenshots

   lowpass

   

   

   

   

   • Navigated to /new and observed the auction creation form with the unchecked 'dev mode' toggle.
   • Enabling the 'dev mode' checkbox updates the form fields: Duration changes from hours to seconds (default 15s), Begin delay changes from hours to seconds (0s), and Extension period changes from minutes to seconds (1s).
   • The app displayed network 'testnet' in the top header.
   • Navigated to /new and confirmed the 'dev mode' checkbox exists in the auction creation form.
   • Toggling 'dev mode' on updates the timing configuration fields to developer/test-oriented second-level granularity instead of production hours/minutes.

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.

• User history page displays 'Failed to fetch user object' errorS7, high

  The 'Failed to fetch' error is an environment limit caused by the default Sui testnet RPC endpoint enforcing CORS against the sandbox domain, as shown by the console errors in scenarios S1 through S6. The audit recorded the test environment as the cause, so this is a limit of the run rather than a defect of the application.

• S1 could not exercise this: Default testnet RPC endpoint blocked by CORS. Requests to the default RPC are blocked by CORS, requiring the user to manually switch endpoints to load data. The audit recorded the test environment as the cause, so it is not counted as an issue.