Implement playwright-core Monorepo Packages #1
Description
Priority: High
Estimate: 16-23 hours
Description
Migrate and implement core Playwright testing infrastructure from lytics-playwright into the new @lytics/playwright-core monorepo. This enables reusable, annotation-driven Playwright testing components for Lytics and Contentstack teams.
Goals
- ✅ Complete @lytics/playwright-annotations package (DONE)
- 📦 Implement @lytics/playwright-reporter with adapter architecture
- 🔌 Implement public adapters (Filesystem, Slack)
- 🔒 Implement internal adapters (Firestore)
- 🧪 Implement @lytics/playwright-journey for test generation
- 📝 Add ESLint plugin for annotation enforcement (optional)
- 🔄 Migrate lytics-playwright to consume new packages
Acceptance Criteria
- All 5 packages build successfully and pass tests
- Documentation complete for each package
- lytics-playwright successfully consumes the new packages
- CI/CD publishes packages to npm and GitHub Packages
- No breaking changes to existing test suite
Definition of Done
- All sub-issues completed and closed
- Packages published to registries
- lytics-playwright updated and tests passing
- Documentation and examples complete
- Knowledge share completed
Sub-Issues
- Implement @lytics/playwright-reporter package #2 - Implement @lytics/playwright-reporter package
- Implement @lytics/playwright-adapters-internal (Firestore) #3 - Implement @lytics/playwright-adapters-internal (Firestore)
- Implement @lytics/playwright-adapters (Filesystem & Slack) #4 - Implement @lytics/playwright-adapters (Filesystem & Slack)
- Implement @lytics/playwright-journey package #5 - Implement @lytics/playwright-journey package
- Add ESLint plugin for annotation enforcement #6 - Add ESLint plugin for annotation enforcement
- Migrate lytics-playwright to use @lytics/playwright-core #7 - Migrate lytics-playwright to use @lytics/playwright-core
- Create comprehensive documentation and examples #8 - Create comprehensive documentation and examples