QA report: chainide.com
No confirmed defects were found, though layout constraints blocked interaction testing across several scenarios.
Exploratory testing exercised nine scenarios across navigation, dashboard views, legal pages, console error checks, and the Ethereum IDE workspace. Six scenarios passed successfully, including core navigation and project filtering. One initial finding regarding an unsupported chain recovery link was reviewed during the audit and withdrawn, leaving zero confirmed issues.
Three scenarios were blocked before completion: triggering a new project, initiating sign in, and recovering from an unsupported chain route. In each case, automated element visibility checks failed due to zero-height container layout structures on the page, preventing direct interaction with the targeted buttons and links.
While the functional flows that completed showed no errors, coverage of interactive workflows such as authentication and project creation remains incomplete due to these interaction blockers.
Run summary
| Metric | Count |
|---|
| Scenarios executed | 9 |
| Passed | 6 |
| Failed | 0 |
| Blocked | 3 |
| 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/
- Testing level: exploratory
- 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.
- Recovery link on unsupported chain 404 page is not interactable (S6, low): The record states the click attempt timed out because the link failed the test driver's automated interactivity checks, which is a limitation of the driver handling the page layout rather than a defective control.
Scenario results
| Scenario | Priority | Result | Issues |
|---|
| S1 Navigate to Projects Dashboard | high | pass | none |
| S2 Load Ethereum IDE Workspace | high | pass | none |
| S3 Filter Dashboard Projects | medium | pass | none |
| S4 Trigger New Project Action | medium | blocked (The 'New Project' button could not be interacted with due to non-interactive element visibility constraints on the dashboard page.) | none |
| S5 Trigger Sign In Action | medium | blocked (Automated driver could not interact with the Sign in button due to zero-height page layout container preventing standard element visibility checks.) | none |
| S6 Unsupported Chain 404 Recovery | medium | blocked after audit (The test could not perform click the recovery link, so the main result could not be checked.) | none |
| S7 Terms of Use Navigation | low | pass | none |
| S8 Privacy Policy Navigation | low | pass | none |
| S9 Verify Absence of Console Errors | low | pass | none |
The audit
The Critic reviewed 1 finding and ran 0 live replays in the browser, each on a fresh page. 0 of the 0 reported issues were reproduced live.
- The test driver was repeatedly blocked from interacting with page controls (buttons and links) due to visibility constraint failures, such as reading a 0px root height layout container, restricting the run's coverage of interactive features.
Coverage and caveats
In scope:
- Landing page navigation and legal links
- Projects dashboard guest experience
- Search functionality on the dashboard
- Unauthenticated Ethereum IDE workspace loading
- 404 error page handling and recovery
- Console error checking for cross-origin issues
Not covered:
- Sign-in and account registration flows (needs an account, out of scope for a hosted run)
- Wallet connection flows (requires third-party extensions and account, out of scope for a hosted run)
- Smart contract compilation and deployment (needs an account, out of scope for a hosted run)
- The application is tested as a guest user; authenticated project creation and code compilation cannot be completed.
- The guest experience permits loading the IDE workspace and dashboard, but may prompt for authentication on specific actions like creating a new project.
- S4 could not be executed: The 'New Project' button could not be interacted with due to non-interactive element visibility constraints on the dashboard page..
- S5 could not be executed: Automated driver could not interact with the Sign in button due to zero-height page layout container preventing standard element visibility checks..
- S6 could not be executed: The test could not perform click the recovery link, so the main result could not be checked..
By the numbers
| Metric | Value |
|---|
| Scenarios | 6 passed, 1 failed, 2 blocked of 9 (20 planned steps) |
| Browser actions | 103 (18 clicks, 6 inputs, 27 navigations, 52 snapshots) |
| Screenshots | 19 (2 explore, 17 scenario, 0 critic), 17 captioned |
| Coverage | 6 pages, 1 forms, 3 flows, 1 console errors |
| Audit | 1 findings, 0 re-verified live, 0 confirmed, 0 promoted, 1 withdrawn |
| Time | 19 min |
