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 verification by default on regular testing tasks #1402

Open
sampengilly opened this issue May 1, 2024 · 0 comments
Open

Support verification by default on regular testing tasks #1402

sampengilly opened this issue May 1, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@sampengilly
Copy link

In an environment where there are mixed unit tests (unit tests for logic, UI behavioural tests using the compose rule and robolectric, tests for screenshoting using paparazzi, etc), I don't want to have to run multiple passes of all the tests by separately running testDebugUnitTest and verifyPaparazziDebug. If I'm already running my whole test suite using testDebugUnitTest then I should be able to configure the Paparazzi rule to perform its verification during that run.

I do not think that other proposed solutions in this issue tracker of excluding screenshot tests from testDebugUnitTest and including only the screenshot tests in verifyPaparazziDebug are really acceptable solutions. (example here: #1161)

I see that the Gradle plugin specifies a system property which configures whether the tasks are in record or verify mode. It appears that it selects that mode based upon whether the record or verify task is being run as part of the task graph.

I have attempted to set that property myself on a normal unit test run using ./gradlew testDebugUnitTest -Dpaparazzi.test.verify=true but it doesn't seem to have any effect.

Is there something I'm missing? Any way to configure the gradle tasks to perform the paparazzi verification during a standard test run?

@sampengilly sampengilly added the enhancement New feature or request label May 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant