You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 testDebugUnitTestandverifyPaparazziDebug. 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?
The text was updated successfully, but these errors were encountered:
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.
The system property needs to exist inside the test JVM, you set it on the Gradle Daemon with -D.
I don't want to have to run multiple passes of all the tests by separately running testDebugUnitTest and verifyPaparazziDebug.
I think it wasn't feasible to separate the source sets up until now, even now it'll take a while to get it stable in AGP, and then adoption (if at all), see my recent comment on the issue.
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
andverifyPaparazziDebug
. If I'm already running my whole test suite usingtestDebugUnitTest
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 inverifyPaparazziDebug
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?
The text was updated successfully, but these errors were encountered: