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
Having two MacOS folders, one for Intel and one for ARM.
File Structure could be like this:
.
└── macos/
├── intel
└── arm
or
.
├── macos-intel
└── macos-arm
Reasoning
If you run Golden Tests with an Intel Mac, it will produce different Golden Images than an Apple Silicon Mac and vice versa.
To be able to test on both platforms reliable, it would be great to have two folders. One for each architecture.
Additional context and comments
No response
The text was updated successfully, but these errors were encountered:
Very interested in this fix. We are currently bypassing this by forcing all machines to use the X86_64 version of Flutter to generate image and run the tests for comparison; which 'works' but decreases test time a bit.
We could also use this to let ARM machines generate both the intel and arm goldens if wanted.
This seems fairly doable. My initial thought is within goldenTest we could detect the architecture and pass that along to the FilePathResolver. I think we'd want to have a caching mechanism so we're not invoking Process.run for every test. I think it would be safe to have this be global because we shouldn't be changing platforms/architectures in the middle of a suite run.
Is there an existing feature request for this?
Command
Differ between Intel Macs & Apple Silicon Macs
Description
Having two MacOS folders, one for Intel and one for ARM.
File Structure could be like this:
or
Reasoning
If you run Golden Tests with an Intel Mac, it will produce different Golden Images than an Apple Silicon Mac and vice versa.
To be able to test on both platforms reliable, it would be great to have two folders. One for each architecture.
Additional context and comments
No response
The text was updated successfully, but these errors were encountered: