Skip to content

Conversation

@dipinknair
Copy link
Collaborator

@dipinknair dipinknair commented May 20, 2024

add additional case for deprecation warning

@dipinknair dipinknair requested a review from a team as a code owner May 20, 2024 15:53
@dipinknair dipinknair requested a review from koubaa May 20, 2024 15:54
@github-actions github-actions bot added the enhancement New features or code improvements label May 20, 2024
@github-actions github-actions bot added the documentation Improvements or additions to documentation label May 20, 2024
@codecov
Copy link

codecov bot commented May 20, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 81.06%. Comparing base (7bb4967) to head (c6fd15b).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #739      +/-   ##
==========================================
+ Coverage   81.01%   81.06%   +0.04%     
==========================================
  Files          32       32              
  Lines        2002     2002              
==========================================
+ Hits         1622     1623       +1     
+ Misses        380      379       -1     

@dipinknair dipinknair requested a review from koubaa May 20, 2024 16:08
@dipinknair dipinknair merged commit 7a1da28 into main May 20, 2024
@dipinknair dipinknair deleted the feat/deprecation_warning branch May 20, 2024 16:19
with pytest.warns(UserWarning):
struct.SystemID
harmonic_acoustic.SystemID
harmonic_acoustic.AnalysisSettings.MultipleRPMs = True
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

minor - putting both in a pytest.warns will technically allow the test to pass if one of these does not cause a deprecation warning. A better design would be to put each in its own pytest.warns block

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I already merged this. But I will make these changes in the other PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation enhancement New features or code improvements

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants