-
Notifications
You must be signed in to change notification settings - Fork 197
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
[test] delete ControlObservableValueTest.png after test #2282
[test] delete ControlObservableValueTest.png after test #2282
Conversation
@HeikoKlare what is that png for? it is saved in ever build. for example |
a64b87a
to
b1192e0
Compare
Test Results 1 815 files ±0 1 815 suites ±0 1h 36m 58s ⏱️ - 7m 5s For more details on these failures, see this check. Results for commit 8fe03bc. ± Comparison against base commit 8d647ea. ♻️ This comment has been updated with latest results. |
Screenshots like this are generally a "debugging" tool when trying to fix UI test. If they are deleted like that they can not be inspected so it's probably better to not generate them at all. |
If the test fails the screenshots remain as artifact. That could be useful. Maybe better they would only be generated on fail? |
If you manage to do that it would be awecome. |
b1192e0
to
ba69873
Compare
2MB artifact in I Builds
ba69873
to
8fe03bc
Compare
ignoring unrelated |
The places where screenshots are saved that I have seen so far are for documenting and debugging inproper focus handling, like here: Lines 84 to 87 in be54f35
So your fix to only save the screenshot in case the failure that needs to be analyzed via that screenshot occurs is the right thing to do. |
2MB artifact in i builds