What is BYOB Testing Extension?
The real-browser driver that lets the testing agent click, type, and scroll like a user. Scripted checks assert structure; the extension proves behavior.
Example
A checkout flow test fills the form, submits, and asserts the confirmation — in a real Chromium, against the preview URL, on every release.
Related terms
Visual Testing Agent
A preview-URL auditor that checks rendered pages like a visitor would. Read-only by default; writes structured findings the builder can act on.
Container Browser (CDP / Playwright)
The runner Chrome driven over DevTools protocol for automated checks. One shared browser, sessions with lifecycles — never install another one per test.
Smoke Check (npm run check / build)
The cheapest reliable gate: typecheck plus production build. Run it after every structural change — it catches breakage code review would take ten times longer to find.
Svelte Runes
The `$state`, `$derived`, `$effect`, and `$props` primitives powering Svelte 5 reactivity. Runes are mandatory in generated code: explicit, compilable, and consistent across every component.
File-Based Routing
Pages defined by file location: `+page.svelte` renders, `+layout.svelte` wraps, `+server.js` serves data. The route tree is the app map — no separate router config to drift.
Load Function
Server-side data loading for a route before it renders. Load on the server for content crawlers and users need immediately; reach for client fetching only for interactive extras.
Sources
Further reading
AI-Powered Testing Workflow with BYOB Extension
See how the BYOB extension, test modal, and project runner work together to execute browser-level test sessions with structured reports.
Feature-Based Testing in BYOB: Test One Capability Deeply
Learn when to use full-site testing versus feature-based testing in BYOB, and how to run tighter test cycles on critical user flows.