Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for Screenshot Tests #695

Open
DenisBronx opened this issue Oct 17, 2024 · 0 comments
Open

Support for Screenshot Tests #695

DenisBronx opened this issue Oct 17, 2024 · 0 comments
Assignees
Labels
Feature Feature request issue type S: untriaged Status: issue reported but unprocessed

Comments

@DenisBronx
Copy link

DenisBronx commented Oct 17, 2024

What is your use-case and why do you need this feature?
With the recent release of the compose-screenshot-testing library by Google, I'm wondering if it's possible to integrate screenshot tests into the coverage report.

I understand that instrumented tests aren't supported, but since these screenshot tests are categorized under screenshotTest and function similarly to regular Java tests, could they still be included in the coverage report with minimal tweaks?

Describe the solution you'd like
Given that the official task for running these tests is named validateDebugScreenshotTest, I would expect the corresponding Gradle commands to be something like:

  1. koverVerifyDebugScreenshot
  2. koverHtmlReportDebugScreenshot
  3. koverXmlReportDebugScreenshot
  4. ...

I realize this could be a significant change, so if we need to create a custom task to include these tests, that would be perfectly acceptable.

@DenisBronx DenisBronx added Feature Feature request issue type S: untriaged Status: issue reported but unprocessed labels Oct 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Feature request issue type S: untriaged Status: issue reported but unprocessed
Projects
None yet
Development

No branches or pull requests

2 participants