-
-
Notifications
You must be signed in to change notification settings - Fork 553
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
Refactor test_experiment_step_termination.py*** #3800
Refactor test_experiment_step_termination.py*** #3800
Conversation
(from unittest to pytest)
Thanks for starting this @abhicodes369. It looks good, but ideally we want to do this after #3617, so I will let this sit for a while until that is complete and |
@abhicodes369, if you're interested, you can help drive #3857 to completion – or we can take this up again after it gets merged (should be about a week at most). |
I will look into 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.
Codacy raises a warning on assert statements despite the fact that it is the recommended way to write pytest
-style tests and that these are test files. This can be disabled later, some insights here: fossasia/query-server#332
@allcontributors please add @abhicodes369 for tests |
I've put up a pull request to add @abhicodes369! 🎉 |
Thanks, @abhicodes369! |
thanks @agriyakhetarpal it really means a lot |
* Refactor test_experiment_step_termination.py*** (from unittest to pytest) * style: pre-commit fixes --------- Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com> Co-authored-by: Agriya Khetarpal <[email protected]>
(from unit test to pytest)
Description
converted a unit test case that uses the unit test to pytest. On the official website of pybamm I saw that they are considering migrating from unit test to pytest.