kotlinx-kover icon indicating copy to clipboard operation
kotlinx-kover copied to clipboard

Results 101 kotlinx-kover issues
Sort by recently updated
recently updated
newest added

Using TestKit allows to run tests more flexible, download an arbitrary distribution from the network. This can help to implement running combinations of tests.

Feature
S: postponed

It is necessary to: - restructure the current documentation - add a FAQ block for simple cases - describe the most basic cases for typical cases (Kotlin Plugin Type +...

S: in progress

Kover looks _very exciting_! Thank you for the Gradle plugin. Request: an equivalent Maven plugin. Projects I work on are around 50/50 Gradle/Maven for builds (these are for backend, not...

Feature
S: postponed
Kover Maven Plugin

**What is your use-case and why do you need this feature?** Property `variantName` will help to filter Kover tasks by selecting those that relate to specific variant. So, to find...

Feature
S: ready for release

**Describe what you would like to clarify about Kover** My project is multi modules, multi flavors, with the following structure ``` RootDir - app -> with 2 flavors: Dev &...

Question
S: in progress

When generating HTML reports and during verification, any nested classes are analyzed and displayed separately. From the point of view of Kotlin code, this is not entirely correct, because these...

Feature
Implement in KGP

**What is your use-case and why do you need this feature?** If the testing does not take place in one build run, but is distributed over several builds, for example,...

Feature
S: confirmed

Hi Kover Team! I have a CI which runs unit tests on multiple shards. I want to configure Kover to make it run a subset of projects. So, say my...

Question
S: waiting for clarification

I use Kover on an Android app that uses Compose for its UI. As we don't really want (for now) to have coverage on Compose code, we've excluded the `@Composable`...

Question
S: waiting for clarification

**Describe the bug** I just noticed that the coverage report showed 0% coverage for some classes which there already are tests. The logs show that these tests are being executed...

Bug
S: waiting for clarification