Historical (April 2026). This describes the consolidation from the FastAPI backend to Next.js. Phase 16 (2026-08-28) deleted the FastAPI backend, the backend-proxy layer and the legacy UI this plan refers to; nothing here describes TestForge today. Kept for history only — see README.md.
Phase 12 - CI/CD Pipeline Enhancement
Goal
Automate code quality checks, build verification, and test execution across GitHub Actions to ensure production-ready code on every commit and pull request.
Scope
- Add comprehensive build step to existing smoke and regression workflows.
- Create a new PR validation workflow for immediate feedback on pull requests.
- Document CI/CD structure and artifact retention policies.
- No application code changes.
Changes
1. Enhanced Smoke Test Workflow (self-test.yml)
- Added
npm run build step after lint
- Ensures Next.js production build succeeds before running tests
- Runs on: main push, pull request, manual trigger
2. Enhanced Regression Test Workflow (regression-test.yml)
- Added
npm run build step after lint
- Ensures Next.js production build succeeds before running tests
- Runs on: manual trigger
- Retention: 30 days (keeps last 5 runs)
3. New PR Validation Workflow (pr-validation.yml)
- Runs on pull request (opened, synchronized, reopened)
- Sequential checks: lint → build → smoke tests
- Posts success/failure comments to PR thread
- Blocks merge if any check fails (via required status check)
Validation Checklist
- ✅ npm run lint — no errors
- ✅ npm run build — Next.js build succeeds
- ✅ npm run test:self — smoke tests pass
Artifact Management
- Smoke Allure reports retained for 30 days (latest 5)
- Regression Allure reports retained for 30 days (latest 5)
- Automatic cleanup via GitHub Actions script
Success Criteria
- All workflows execute successfully
- Build step validates Next.js production configuration
- PR validation provides immediate feedback
- No test regressions from workflow changes
Safety
- Workflows are read-only for artifacts and contents
- No deployment or push actions
- Can be safely enabled in production CI/CD
Next Steps
- Review workflow files for correctness
- Enable branch protection rules requiring PR validation
- Monitor workflow execution times and optimize if needed
- Extend with deployment step in Phase 13