-
Notifications
You must be signed in to change notification settings - Fork 699
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
Feature: GitHub Actions Workflow for Scheduled Morango Integration Tests #11931
Conversation
Build Artifacts
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The postgres configuration is absolutely required here, would be good to separate postgres and sqlite into separate jobs rather than sequential steps so we get a fuller report.
With thats done, doing a matrix of Python versions for Sqlite would add additional confidence.
…oduce Python version matrix for SQLite testing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Excellent, thank you! I can't spot any more issues with my eyes, so we'll let this run and see if it works!
Fixes #11903
Summary
Integration tests for Kolibri's morango implementation are crucial for testing syncing features across multiple instances. These tests are disabled by default and require specific conditions to run. To ensure regular testing, a new GitHub Actions workflow is proposed to run these tests on a weekly schedule.
…
References
…
Reviewer guidance
…
Testing checklist
PR process
Reviewer checklist
yarn
andpip
)