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

Pytest style analysis/ #1568

merged 2 commits into from Aug 1, 2017


None yet
4 participants

utkbansal commented Jul 30, 2017

Fixes #

Changes made in this Pull Request:

PR Checklist

  • Tests?
  • Docs?
  • CHANGELOG updated?
  • Issue raised/referenced?

It is nice to see the comments we made in the previous PR being already tackled in this one 👍

@utkbansal utkbansal changed the title from [Review Needed]Pytest style analysis/ to Pytest style analysis/ Jul 30, 2017

assert_almost_equal(, 1.485, 3)
def test_fit(self):
p = self._make_p()
def test_fit(self, p):

This comment has been minimized.


kain88-de Jul 30, 2017


please have p run in the fixture.

This comment has been minimized.


kain88-de Jul 30, 2017


Then we can see to make the fixture module wide to save the initialization cost of the analyzsis

This comment has been minimized.


jbarnoud Jul 30, 2017


@utkbansal This p_run fixture should use the p fixture. The p fixtureneeds to remain ortest_raise_NoDataError` will be broken.

@richardjgowers richardjgowers merged commit 8e3f0e1 into MDAnalysis:develop Aug 1, 2017

2 checks passed

continuous-integration/travis-ci/pr The Travis CI build passed
coverage/coveralls Coverage remained the same at 90.419%
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment