On 2017-05-11 12:05, Angela Schreiber wrote:
hi oak-devs
as a follow up to http://markmail.org/message/rzbqwwx3lilshct6 i would
like to suggest that we enforce minimal test coverage not only with
security modules but also for other oak code that is used in production.
i gave it a try and identified those modules that already have a somewhat
sensible coverage as this exercise IMO doesn't make sense for modules that
are poorly tested.
enforcing minimal coverage would mean that the module build will fail if
the coverage is no longer met.
the figures (computed yesterday) look as follows:
- oak-jcr: 0.71
- oak-core: 0.75
> ...
To get coverage for oak-core, one should run with
a) MongoDB running and
b) Derby RDB profile.
Did you try that?
Best regards, Julian
