-
-
Notifications
You must be signed in to change notification settings - Fork 498
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 for router.dart #2138
Test for router.dart #2138
Conversation
Our Pull Request Approval ProcessWe have these basic policies to make the approval process smoother for our volunteer team. Testing Your CodePlease make sure your code passes all tests. Our test code coverage system will fail if either of these two conditions occur:
The process helps maintain the overall reliability of the code base and is a prerequisite for getting your PR approved. Assigned reviewers regularly review the PR queue and tend to focus on PRs that are passing. ReviewersWhen your PR has been assigned reviewers contact them to get your code reviewed and approved via:
Reviewing Your CodeYour reviewer(s) will have the following roles:
Other🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #2138 +/- ##
===========================================
+ Coverage 78.99% 79.88% +0.88%
===========================================
Files 152 152
Lines 7456 7456
===========================================
+ Hits 5890 5956 +66
+ Misses 1566 1500 -66 ☔ View full report in Codecov by Sentry. |
@palisadoes, @Ayush0Chaudhary could you please suggest me why is the above test failing. |
It looks like a transient bug. Please do a minor commit to see whether it clears. |
@palisadoes I followed your suggestion by making a minor commit, but unfortunately, the issue continues to persist. After further investigation, it appears that the problem is linked to the GitHub Actions workflow. I'm seeking guidance on the best course of action to resolve this. Could you kindly advise on the next steps I should take to address this issue related to the GitHub Actions workflow? |
|
Ok |
@noman2002 can you please look into this issue |
Pull request #2139 demonstrates this issue more clearyly. |
The pull request target GitHub workflow has suddenly started to fail in this and other repos. The GitHub action hasn't been updated since September. A dependency has changed and the authors will need to fix it. We'll have to ignore it for now. |
@Azad99-9 Please |
got it @palisadoes . |
@aashimawadhwa please assign reviewers for this PR. |
ae4a4b7
into
PalisadoesFoundation:develop
* Modified the event edit test and made the code coverage of file edit_event_page to 100% * tests for router.dart * minor commit to fix failing bug. * test-pr * commiting after running dart format
What kind of change does this PR introduce?
This PR adds unit tests to the router.dart file
#1473
Fixes #1473
Did you add tests for your changes?
Yes
Snapshots/Videos:
If relevant, did you update the documentation?
No
Summary
The motive is to make the router.dart file 100% code covered.
Does this PR introduce a breaking change?
No
Other information
Created a new file: test/router_test.dart
Have you read the contributing guide?
Yes