[RFC] add tox.ini / support for pytest

[blueyed]

This is rudimentary, but makes it a lot easier to run the tests.

Please consider adopting it and mention it in the docs.
It could also be used on Travis.

[coveralls]

Coverage remained the same at 99.63% when pulling 730edf7 on blueyed:tox into 7c92536 on djangonauts:master.

[nemesifier]

@blueyed excellent suggestion. I have always been lazy on this subject. I would like to go ahead on this, could you rewrite the Test section of the README and .travis.yml too?

[auvipy]

welcome changes!!

[blueyed]

I've hoped that you would pick it up from here.
I can do it, of course - but not soonish.. ;)

[nemesifier]

"Now is better than never, although never is probably better than right now" (cit.)

[blueyed]

never is probably better than right now

I am taking this. Feel free to adopt it, of course.

[nemesifier]

I don't understand why you closed it. Can it stay open as a reminder for when me or other contributors will have time to look into it?

[coveralls]

Coverage remained the same at 99.63% when pulling 730edf7 on blueyed:tox into 7c92536 on djangonauts:master.

[coveralls]

Coverage remained the same at 99.63% when pulling 730edf7 on blueyed:tox into 7c92536 on djangonauts:master.

[blueyed]

Can it stay open as a reminder for when me or other contributors will have time to look into it?

Sure. I understood it wrongly then in the beginning - and came across it when going through my open PRs. Sorry.

[blueyed]

I've updated it: it now allows you to use pytest/pytest-django through tox (used in one matrix entry on Travis).

I'll need to revisit myself, but would appreciate any comments/review on it already.

[nemesifier]

@blueyed great!

Could you squash the commits?

One question, why adding pytest to the build? Wouldn't that slow down the build with no practical advantage?

[nemesifier]

could you remove this extra blank line?

[nemesifier]

I'm ignorant of pytest, what's this section for?

[blueyed]

Could you squash the commits?

Sure, please never merge fixup! commits.. :)

One question, why adding pytest to the build? Wouldn't that slow down the build with no practical advantage?

Only for demo.. we could use pytest for only one / a few in the end.

[nemesifier]

@blueyed can we keep it simple and avoid adding unneeded dependencies to the build please?

[blueyed]

What's the problem with having one build also pip-install pytest/pytest-django?
It is more comfortable to have pytest as a test runner, therefore I added it to tox / config for it, but then I think it should also get tested/used on CI to catch any problems with it.

[nemesifier]

I don't want to use more resources than needed and I don't want to slow down the build unnecessarily. We are using a free service after all.

Developers can use pytest offline in their own dev environment.

[blueyed]

Do you really think an additional pip install pytest pytest-django about once per month is a problem for Travis?! (https://travis-ci.org/djangonauts/django-rest-framework-gis/pull_requests)

But given that, please comment on the build matrix I came up with otherwise - there are probably things to strip there then?!

[blueyed]

Old (9 builds): https://travis-ci.org/djangonauts/django-rest-framework-gis/builds/229053544
New (11, but 10 with -pytest (re)moved): https://travis-ci.org/djangonauts/django-rest-framework-gis/builds/232514268; but covers Django 1.11.

To be clear: my idea was to use py36-dj110-pytest instead of py36-dj110 - which would result in 10 builds.

[blueyed]

Squashed, and removed pytest from Travis. Also the config for it - still works through Tox.

[nemesifier]

@blueyed thanks a lot 👍!

[blueyed]

@nemesisdesign
Thanks for merging it! :)