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 - oak-core-spi: 0.66 - oak-lucene: 0.81 - oak-solr-core: 0.53 - oak-segment-tar: 0.65 - oak-blob: 0.70 - oak-blob-plugins: 0.51 - oak-upgrade: 0.79 - oak-commons: 0.68 the coverage for the remaining modules were either way below < 50% or i felt that enforcing coverage doesn't make too much sense. if you wanted to get a feeling first how this would work, you can look at the following modules that already have it enabled: - oak-auth-external (0.8) - oak-auth-ldap (0.73) - oak-authorization-cug (0.97) wdyt? kind regards angela
