News for hackers. Stuff that matters.
Re:Pytest 3.2.0 released by jwilk on Wednesday August 09, 2017 @08:27AM (#14967885)
I've been a long time nosetests user, but it's become unmaintained, so I'd like to migrate something else. pytest seems to be an obvious choice, but I really dislike the way it formats test failures. Is there a way to make it use a more traditional format?
Re:Pytest 3.2.0 released by jeremya on Wednesday August 09, 2017 @09:13AM (#14968363)
Yes, you can alter the way tracebacks are printed (or not printed) for test failures:

https://docs.pytest.org/en/latest/usage.html#modifying-pytho...

Re:Pytest 3.2.0 released by jwilk on Wednesday August 09, 2017 @10:34AM (#14969329)
Thanks! --tb=native combined with --color=no makes it almost bearable.

It still annoys me that

  ==================================================================================== FAILURES =====================================================================================
takes the whole screen width. I can pipe stdout through "cat" to fix it, but it's not very convenient.
Re:Pytest 3.2.0 released by variedthoughts on Thursday August 10, 2017 @03:45AM (#14977342)
Try -q
Re:Pytest 3.2.0 released by quodlibetor on Wednesday August 09, 2017 @09:35AM (#14968584)
Interesting. pytest's handling of `assert foo == bar` is one of my top two favorite things about it. My other favorite thing being fixtures.
Re:Pytest 3.2.0 released by drcongo on Wednesday August 09, 2017 @03:09PM (#14972554)
This is probably not to your taste, but I _love_ it: https://pivotfinland.com/pytest-sugar/
Re:Pytest 3.2.0 released by JustSomeNobody on Wednesday August 09, 2017 @09:05AM (#14968293)
Is nose buggy or is it missing features you need?
Re:Pytest 3.2.0 released by Alex3917 on Wednesday August 09, 2017 @10:29AM (#14969250)
Nose is buggy. Lots of memory leaks, things that don't work in parallel, etc.