Nishi vs the Field -- Automated Testing and Competitive Intel (Racing Crew)

Nishi Family › Compare › Automated Testing and Competitive Intel (Racing Crew)

Nishi vs the Field

Automated Testing and Competitive Intel (Racing Crew) — mechanically measured, liar-killed, sovereign.

Capability	Nishi	Playwright	Cypress	Selenium	Applitools	Notes
Vision forensics on the SHIPPED artifact (not source, not a proxy)	Yes	Yes	Yes	No	Part	Executes the real wasm on nx_wasm_vm and reads the framebuffer: blackout/frozen/magenta-leak/sky-ground structure; Applitools does screenshot AI-diff, but on browser captures not on the shipped bytes in our own VM
Seeded-repro fuzz determinism (any red = exact repro)	Yes	Yes	Yes	Yes	No	LCG seed printed in every finding; frames 1-6 byte-identical across runs; the loop auto-found + localized 2 miscalibrations on runs 1 and 2 (2026-07-03)
No-reference perceptual image-quality judge	Yes	No	No	No	Best	MSCN / NIQE-class 5-axis natural-scene statistics (reverse-AI photoreal judge); Applitools visual AI leads on learned diff
State invariants per tick	Yes	Yes	Yes	Yes	No	camera-y bounds + pitch-clamp checked every tick, not just at frame samples
Competitive-intel delta ledger (survey incumbents, drive roadmap)	Yes	No	No	No	No	Per-incumbent delta ledger with a 90-day survey cadence and next-due tracking (nx_cint_record/set_next_due); no test tool ships strategic competitive-intel as a primitive
Measured pitwall board (1:1 no-proxy)	Yes	No	No	No	No	The racing-crew scoreboard: measured position vs named incumbents, no proxy (nxasm 4x/size/determinism triple-exceed found + gated 2026-05-29)
Liar-killed competitive census plane	Yes	No	No	No	No	32 live head-to-head comparisons; every Nishi cell requires the symbol on disk, fabricated cells die at build -- the racing crew's find-gaps-vs-competitors engine, productized
UX / UI composition grading	Yes	Yes	Yes	No	Part	nx_ui_judge scores contrast/tokens/mobile; the field pairs with axe/Lighthouse, Applitools does visual UI diff
Real-browser WebDriver / CDP driver	No	Best	Best	Part	Yes	Playwright CDP + Selenium WebDriver are the bar; our harness runs wasm directly, the JS/canvas/DOM layer is outside it by construction -- the named next rung
Selector-based E2E scripting API	No	Part	Best	Best	Yes	Playwright locators + auto-wait are the bar; we fuzz inputs, we do not script user journeys
Visual-AI self-healing selectors	No	Yes	Yes	No	Part	Applitools self-healing locators + AI diff are the bar; our vision is heuristic forensics, not a learned model
Cross-browser cloud test grid	No	Best	Yes	Part	Best	Selenium Grid + BrowserStack are the bar; we run one interpreted VM
Network interception and mocking	No	Part	Part	Yes	No	Playwright route-mocking is the bar; absent here
Flaky-test detection and quarantine	No	Part	Best	Yes	No	Every mature suite quarantines flakies; ours is deterministic-by-seed so flakiness is structurally rarer, but no detector organ exists
Auto-record test codegen	No	Best	Part	Yes	No	Playwright codegen + Cypress Studio record user actions into tests; absent here (ties to the team census macro-recorder gap)
CI reporting and dashboards	No	Part	Part	Best	Best	JUnit/Allure reporting is the field standard; our forensics tables are console + the /compare board, no per-run CI surface
Accessibility auto-audit	No	Yes	Yes	No	No	axe-core / Lighthouse a11y are the bar; ties to the UI-quality doctrine but no automated a11y organ
LLM-driven test authoring and triage	No	Part	Best	No	Part	The cross-roster convergence gap (5th radar to point here); nobody in this field fully ships it either
Tests the shipped bytes on our own VM (sovereign, no external browser)	Best	No	No	No	No	The harness executes the ACTUAL deployed wasm in nx_wasm_vm and inspects VM memory + framebuffer host-side -- zero external browser, zero proxy, bit-exact; the field drives a real browser it does not own
Survey-incumbents-and-drive-the-roadmap as a standing primitive	Best	No	No	No	No	The racing doctrine is a compiled ledger + cadence + pitwall + the 32-comparison plane: honest delta-to-incumbent drives every roadmap; the test-automation field ships no strategic competitive-intel layer

Honest verdict. The Racing crew is the meta-team the operator named -- auto-find bugs, auto-resolve, and race every effort against named competitors by default -- and its most distinctive capabilities are ones the browser-automation field simply does not have. It tests the SHIPPED BYTES: seeded-fuzz + vision forensics execute the actual wasm on our own VM and LOOK at the rendered framebuffer (blackout, frozen-frame, magenta-leak, sky-ground structure), so any red is an exact seed+tick repro; the loop auto-found and localized two real miscalibrations on its first two runs. And competitive-intel is a STANDING PRIMITIVE: a delta-to-incumbent ledger on a 90-day survey cadence plus the pitwall board and the 32-comparison liar-killed /compare plane -- surveying incumbents to drive the roadmap, which no test tool ships. What it lacks is the field's entire interactive half: no real-browser WebDriver/CDP driver, no selector E2E scripting, no visual-AI self-healing locators (Applitools), no cross-browser cloud grid (the JS/canvas layer is outside our harness by construction), no flaky-test quarantine, no record-codegen, no accessibility audit. The climb: a sovereign WebDriver/CDP driver so the harness drives real pages, wire competitive-intel to auto-open a track per census, then flaky-detection and a11y.

Generated by nx_swcompare_matrix (sovereign NishiLang organ) from knowledge/compare/racing.matrix — every Nishi cell verified against real organ source on disk. Zero JS, zero trackers.