-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
ci: create ci workflow for multichain flow #12425
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #12425 +/- ##
==========================================
+ Coverage 56.41% 56.82% +0.41%
==========================================
Files 1797 1813 +16
Lines 40586 40862 +276
Branches 5097 5164 +67
==========================================
+ Hits 22896 23221 +325
+ Misses 16134 16054 -80
- Partials 1556 1587 +31 ☔ View full report in Codecov by Sentry. |
This reverts commit c9cecd1.
Bitrise✅✅✅ Commit hash: a2b3200 Note
|
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.
Awesome!
76ffa81
Bitrise✅✅✅ Commit hash: 6c51ab1 Note
|
Quality Gate passedIssues Measures |
Description
This PR addresses the new flows introduced with the updated network chain permissions functionality. The goal is to ensure comprehensive automated test coverage for these changes, reducing the risk of bugs found later in the development process.
Key things to note here:
breakdown of the CI workflows:
Smoke Pipeline: This pipeline runs all E2E tests with an enabled multichain flag. This ensures that engineers actively validate the new MC flows as part of their workflow. By default, the smoke pipeline runs on pull requests, allowing us to catch any issues with the MC flow before changes are merged into the main branch. We plan to make the smoke E2E pipeline a required step before merging PRs soon.
Regression Pipeline: This pipeline runs E2E tests with the multichain flag disabled. It ensures that existing functionality remains stable without the MC changes. The regression pipeline is scheduled to run every four hours against the main branch, providing frequent and consistent validation of the baseline functionality.
Related issues
Fixes:
Manual testing steps
Screenshots/Recordings
Before
After
Pre-merge author checklist
Pre-merge reviewer checklist