bowman-lab / enspara

Modeling molecular ensembles with scalable data structures and parallel computing
https://enspara.readthedocs.io
GNU General Public License v3.0
33 stars 16 forks source link

nose -> pytests? #223

Closed Justin-J-Miller closed 5 months ago

Justin-J-Miller commented 5 months ago

There was some discussion in issue #214 about switching from nose to another testing suite. At the time the consensus was to switch to pytest. Is this still the preference?

Happy to poke at this in the coming days if so!

lgsmith commented 5 months ago

I think the one that seems most popular is the one that we should target. Nose doesn't seem to be maintained, and won't work with the most current version of python, so we can of course differ doing something about this if we want but it will eventually need to be addressed unless someone else picks up nose. The note to users has some suggestions for other test suites to use.

Edited to get rid of dumb miscopied link.

Justin-J-Miller commented 5 months ago

Yes, nose is no longer being maintained. There is nose2 which is mostly the same with some exceptions. Pytest seems to mostly work on our existing tests from my quick foray this morning. 

lgsmith commented 5 months ago

That's good. I think when we talked about this originally I'd thought pytest looked better. I think it may have been because the readme on nose2's github makes it seem like that is their recommendation. Maybe you saw that as well?

justinrporter commented 5 months ago

On projects after enspara I have used pytest and found it to be a very nice library. For whatever that’s worth.Sent from my iPhoneOn Apr 14, 2024, at 4:24 PM, lgsmith @.***> wrote: That's good. I think when we talked about this originally I'd thought pytest looked better. I think it may have been because the readme on nose2's github makes it seem like that is their recommendation. Maybe you saw that as well?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>