Run browser tests in safari

[mcbarton]

Description

Please include a summary of changes, motivation and context for this PR.

Fixes # (issue)

Type of change

Please tick all options which are relevant.

• Bug fix
• New feature
• Added/removed dependencies
• Required documentation updates

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 81.78%. Comparing base (3f5166e) to head (adcf86a).

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #368      +/-   ##
==========================================
- Coverage   82.10%   81.78%   -0.32%     
==========================================
  Files          20       20              
  Lines         950      950              
  Branches       87       87              
==========================================
- Hits          780      777       -3     
- Misses        170      173       +3     

see 1 file with indirect coverage changes
see 1 file with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[vgvassilev]

Cool that we can run now tests in Safari too. Does it fail if something is broken?

[mcbarton]

Cool that we can run now tests in Safari too. Does it fail if something is broken?

@vgvassilev Yes it will fail if something is broken, because emrun will catch the non zero exit code, just like the other browsers. Selenium and safaridriver are just used to open the webpage in Safari, then emrun gets the output from the tests running (including the return value).

[mcbarton]

I will update this PR soon to use the relative path to safari test script to be consistent with what cppinterop does

[vgvassilev]

LGTM!