Phase 9: Testing & QA Setup
I've set up the testing infrastructure, but we can't do full testing until we have content in the CMS. The agent created Playwright tests, Lighthouse CI configuration, and GitHub Actions workflows.
Phase 9: Testing & QA Setup
Date: January 6, 2026
Phase: Phase 9 - Testing & QA
Status: Infrastructure Complete, Awaiting Content
Note: This post is written from Joel's perspective (first person "I" = Joel). Technical details sections are clearly marked as written by the AI agent (Cursor - Claude Code).
I've set up the testing infrastructure, but we can't do full testing until we have content in the CMS. The agent created Playwright tests, Lighthouse CI configuration, and GitHub Actions workflows, but we'll need to populate content first to really test everything.
What's Been Set Up
Playwright E2E Tests
The agent created a full Playwright test suite with:
- Homepage tests (navigation, responsive design, dark mode)
- Accessibility tests (using @axe-core/playwright)
- Performance tests (Core Web Vitals, load times)
- Blog system tests (RSS feed, blog listing)
Lighthouse CI
Set up Lighthouse CI with:
- Configuration for 100 score targets
- GitHub Actions workflow
- Performance assertions
CI/CD Workflows
Created GitHub Actions workflows for:
- E2E tests on push/PR
- Lighthouse CI on main branch
- Test reports and artifacts
What's Blocking Full Testing
We need content in Agility CMS to properly test:
- Blog posts (to test blog listing and detail pages)
- Career entries (to test career timeline)
- Uses items (to test uses page)
- Pages (/about, /career, /uses)
The categories and tags are created, so we're ready to add blog posts. Once we have content, we can run the full test suite and Lighthouse audits.
Joel's Thoughts / Reflections
[Space for Joel to add personal thoughts, reactions, design decisions, or creative direction]