astro-test-perf
Astro CI Test Performance Analysis
Fetch a recent CI run from withastro/astro, parse test durations from the logs, and
produce a performance report showing the slowest tests across all suites and platforms.
Background: Astro CI Structure
Astro's CI workflow (.github/workflows/ci.yml) runs these test suites:
| Suite | Job name pattern | Test runner | Platforms |
|---|---|---|---|
| Astro | Test (astro): <os> (node@<ver>) |
Node.js test runner | Ubuntu Node 22/24, macOS Node 24, Windows Node 24 |
| Integrations | Test (integrations): <os> (node@<ver>) |
Node.js test runner | Same as Astro |
| E2E | Test (E2E): <os> (node@<ver>) |
Playwright (Chrome + Firefox) | Ubuntu Node 22, Windows Node 22 |
Each suite runs across multiple platform/Node version combinations defined in the CI
matrix. The Astro and Integrations suites use Turbo to run test commands, and the test
output uses the Node.js test runner format with ✔/✗ markers and durations in
parentheses. E2E uses Playwright which outputs dot-progress and summary lines.
More from withastro/astro-maintainer-skills
security-advisory-review
>
1astro-preview-release
Trigger and monitor a preview release for an Astro pull request. Use this skill whenever the user wants to publish a preview/canary build of an Astro PR so that reporters or users can test a fix before it merges — including phrases like "create a preview release", "add the preview label", "let someone test this PR", "publish a canary for this fix", or "how do I get a preview package for this PR". Specific to the withastro/astro monorepo and pkg.pr.new.
1