Reenable 4 fragment shader tests#180875
Conversation
There was a problem hiding this comment.
Code Review
This pull request re-enables several fragment shader tests for the Impeller backend by changing them from _runSkiaTest to the standard test function. The changes also include updating a build configuration to generate necessary shader variants for Impeller and applying a temporary workaround in one of the tests to use setFloat instead of getUniformFloat for setting uniforms, with a TODO to revert this change later. The changes look good and are aligned with the goal of increasing test coverage on Impeller. I have one suggestion to improve maintainability in the BUILD.gn file by deduplicating some flags.
| shader_target_flags = [ | ||
| "--sksl", | ||
| "--runtime-stage-metal", | ||
| "--runtime-stage-gles", | ||
| "--runtime-stage-vulkan", | ||
| ] |
There was a problem hiding this comment.
The list of runtime stage flags is duplicated in the sampler_order_fixture target within this file (lines 47-49). To improve maintainability and avoid this duplication, consider defining these flags in a shared variable.
This aligns with the style guide principle to "Avoid duplicating state".
For example, you could define a variable at the top of the file:
_impeller_runtime_stages = [
"--runtime-stage-metal",
"--runtime-stage-gles",
"--runtime-stage-vulkan",
]And then use it in ink_sparkle:
shader_target_flags = [ "--sksl" ] + _impeller_runtime_stagesAnd in sampler_order_fixture:
shader_target_flags = _impeller_runtime_stagesReferences
- The style guide advises to 'Avoid duplicating state: Keep only one source of truth.' The list of runtime stage flags is duplicated in this file. (link)
|
Golden file changes have been found for this pull request. Click here to view and triage (e.g. because this is an intentional change). If you are still iterating on this change and are not ready to resolve the images on the Flutter Gold dashboard, consider marking this PR as a draft pull request above. You will still be able to view image results on the dashboard, commenting will be silenced, and the check will not try to resolve itself until marked ready for review. For more guidance, visit Writing a golden file test for Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing. |
issue flutter#180764 turns on 4 disabled tests ## Pre-launch Checklist - [x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [x] I read the [Tree Hygiene] wiki page, which explains my responsibilities. - [x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement]. - [x] I signed the [CLA]. - [x] I listed at least one issue that this PR fixes in the description above. - [x] I updated/added relevant documentation (doc comments with `///`). - [x] I added new tests to check the change I am making, or this PR is [test-exempt]. - [x] I followed the [breaking change policy] and added [Data Driven Fixes] where supported. - [x] All existing and new tests are passing. If you need help, consider asking for advice on the #hackers-new channel on [Discord]. **Note**: The Flutter team is currently trialing the use of [Gemini Code Assist for GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code). Comments from the `gemini-code-assist` bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed. <!-- Links --> [Contributor Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#overview [Tree Hygiene]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md [test-exempt]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#tests [Flutter Style Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md [Features we expect every widget to implement]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md#features-we-expect-every-widget-to-implement [CLA]: https://cla.developers.google.com/ [flutter/tests]: https://github.com/flutter/tests [breaking change policy]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#handling-breaking-changes [Discord]: https://github.com/flutter/flutter/blob/main/docs/contributing/Chat.md [Data Driven Fixes]: https://github.com/flutter/flutter/blob/main/docs/contributing/Data-driven-Fixes.md
issue #180764
turns on 4 disabled tests
Pre-launch Checklist
///).If you need help, consider asking for advice on the #hackers-new channel on Discord.
Note: The Flutter team is currently trialing the use of Gemini Code Assist for GitHub. Comments from the
gemini-code-assistbot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.