#35666 closed Cleanup/optimization (fixed)
Test stack level of deprecation warnings
Reported by: | Simon Charette | Owned by: | Simon Charette |
---|---|---|---|
Component: | Testing framework | Version: | 5.1 |
Severity: | Release blocker | Keywords: | |
Cc: | Triage Stage: | Ready for checkin | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
With another improperly set instance of stacklevel
and few others behind our belt I think it's worth documenting and adjusting our test suite to systematically test against the assertWarnsMessage.filename
to ensure is it properly assigned.
Change History (9)
comment:1 by , 3 months ago
Owner: | set to |
---|---|
Severity: | Normal → Release blocker |
Status: | new → assigned |
Triage Stage: | Unreviewed → Accepted |
comment:3 by , 3 months ago
Related PR from Adam that does not show in review queue so I'm adding it here for visibility.
comment:4 by , 3 months ago
Summary: | Stack level of deprecation warnings should be tested → Test stack level of deprecation warnings |
---|
comment:5 by , 3 months ago
Needs documentation: | set |
---|---|
Patch needs improvement: | set |
comment:6 by , 2 months ago
Needs documentation: | unset |
---|---|
Patch needs improvement: | unset |
Feedback addressed on Github. Feel free to re-organize the commits how you see fit Natalia.
comment:7 by , 2 months ago
Triage Stage: | Accepted → Ready for checkin |
---|
Note:
See TracTickets
for help on using tickets.
Thank you Simon, I agree with your rationale.
I think some of the commits from your PR should be backported to
5.1
so I'll be marking this as a release blocker for5.1
.