Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test pipeline #4

Closed
wants to merge 13 commits into from
Closed

Test pipeline #4

wants to merge 13 commits into from

Conversation

AlexioDanje
Copy link
Collaborator

No description provided.

adanje added 13 commits December 10, 2024 12:18
Comprehensive testing setup across the project:
- Configure Vitest for unit testing
- Set up @testing-library/react for component testing
- Add coverage reporting and thresholds
- Create test documentation
- Add test scripts to package.json
- Configure .gitignore for test artifacts

The testing infrastructure includes:
- Unit tests for services and utilities
- Component tests with React Testing Library
- Coverage requirements (80% threshold)
- CI integration with coverage checks
- Add /user/ prefix to UserService API endpoint paths to match backend changes
- Update AddRealmComponent test with new dashboard configuration fields
- Align test expectations with current dev branch implementation

These changes sync the tests with modifications introduced in the dev branch,
fixing broken tests for user management endpoints and realm creation.
Implement complete GitHub Actions workflow with:
- Automated testing with coverage reporting
- Code quality analysis via Code Climate
- Build verification and artifact storage
- Security scanning with Snyk
- NPM caching for faster builds

Configuration includes:
- Coverage thresholds (80% across all metrics)
- Code quality thresholds via .codeclimate.yml
- Test artifacts preservation
- Dependency vulnerability scanning
- Build artifact management
Implement complete GitHub Actions workflow with:
- Automated testing with coverage reporting
- Code quality analysis via Code Climate
- Build verification and artifact storage
- Security scanning with Snyk
@timler
Copy link
Collaborator

timler commented Dec 11, 2024

Snyk checks have failed. 1 issues have been found so far.

Icon Severity Issues
Critical 0
High 0
Medium 1
Low 0

security/snyk check is complete. 1 issues have been found. (View Details)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants