pytest-check 2.0.0b1 available to test.

pip install pytest-check --pre

Change modifies default behavior and deprecates a flag (a new flag, but still).

Reasons: makes it by default faster.

- new `--check-max-tb=0` flag replaces `--check-no-tb`.
- default is for check-max-tb=1

PR: https://github.com/okken/pytest-check/pull/110

I'd love to hear feedback.😀

Speak now or forever (you know how it goes ) file issues without reading the README or the Changelog. 😩 Is that too real for a holiday?

#pytest #pythontesting

2.0.0 - new --check-max-tb, defaults to 1, deprecate --check-no-tb by okken · Pull Request #110 · okken/pytest-check

The default behavior has changed. Since --check-max-tb=1 is the default, the default behavior is now: Show traceback for the first failure per test. (controlled by --check-max-tb, default is 1) Sh...

GitHub
No feedback yet.
@brianokken I can sing a song about missing feedback. It is about time we meet at a conference or so 👨‍🎤
@jugmac00 will you be at either PyCascades or PyConUS?
@jugmac00 also I would like you to be on test & code

@brianokken That would be soooo awesome! 🎉

That said.. work is pretty busy and I need to finish some tax things urgently.

What about getting in touch in February again? At very latest in March?

Good thing is... I am currently preparing/submitting a couple of talks about the journey to #tox version 4. Maybe that would be something you would like to talk about?

Except you like to know more about the German tax system 😉

@jugmac00 Talking about tox sounds great. Remind me in Feb or March, or just pencil something in. I'll send you some info.

@brianokken I definitely cannot attend PyConUS, as it overlaps with a mandatory work event. The one who set up this date is probably a Java dev or so 😂

I never considered attending PyCascades although I heard amazing things about it. Oh, and it is already in March! I certainly missed the cfp deadline.

Do you plan to speak at these conferences?

And just in case... do you plan to visit Europe this year?

@jugmac00 speaking at PyCascades. Haven't heard back from PyConUS yet

I'd love to get back to Europe. Work trips are pretty slim still. None planned.

I'd have to get a sponsored trip for a conference talk or training gig somewhere.

@brianokken wondering if you would consider integration with subtests
@ossronny subtests seem like a separate solution to the same problem. But sure, why not?

@brianokken it's all about partitioning of reports, checks is about groups of soft assets, subtests is about numbered or named subsections of tests

IMHO the assert groups fit test sections as reporting detail

@ossronny do you use subtests much?
@brianokken currently primarily in some acceptance e2e testing, for most smaller stuff parameterization wins
@ossronny I’ll look into it sometime. I’m not familiar with the guts of subtests.
@brianokken I found it really nice, however as part of my workflow I use `pytest --pdb` a lot to debug my tests it seems useless whit check.check_func
@mgreco yep. Doesn’t work for that.
@brianokken I'm wondering (from my ignorance) if it could be possible using the post mortem mechanism to solve this... probably not, but it's just an idea that I could explore (maybe a PR).