Re: [PATCH 2/2] test: pytest runner for the test suite

On Sun 08 Apr 2018 at 19:14 -0300, David Bremner wrote: > Floris Bruynooghe writes: > >> This series looks good to me, would be great to have! Do you want to >> commit them this or should I just incorporate it and submit together >> with tests once actual tests exist. You could

Re: [PATCH 2/2] test: pytest runner for the test suite

On Sun, Apr 08 2018, Floris Bruynooghe wrote: > This series looks good to me, would be great to have! Do you want to > commit them this or should I just incorporate it and submit together > with tests once actual tests exist. You could always commit with a ``def > test_dummy(): assert True`` or

Re: [PATCH 2/2] test: pytest runner for the test suite

This series looks good to me, would be great to have! Do you want to commit them this or should I just incorporate it and submit together with tests once actual tests exist. You could always commit with a ``def test_dummy(): assert True`` or something if you like. Thanks! Floris On Sat 07 Apr

[PATCH 2/2] test: pytest runner for the test suite

The 'test_subtest_known_broken' should be removed when there are actual tests to run. Based on a function from Tomi [1] [1]: id:m2r2nq23r9@guru.guru-group.fi --- test/T391-pytest.sh | 14 ++ 1 file changed, 14 insertions(+) create mode 100755 test/T391-pytest.sh diff --git