Hi Holger, everyone, On Thu, Apr 6, 2017 at 3:30 AM holger krekel <[email protected]> wrote:
> > I am fine to have user-tests guide the decision ... so now for me it's > only between offering a context manager or offering a special > "NoExceptionRaised" object which you can give to pytest.raises(...). > so we are almost there and for me, the user-testing can decide that so it's > not much discussion left to do at least from my side ... > Sorry for the delay! Made a quick poll again, showing all the possibilities we have been considering here (including giving up and not adding anything), and pytest.do_not_raise won by 100% of the opinions... but in fact only 5 people actually took interest and replied, so I don't think this pool has much value TBH. :P So for me there is already one useful outcome of our discussion here: > > - UI facing API is good to test against users/colleagues perceptions > as it gives real-life empirical clues instead of gut feelings > of implementors (including mine) > > - maintenance costs or a raise in internal complexities > also play into the evaluation of how/if to do something > Agreed! Cheers, Bruno
_______________________________________________ pytest-dev mailing list [email protected] https://mail.python.org/mailman/listinfo/pytest-dev
