Yes, converting a django based project. On Tue, 4 Dec 2018 at 2:56 Craig de Stigter <craig...@gmail.com> wrote:
> Just after posting I re-read your post, and maybe I mis-read it the first > time. Are you referring to converting a django-based project, rather than > Django itself? > > On Tue, 4 Dec 2018 at 13:54 Craig de Stigter <craig...@gmail.com> wrote: > >> > gradually porting all tests >> >> Mostly-automated conversion is possible, so it doesn't have to be a >> gradual process. >> >> I wrote a script which converts xunit-style assertions into pytest ones: >> https://github.com/craigds/decrapify/blob/master/pytestify.py >> >> In the context of a large project port, my PR for OSGeo/gdal >> <https://github.com/osgeo/gdal/pull/963> is under consideration for >> merge. Most of the work was automated. >> >> I would expect a conversion of django's test suite to pytest to be >> simpler than the GDAL one (django's test suite is in far better shape to >> start with). As a heavy user of django, I'd be interested in taking the >> lead on it, or at least contributing in an advisory way. I'm not aware of >> any discussion on the django lists about this yet though. >> >> Is your question purely academic or are you considering submitting >> something to Django to work on this? >> >> Cheers >> Craig de Stigter >> >> On Mon, 3 Dec 2018 at 21:24 Sivan Grünberg <si...@vitakka.co> wrote: >> >>> Hi All, >>> >>> A transcript from a conversation about considering porting django >>> TestCase's to pytest: >>> >>> "Some counterpoints: >>> - Tomorrow `some_other_test` will be the guideline and pytest will be >>> passe >>> - Why add a new dependency when you have something built in, _if it's >>> good enough_ >>> >>> But all that is just conversation, the real issue i'm having is: >>> Now we have 2 ways of doing something in the project >>> consistency is my #1 goal or requirement in a project >>> Makes the codebase so much easier to maintain and learn (edited) >>> I'm trying to grok if pytest gives us such advantages that it's worth >>> gradually porting all tests to use it for consistency, but while the syntax >>> is nice you could achieve the same thing by reading those paramterized >>> lists in a loop i think?" >>> >>> Last remark was in reference to @pytest.mark.parametrize. >>> >>> Do we have a document somewhere to answer such? like a comparison that >>> outlines why it might be better to do so , or alternatively, to discuss the >>> contexts where sticking to Django TestCase's is better? >>> >>> Is there a full feature list that I may point people at when they ask me >>> "why pytest" ? >>> >>> Cheers, >>> >>> -Sivan >>> _______________________________________________ >>> pytest-dev mailing list >>> pytest-dev@python.org >>> https://mail.python.org/mailman/listinfo/pytest-dev >>> >> -- Sivan Greenberg Co founder & CTO Vitakka Consulting
_______________________________________________ pytest-dev mailing list pytest-dev@python.org https://mail.python.org/mailman/listinfo/pytest-dev
