Astro
Astro's hybrid rendering model is one of its most powerful features — you can mix static site generation (SSG) and server-side rendering (SSR) in the same project, choosing per page. A blog index might be static, a user dashboard SSR, and a product page somewhere in between with
Astro
Astro's island architecture is one of its defining features — you get static HTML for most of your page, with interactive components (islands) hydrated only where needed. This composable model is excellent for performance, but it introduces unique testing challenges: when does hydration happen? How do you test client:
Astro
End-to-end tests are where Astro's architecture really gets tested — navigation between pages, form submissions, SSR data loading, hydration of islands, and the subtle differences between your dev server and production build. Playwright is the right tool for this. It's fast, runs in real browsers,
Astro
Astro's component model is unique — .astro files are compiled at build time, which means standard component testing approaches from React or Vue don't apply directly. But with Vitest and Astro's experimental container API, you can write fast, reliable unit tests for your Astro components
Astro
Astro's API routes (files in src/pages/api/) let you build backend endpoints alongside your frontend pages. They handle HTTP methods, parse request bodies, set cookies, and return JSON — all within the same project. But they need their own testing approach: unit tests for handler logic, integration tests
Test Automation
Astro's build output is mostly static HTML. That makes it fast and SEO-friendly — and it also makes testing feel optional right up until something breaks in production. A misconfigured endpoint returns 500s, an interactive island stops hydrating, or a content collection query returns an empty array after