-
Notifications
You must be signed in to change notification settings - Fork 667
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
Addition of pytest
case for not None
values for frames
and start
/stop
/step
#4769
Addition of pytest
case for not None
values for frames
and start
/stop
/step
#4769
Conversation
Added pytest case where both frames and start/stop/step are present to raise valueerror
Updated changelog to add coverage of raise error case where frames and start/stop/step are present
Hello @talagayev! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found: There are currently no PEP 8 issues detected in this Pull Request. Cheers! 🍻 Comment last updated at 2024-11-27 16:01:33 UTC |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #4769 +/- ##
===========================================
- Coverage 93.68% 93.66% -0.03%
===========================================
Files 177 189 +12
Lines 21742 22808 +1066
Branches 3055 3055
===========================================
+ Hits 20368 21362 +994
- Misses 927 1000 +73
+ Partials 447 446 -1 ☔ View full report in Codecov by Sentry. |
pytest
case for not None
values for frames
and start
/stop
/step
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.
LGTM @talagayev!
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.
Happy to discuss this further, but would prefer if we didn't fill up the changelog with small test changes.
removed Changelog change
now that I was working on a different Issue I noticed that |
@talagayev can you please resolve the conflict? Thanks. |
@RMeli it's now good to go :) |
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.
Thanks @talagayev.
Note for other reviewers: formatting will be sorted down the line, so I'm approving as-is.
Happy to help :) For the formatting for any upcoming PRs, I can run black through the added code if this would be preferred, or is |
Up to you, but in such case black should only affect the added code, not the whole file. We are using So either way is fine. If you don't format what you are writing, it will be automatically formatted with |
Ah I see, will then run it for the code snippets that I add, although I got a feeling that sometimes |
Yes, this page details how to use I'll give @IAlibay a chance to review, but don't worry about the formatting. |
Ah I see, thanks for the link, will take a look at it :) |
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.
Sorry didn't realise I was blocking here, lgtm.
Fixes #4648
Changes made in this Pull Request:
pytest
case intest_base.py
to cover the case whereframes
andstart
/stop
/step
are both specified as notNone
, leading to anValueError
PR Checklist
Developers certificate of origin
📚 Documentation preview 📚: https://mdanalysis--4769.org.readthedocs.build/en/4769/