Conversation
|
Suggestions for
|
|
Suggestions for
|
|
Suggestions for
|
|
Suggestions for
|
|
Suggestions for
Using |
|
/review |
PR Reviewer Guide 🔍Here are some key observations to aid the review process:
🤖 Helpful? Please react with 👍/👎 | Questions❓Please reach out in Slack #ask-u-pr |
Codecov ReportAll modified and coverable lines are covered by tests ✅ @@ Coverage Diff @@
## release/2.10 #1111 +/- ##
===============================================
Coverage ? 25.17%
===============================================
Files ? 137
Lines ? 20216
Branches ? 0
===============================================
Hits ? 5089
Misses ? 15127
Partials ? 0
Flags with carried forward coverage won't be shown. Click here to find out more. |
…ity.testtools.codecoverage
[Delete any line or section that does not apply]
Purpose of this PR
Testing status
[Explanation of what’s tested, how tested and existing or new automation tests. Can include manual testing by self and/or QA. Specify test plans. Rarely acceptable to have no testing.]
Documentation status
[Overview of how documentation is affected by this change. If there is no effect on documentation, explain why. Otherwise, state which sections are changed and why.]
Technical risk
[Overall product level assessment of risk of change. Need technical risk & halo effect.]
Comments to reviewers
[Info per person for what to focus on, or historical info to understand who have previously reviewed and coverage. Help them get context.]
Package version
[Justification for updating either the patch, minor, or major version according to the semantic versioning rules]