[Feature] Add E2E and Unit Test CI Pipeline #33
Description
[Feature] Add E2E and Unit Test CI Pipeline
Description
Currently, the project lacks automated continuous integration (CI) for End-to-End (E2E) tests and Unit Tests (UT). This creates risks for code quality and can lead to undetected regressions in pull requests.
Motivation
- Code Quality: Automated testing ensures code changes don't introduce bugs
- Development Efficiency: Catch issues early in the development cycle
- Confidence: Developers can refactor and add features with confidence
- Review Process: PR reviewers can see test results before merging
- Consistent Testing: Tests run in a standardized environment for all contributors
Proposed Solution
Add GitHub Actions workflows to run:
1. Unit Tests (UT)
- Run on every push and pull request
- Execute all unit tests in the project
- Generate code coverage reports
- Fail if tests don't pass or coverage drops below threshold
2. End-to-End Tests (E2E)
- Run on pull requests to main/master branch
- Set up required test environment (Docker, databases, etc.)
- Execute E2E test suites
- Capture test artifacts (logs, screenshots) on failure