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
{{ message }}
This repository has been archived by the owner on Sep 1, 2021. It is now read-only.
I have some unit tests which compares the content of a Canvas with a PNG containing the expected output. Unfortunately tests like these are not deterministic because of hardware acceleration. My workstation supports hardware acceleration but my CI system does not. So the output is slightly different and therefor tests are failing because the actual canvas doesn't match the expected output.
This can be fixed by disabling hardware acceleration but unfortunately there is no such option in jest-electron-runner yet. I guess the easiest way would be implementing an environment variable like JEST_ELECTRON_RUNNER_DISABLE_HARDWARE_ACCELERATION.
Or maybe it is a good idea to disable hardware acceleration by default and let users enable it on demand with an environment variable like JEST_ELECTRON_RUNNER_ENABLE_HARDWARE_ACCELERATION?
The text was updated successfully, but these errors were encountered:
I have some unit tests which compares the content of a Canvas with a PNG containing the expected output. Unfortunately tests like these are not deterministic because of hardware acceleration. My workstation supports hardware acceleration but my CI system does not. So the output is slightly different and therefor tests are failing because the actual canvas doesn't match the expected output.
This can be fixed by disabling hardware acceleration but unfortunately there is no such option in jest-electron-runner yet. I guess the easiest way would be implementing an environment variable like JEST_ELECTRON_RUNNER_DISABLE_HARDWARE_ACCELERATION.
Or maybe it is a good idea to disable hardware acceleration by default and let users enable it on demand with an environment variable like JEST_ELECTRON_RUNNER_ENABLE_HARDWARE_ACCELERATION?
The text was updated successfully, but these errors were encountered: