setup.py test is configurable and with coverage

[boyska]

the previous collector was difficult to configure, while now everything
can be done just editing the standard setup.cfg

Unit test coverage is a useful indicator when writing unit tests!

[boyska]

@ael-code you have some experience with setuptools, so you are a good candidate for reviewing this. Anyone else is welcome, of course!

[ael-code]

probably I'm doing something wrong.

• checked out the branch
• python setup develop

test command is not installed

[boyska]

@ael-code what do you mean by test command is not installed ? It should be
python setup.py test. I'll clarify the docs.

[ael-code]

sorry for the stupid question :) it works

[boyska]

That was not stupid, that was missing doc. Now the docs is not missing anymore ;)

[ael-code]

maybe I merged too early.

I did not understand... looking at nose docs seems that python setup.py nosetests make the same thing you implemented without the need to introduce a custom command.

I'm confused.

[boyska]

On Tue, Feb 24, 2015 at 10:03:15AM -0800, ael wrote:

I did not understand... looking at nose docs seems that python setup.py nosetests make the same thing you implemented but without the need to introduce a custom command.

not exactly. That command is so few configurable that it is very
difficult to make it read setup.cfg. Reading many webpages (I'm now too
lazy to find them all) I discovered that even the nose project is not
liking that "bundled" command, and is suggesting the other approach
instead.

[ael-code]

fine 👍