Remove test command in favor of tox

[hackebrot]

This PR introduces a better way of running the test suite. Instead of setting up a TestCommand in setup.py it leaves the dependency management for testing to tox. As a consequence I also removed mock from compat.py and setup.py. From what I know, it was solely used in tests (and grep did not report anything else).

The steps to run the test suite are as follows:

$ git clone https://github.com/audreyr/cookiecutter.git
$ cd cookiecutter/
$ mkvirtualenv -a $(pwd) cookiecutter
$ python setup.py develop

$ pip install tox
$ tox

I updated the contributor docs to reflect this behavior, which fixes #466.

Please let me know your thoughts!

Best
Raphael

[codecov-io]

Current coverage is 95.84%

Merging #480 into master will not affect coverage as of df31ead

@@            master    #480   diff @@
======================================
  Files           12      12       
  Stmts          457     457       
  Branches         0       0       
  Methods          0       0       
======================================
  Hit            438     438       
  Partial          0       0       
  Missed          19      19       

Review entire Coverage Diff

---

Uncovered Suggestions

1. +0.88% via cookiecutter/vcs.py#59...62
2. +0.66% via ...okiecutter/compat.py#70...72
3. +0.66% via ...okiecutter/compat.py#61...63
4. See 5 more...

Powered by Codecov

[hackebrot]

@michaeljoseph Do you happen to have time for a review? 😀

[michaeljoseph]

Do we still need this mock dependency?

[hackebrot]

Thank you @michaeljoseph and @pydanny for your thorough review 🙇

From what I know codecov reports the coverage for each of the test envs. If I get rid of --cov in the generic testenv it will stop doing so, I'm afraid. That's why I left this unchanged.

[michaeljoseph]

@hackebrot I meant, the generic testenv should have --cov=cookiecutter instead of --cov cookiecutter?
But it does seem to work as is...

[hackebrot]

I changed the test env command to also reflect the invocation from the official docs. https://pypi.python.org/pypi/pytest-cov

The docs now explain how to run flake8 via tox. However it only checks cookiecutter and ignores tests. We can exclude the dummy test data directories from flake8 though (they cause errors atm).

[michaeljoseph]

We could remove these sections entirely now right?

[hackebrot]

Yes, Sir! 👌

[michaeljoseph]

👍

[hackebrot]

😤

I'll rebase if you think we are all set here. LGTM

[vincentbernat]

The previous ways of doing things was generic. Due to the way tox works, it is not a general solution as we may wish to be able to test an installed version of cookiecutter without using virtualenv. python setup.py test should be able to test the same environment that python setup.py install configures.