-
Notifications
You must be signed in to change notification settings - Fork 18
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
DM-7235: Pytest updates #72
Conversation
4a1518c
to
6c4e663
Compare
utilsTests.run(suite()) | ||
class MatchMemoryTestCase(lsst.utils.tests.MemoryTestCase): | ||
pass | ||
|
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.
Is there a desire to homogenize the name of the memory test class? I see three different ones here (none of which are TestMemory as suggested in @timj's slides & the DM Developer Guide).
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.
The name doesn't matter. I have no opinion on whether it should be standardized.
With the caveat that I am currently unable to actually pull this down & run it myself, this all looks fine, but please consider the following:
|
b96a306
to
51ecda8
Compare
This commit updates some of the tests to use the py.test framework. This includes checking for bad uses of assert_, assertEquals, and assertTrue, the lsstUtils alias, as well as cleaning up the test code with autopep8 to comply with the LSST PEP8 standard.
This required extensive modifications so that the data creation happens only once.
A few of the tests in pipe_tasks have non-standard names i.e. names that do not begin with test. This commit renames those tests by adding 'test' in front of the old name and capitalizing the former first character.
ea923a1
to
b7d3ea9
Compare
No description provided.