resume/.cursor/rules/deployment-workflow.mdc

63 lines
1.7 KiB
Plaintext

---
description:
globs:
alwaysApply: false
---
# Deployment Workflow
## Testing Requirements
- All changes must be tested locally before deployment
- Tests must pass for both mobile and desktop viewports
- Lighthouse tests must maintain perfect scores (100/100) for accessibility and SEO
- Playwright tests must pass for all viewport sizes
## Git Operations
- Avoid use direct git commands (`git add`, `git commit`, `git push`) if we do git flows do then as oneliners.
- All git operations must be performed through `./build-test-deploy.sh`
- The script handles:
- Building the Docker container
- Running all tests
- Committing changes
- Pushing to repository
## Build-Test-Deploy Script
The `./build-test-deploy.sh` script is the single source of truth for deployment:
1. Builds the Docker container
2. Runs the test suite
3. Only proceeds with git operations if tests pass
4. Handles all git operations in the correct order
## Testing Process
1. Make changes to the codebase
2. Run `./build-test-deploy.sh` to:
- Build the container
- Run tests
- Deploy if tests pass
3. If tests fail:
- Fix the issues
- Run the script again
- Do not proceed with deployment until all tests pass
## Viewport Testing
The test suite runs against multiple viewport sizes:
- Mobile: 375x667
- Desktop: 1024x768
All tests must pass for all viewport sizes before deployment is allowed.
## Lighthouse Requirements
Maintain perfect scores:
- Accessibility: 100/100
- SEO: 100/100
- Performance: 97/100 minimum
- Best Practices: 93/100 minimum
## Playwright Tests
Must pass all accessibility tests:
- WCAG 2.1 Level AAA compliance
- ARIA attributes
- Heading structure
- External link validation
- Color contrast
- Image alt text