Rbanh/schemeta
1
0
Fork 0
Code Issues 11 Pull Requests Actions 1 Packages Projects Releases Wiki Activity

Expand browser QA scenario with dense analog sample and readability assertions #14

New Issue
Closed
opened 2026-02-18 21:33:39 -05:00 by Rbanh · 1 comment
Rbanh commented 2026-02-18 21:33:39 -05:00
Owner
Copy Link

Objective

Extend browser QA to validate readability and diagnostics on a dense analog schematic case.

Scope

  • Add dense analog sample fixture representing known clutter risk.
  • Add scripted browser flow to run compile/layout modes on this sample.
  • Assert readability-oriented metrics and diagnostics sanity (crossings/overlaps, warnings, tie-net usage expectations).

Acceptance Criteria

  • Dense sample scenario runs in automated browser QA.
  • Threshold assertions catch readability regressions.
  • Failures produce useful artifacts for triage.
## Objective Extend browser QA to validate readability and diagnostics on a dense analog schematic case. ## Scope - Add dense analog sample fixture representing known clutter risk. - Add scripted browser flow to run compile/layout modes on this sample. - Assert readability-oriented metrics and diagnostics sanity (`crossings/overlaps`, warnings, tie-net usage expectations). ## Acceptance Criteria - Dense sample scenario runs in automated browser QA. - Threshold assertions catch readability regressions. - Failures produce useful artifacts for triage.
Rbanh added this to the Phase 3 - Browser QA and UX Consistency milestone 2026-02-18 21:34:07 -05:00
Rbanh commented 2026-02-18 21:44:52 -05:00
Author
Owner
Copy Link

Completed in commit d5836a2.

Delivered:

  • Added dense analog fixture (examples/dense-analog.json).
  • Extended browser QA to compile/layout this case and assert readability-oriented thresholds.
  • Added artifacts to support triage on threshold failures.

Validation:

  • Executed in npm run test:ui flow.
Completed in commit `d5836a2`. Delivered: - Added dense analog fixture (`examples/dense-analog.json`). - Extended browser QA to compile/layout this case and assert readability-oriented thresholds. - Added artifacts to support triage on threshold failures. Validation: - Executed in `npm run test:ui` flow.
Rbanh closed this issue 2026-02-18 21:45:02 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Phase 3 - Browser QA and UX Consistency
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Rbanh/schemeta#14
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?