Re: [GSOC] Shifting to Py.Test and Improving the Test Suite

2014-04-06 Thread Chris Wilson
Hi Andrew, On Sun, 6 Apr 2014, Andrew Pashkin wrote: * It makes it much harder to write custom assertions and get meaningful display on error. Can you give an examples for cases with messages/breakings and for custom assertions? I don't have an example of breakage to hand, I ripped out the

Re: [GSOC] Shifting to Py.Test and Improving the Test Suite

2014-04-06 Thread Andrew Pashkin
...Sometimes it gets different results (if one of the tested methods has side effects) and then the assertion message makes no sense, hides the problem, or pytest breaks. * It makes it much harder to write custom assertions and get meaningful display on error. Can you give an examples for ca

Re: [GSOC] Shifting to Py.Test and Improving the Test Suite

2014-04-06 Thread Ɓukasz Rekucki
On 6 April 2014 17:24, Andrew Pashkin wrote: > Some Pytest advocacy: > 1) Pytest has convenient tests collection options - you can just specify > folder to run all tests in it. It is also possible to filter tests by regex, > and select specific ones. Sounds good, but unittest's test discovery is

Re: [GSOC] Shifting to Py.Test and Improving the Test Suite

2014-04-06 Thread Chris Wilson
Hi Andrew, I'm not a Django core contributor but just a user and occasional patcher. I submit some comments on this proposal in the hope that they will be useful. On Sun, 6 Apr 2014, Andrew Pashkin wrote: Some Pytest advocacy: 1) Pytest has convenient tests collection options - you can just

Re: [GSOC] Shifting to Py.Test and Improving the Test Suite

2014-04-06 Thread Andrew Pashkin
Some Pytest advocacy: 1) Pytest has convenient tests collection options - you can just specify folder to run all tests in it. It is also possible to filter tests by regex, and select specific ones. 2) PyUnit: class MyTestCase(TestCase): def test_something(self): expected_content = ..