QA report: chainide.com
Core IDE workflows succeeded and no application defects were confirmed during testing.
Testing exercised the core Ethereum IDE workflows on ChainIDE, including guest workspace initialization, Solidity template compilation, JavaScript VM connection, UI panel toggling, bottom tool pane navigation, and contract deployment on the Arc testnet.
No confirmed issues remain after audit. A single finding concerning Solidity compiler settings persistence across page reloads was withdrawn during review, leaving zero defects across all evaluated flows.
Four scenarios were blocked from completion due to external testnet and wallet network matching constraints or unverified assertions, leaving injected Web3 provider connection, rejected transaction recovery, and Polygon workspace loading partially unverified.
Run summary
| Metric | Count |
|---|
| Scenarios executed | 11 |
| Passed | 7 |
| Failed | 0 |
| Blocked | 4 |
| Findings raised | 1 |
| Issues after the audit | 0 |
| Withdrawn by the audit | 1 |
| Critical / high / medium / low | 0 / 0 / 0 / 0 |
- Target: https://chainide.com/s/ethereum
- Testing level: core_workflow
- Stack: unknown
Issues
No issues survived the audit.
Withdrawn findings
The Critic re-examined these claims and found the evidence did not support them. They are kept here rather than deleted.
- Solidity compiler Optimization setting does not persist across page reloads (S7, low): The replay explicitly initialized a completely new workspace by clicking 'Creating Project' after the reload, which correctly loads the default unoptimized compiler settings rather than restoring the previous unpersisted session.
Scenario results
| Scenario | Priority | Result | Issues |
|---|
| S4 Connect to Injected Web3 Provider | high | blocked (the app cannot be put on the run's chain The wallet step never ran.) | none |
| S10 Deploy contract and reject transaction | high | blocked (the app cannot be put on the run's chain) | none |
| S11 Deploy contract successfully on Arc testnet | high | pass | none |
| S8 Load Polygon multi-chain workspace | high | blocked (the app cannot be put on the run's chain) | none |
| S1 Initialize guest workspace and load contract | high | pass | none |
| S2 Compile standard Solidity template | high | pass | none |
| S3 Connect to JavaScript VM wallet | high | pass | none |
| S5 Toggle IDE side panels | medium | pass | none |
| S6 Navigate bottom tool panes | medium | pass | none |
| S7 Persist local browser settings across reloads | medium | blocked after audit (The failure rested only on findings the audit set aside, so the main result was not checked.) | none |
| S9 Check start page load integrity | low | pass | none |
The audit
The Critic reviewed 1 finding and ran 1 live replay in the browser, each on a fresh page. 0 of the 0 reported issues were reproduced live.
- The tester blocked scenarios S4, S8, and S10 citing a network mismatch with the test wallet's pinned Arc testnet, yet S11 passed and successfully deployed a contract on that exact same network.
- Scenario S10 was marked as blocked even though its observations clearly show its expected result of gracefully recovering from a rejected transaction was fully met.
- A possible defect in S1 ("HTTP 400 error logged during workspace initialization") was not promoted: the live replay came back not-reproduced.
Coverage and caveats
In scope:
- Ethereum and Polygon workspaces
- Guest workspace initialization
- Solidity compilation flows
- Wallet connections (Injected and JS VM)
- Contract deployment state handling via injected test wallet
- IDE layout, side panels, and tool panes
Not covered:
- GitHub authentication (requires account, out of scope for hosted target)
- External origin navigation outside /s/ bounds
- An injected test wallet on Arc testnet (chain id 5042002) is available.
- The 'deploy interactions tab' reported in the AppMap contains standard deployment controls to initiate transactions.
- Connecting to the Polygon workspace requests a network switch to Polygon, triggering the required wrong-network test since the test wallet strictly enforces Arc testnet.
- S4 could not be executed: the app cannot be put on the run's chain The wallet step never ran..
- S10 could not be executed: the app cannot be put on the run's chain.
- S8 could not be executed: the app cannot be put on the run's chain.
- S7 could not be executed: The failure rested only on findings the audit set aside, so the main result was not checked..
By the numbers
| Metric | Value |
|---|
| Scenarios | 7 passed, 0 failed, 4 blocked of 11 (45 planned steps) |
| Browser actions | 242 (90 clicks, 2 inputs, 14 navigations, 136 snapshots) |
| Screenshots | 21 (0 explore, 21 scenario, 0 critic), 21 captioned |
| Coverage | 3 pages, 1 forms, 3 flows, 1 console errors |
| Audit | 1 findings, 1 re-verified live, 0 confirmed, 0 promoted, 1 withdrawn |
| Time | 15 min |
| Wallet | 1 transactions, 0 signatures, 1 refusals on chain 5042002 |
