Issues #146, #147 and #149

[arcivanov]

Fix coverage not failing when forked
Make unittest and coverage library functions

[mriehl]

Thanks for the good catch and even more so for the fix. Can you provide a concrete example use case why it is useful to have coverage as a library function?

[arcivanov]

@mriehl definitely!
In Maven, which pybuilder seems to attempt to simulate there is an ability to create several "executions" (https://maven.apache.org/guides/mini/guide-configuring-plugins.html#Using_the_executions_Tag) of the same plugin with different configurations that would allow running unit tests or integration tests or packaging with varying parameters in the build cycle.

If unit tests can be run multiple times, it is respectively desirable for coverage to be run for those unit tests as well (also with different configurations).

Forking of unit tests in addition to coverage provides module reloading isolation between the unit test executions.

Using library calls allows an external plugin to invoke unit test and coverage in custom tasks stepping around reactor.execute_task (for example to replace integrationtest plugin with several invocations of unittest calls). It's generally very desirable for all plugins to expose API to be library-call friendly for custom plugins to interface with each other.

[arcivanov]

In fact, I'm going to refactor to use "execution_prefix" and "execution_name" for respective arguments.

[arcivanov]

@mriehl shouldn't this line be in start_coverage after start?

[mriehl]

Thanks, fantastic work on these issues. Would you consider accepting write privileges on the repo so that it's easier to contribute?

[arcivanov]

@mriehl yep, that definitely would be helpful, thanks!