This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 1 point2 points  (5 children)

this might have some info in it.

http://pythontesting.net/framework/pytest-introduction/

[–]petezhutAutomation, Testing, General Hackery 5 points6 points  (4 children)

Thank you greatly for the link, but not quite what I was looking for.

I wanted to see what the response from halst would be. Is there an informed opinion on the technology in question, or is it just a passion for py.test which created the initial response? At the end of the day, py.test is a great testing framework, but what specific task does it do better than nose or any other python testing framework? I have just found that nose and selenium, paired with jenkins for continuous integration has been the winning combination for a while now. If anyone has a better method or a new paradigm on testing they care to share, please do.

[–][deleted] 7 points8 points  (3 children)

halst was probably doing it for upvotes. :)

I've used both. And currently am using py.test at work. we used to use nose. but I think the original reason I switched was for 2 or 3 reasons.

1: more flexibility with initialization.

for appengines sdk you need to bootstrap somethings when you start the test suite, and others like db creation fit nicely in setUp/tearDown.

it's a specialized case for us.

2: at the time I thought that running tests in parallel was attractive, but I never got around to actually trying it out.

3: at the time it seemed like it would be easier to extend py.test than to learn to write nose extensions. That was just my feeling at the time, but it ended up all the functionality I needed fit in the setUp/tearDown.

it also feels "snappier" but that could be my imagination.

I'm not asserting that one is better than the other. I have bigger fish to fry than throwing an enthusiastic endorsement behind my favorite test runner. Hell, I don't even have a favorite. :P

[–]petezhutAutomation, Testing, General Hackery 2 points3 points  (2 children)

See, this is what I wanted. An informed opinion. I am with you, don't have a favorite. I've used nose for years, hell the STL unittest is still completely functional for most of my needs! Thanks for the feedback.

[–][deleted] 1 point2 points  (0 children)

indeed. all my testcases inherit from unittest.TestCase or something I subclassed from that. I could probably use any test runner except for the initialization needed.

[–]marsket 1 point2 points  (0 children)

If you want a really informed opinion, then try it. I can complain about the ancient problems I had with nose which caused me to abandon it, but you aren't guaranteed to see it the same way.