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

[test] delete ControlObservableValueTest.png after test #2282

Merged
merged 1 commit into from
Sep 18, 2024

Conversation

jukzi
Copy link
Contributor

@jukzi jukzi commented Sep 17, 2024

2MB artifact in i builds

@jukzi jukzi requested a review from HeikoKlare September 17, 2024 07:16
@jukzi jukzi force-pushed the ControlObservableValueTest.png branch from a64b87a to b1192e0 Compare September 17, 2024 07:25
Copy link
Contributor

github-actions bot commented Sep 17, 2024

Test Results

 1 815 files  ±0   1 815 suites  ±0   1h 36m 58s ⏱️ - 7m 5s
 7 699 tests ±0   7 470 ✅  - 1  228 💤 ±0  1 ❌ +1 
24 258 runs  ±0  23 510 ✅  - 1  747 💤 ±0  1 ❌ +1 

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.

@akurtakov
Copy link
Member

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.

@jukzi
Copy link
Contributor Author

jukzi commented Sep 17, 2024

If the test fails the screenshots remain as artifact. That could be useful. Maybe better they would only be generated on fail?

@akurtakov
Copy link
Member

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.

@jukzi jukzi force-pushed the ControlObservableValueTest.png branch from b1192e0 to ba69873 Compare September 17, 2024 10:30
@jukzi jukzi force-pushed the ControlObservableValueTest.png branch from ba69873 to 8fe03bc Compare September 18, 2024 05:46
@jukzi
Copy link
Contributor Author

jukzi commented Sep 18, 2024

ignoring unrelated Download of osgi.bundle,org.eclipse.jface.examples.databinding,1.4.400.v20240424-0956 failed on linux

@jukzi jukzi merged commit dad3444 into eclipse-platform:master Sep 18, 2024
14 of 16 checks passed
@HeikoKlare
Copy link
Contributor

what is that png for? it is saved in ever build. for example

Screenshots like this are generally a "debugging" tool when trying to fix UI test.

The places where screenshots are saved that I have seen so far are for documenting and debugging inproper focus handling, like here:

if (!dialog.hasFocus()) {
String screenshotPath= ScreenshotTest.takeScreenshot(FindReplaceUITest.class, testName.getMethodName(), System.out);
fail("this test does not work on GTK unless the runtime workbench has focus. Screenshot: " + screenshotPath);
}

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants