Enable the python setup.py test command.

[Kentzo]

No description provided.

[Martiusweb]

Hi,

Thanks for you pull-requests. I'll try to review them tomorrow or Friday.

[Kentzo]

No problem.

[Martiusweb]

Thanks for all your PRs.

Unfortunately this one will not work as it is, because test/__init__.py imports all modules of the package so they're discovered when running python -m unittest test. Emptying test/__init__.py will fix this, but there are some things to change: since python -m unittest test will not work anymore:

• README and travis configuration needs to be updated to use python setup.py test,
• test_case_await should probably not be discovered as being part of the suite, hence renamed or ignored in a way,
• the configuration of test_suite should rather be set in setup.cfg.

[Kentzo]

@Martiusweb Hmm, it seems to work for me (Python 3.6.3) with only one test failing:

FAIL: test_patch_generator_with_multiple_scopes_on_same_dict (test.test_mock.Test_patch_dict_decorator_coroutine_or_generator_scope) [Outher: GLOBAL, inner: LIMITED]
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/kentzo/Documents/Work/GreatFruit/asynctest/test/test_mock.py", line 782, in test_patch_generator_with_multiple_scopes_on_same_dict
    (self.is_patched(), self.second_is_patched()))
AssertionError: Tuples differ: (True, False) != (True, True)

First differing element 1:
False
True

- (True, False)
+ (True, True)

[Kentzo]

@Martiusweb Updated the PR to allow running tests via -m unittest, setup.py test and pytest (setup.py pytest too if you have pytest-runner installed).

Integrated coveralls, but you have to activate it for the repo. Here is an example for my fork: https://coveralls.io/builds/18737375

[Kentzo]

@Martiusweb For coveralls to work on Appveyor, the COVERALLS_REPO_TOKEN has to be set manually after you active the project there.

[Kentzo]

@Martiusweb Anything missing?