-
Notifications
You must be signed in to change notification settings - Fork 632
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
fix: Fix issue #3244 #3246
fix: Fix issue #3244 #3246
Conversation
@giuseppe2028 you need to update the Paparazzi screenshots https://github.com/Ivy-Apps/ivy-wallet/blob/main/docs/CI-Troubleshooting.md#paparazzi-tests |
temp/legacy-code/src/main/java/com/ivy/legacy/ui/component/transaction/TransactionCard.kt
Show resolved
Hide resolved
temp/legacy-code/src/main/java/com/ivy/legacy/ui/component/transaction/TransactionCard.kt
Show resolved
Hide resolved
01f962f
to
6f3b1e5
Compare
I have tried all the possible solution, but the test does not run yet. |
@giuseppe2028 try increasing this to ivy-wallet/shared/ui/testing/src/main/java/com/ivy/ui/testing/PaparazziScreenshotTest.kt Line 14 in 8f0360f
|
We recently updated Compose and there might be flaky Paparazzi tests. Also update your branch to be on top of the latest |
This #3243 should improve this suboptimal developer experience |
# Conflicts: # screen/transactions/src/test/snapshots/images/com.ivy.transactions_TransactionsPaparazziTest_snapshot Transactions Screen[Dark].png # screen/transactions/src/test/snapshots/images/com.ivy.transactions_TransactionsPaparazziTest_snapshot Transactions Screen[Light].png # shared/ui/testing/src/main/java/com/ivy/ui/testing/PaparazziScreenshotTest.kt
Pull Request (PR) Checklist
Please check if your pull request fulfills the following requirements:
main
branch.What's changed?
Describe with a few bullets what's new:
Risk Factors
What may go wrong if we merge your PR?
In what cases your code won't work?
0620.mov
Does this PR closes any GitHub Issues?
Check Ivy Wallet Issues.
Troubleshooting CI failures ❌
GitHub Actions failing? Read our CI Troubleshooting guide.