Re: [pytest-dev] process for replacing yield tests with modern style

2016-11-28 Thread Chris Dent
On Mon, 31 Oct 2016, Chris Dent wrote: On Fri, 28 Oct 2016, Chris Dent wrote: * questions when I get stuck with gabbi I've made some progress on this but I'm still not entirely satisfied with the solution. I've encapsulate the necessary changes in a pull request https://github.com/cdent/g

Re: [pytest-dev] process for replacing yield tests with modern style

2016-10-31 Thread Chris Dent
On Fri, 28 Oct 2016, Chris Dent wrote: On Sat, 22 Oct 2016, holger krekel wrote: So let's now get to your original example at https://github.com/tiddlyweb/tiddlyweb/blob/master/test/http_runner.py and that might be enough to increase my understanding so that I can deal with the considerably mo

Re: [pytest-dev] process for replacing yield tests with modern style

2016-10-28 Thread Chris Dent
On Sat, 22 Oct 2016, holger krekel wrote: maybe there is a solution ... Thanks I think this has potentially given me enough to at least fix the old simple version found in: So let's now get to your original example at https://github.com/tiddlyweb/tiddlyweb/blob/master/test/http_runner.py a

Re: [pytest-dev] process for replacing yield tests with modern style

2016-10-22 Thread holger krekel
Hi Chris, all, maybe there is a solution ... On Fri, Oct 21, 2016 at 13:03 +0100, Chris Dent wrote: > Several years ago, when I started using pytest, the yield tests were > my favorite thing about it. Super simple: push out functions that > have assertions in them. That's what pytest was all abou

Re: [pytest-dev] process for replacing yield tests with modern style

2016-10-21 Thread Chris Dent
On Thu, 20 Oct 2016, Floris Bruynooghe wrote: On 29 August 2016 at 09:31, Ronny Pfannschmidt wrote: Hi Chris, currently there is no easy/good Replacement for the use-case you outline. the "correct" way would be a custom py.test specific collector Yeah, a custom collector is the way to go he

Re: [pytest-dev] process for replacing yield tests with modern style

2016-10-20 Thread Floris Bruynooghe
On 29 August 2016 at 09:31, Ronny Pfannschmidt wrote: > Hi Chris, > > currently there is no easy/good Replacement for the use-case you outline. > the "correct" way would be a custom py.test specific collector Yeah, a custom collector is the way to go here. I agree that it was never really the co

Re: [pytest-dev] process for replacing yield tests with modern style

2016-08-29 Thread Ronny Pfannschmidt
Hi Chris, currently there is no easy/good Replacement for the use-case you outline. the "correct" way would be a custom py.test specific collector note that it was mostly luck this worked at all - ever since py.test switched to collect first yield tests where semantically broken due to running an

[pytest-dev] process for replacing yield tests with modern style

2016-08-24 Thread Chris Dent
Several years ago I developed a relative simple YAML-based way of doing HTTP tests. The processed turned yaml into tests and yielded them for pytest to collect. At the time yield was the pytest approved way of doing such things. That's here: https://github.com/tiddlyweb/tiddlyweb/blob/master/