Updating our support strategy for Safari

Hello. We had discussed this in the past and one idea was to add support for IE/Edge and Safari on windows by adding a windows agent machine and modifying our jenkins pipeline to support it, when TC would have support for it and when there would be some docker images for it (original message: http://markmail.org/message/ldzazc7s2uoqkk2n ).

The assumption was that Safari on Windows shouldn’t be too different from Safari on Mac.

I had also opened an related issue: Add support for Microsoft Edge · Issue #766 · testcontainers/testcontainers-java · GitHub

Now, one reason we didn’t push on this is also because we realized that Safari has moved to webkit and thus testing on Chrome was testing a lot for Safari too. And it seem it’s been true since we haven’t had a lot problem in lots of years.

So right now, my preference would indeed to do the following:

  • Indicate that we don’t support Safari to the same level as the other browsers
  • Discuss with @ilie.andriuta to see if he’d be ok to do some tests on Safari every N months. Note: Safari can be installed on Windows
  • I’d prefer to not use another testing tool like browserstack. Or we could use it as test if we wanted to move all our tests there but I fear that could degrade stuff in our build (would we be able to fail the build when it fails on browserstack, can we control setup of the VMS there like being able to have LO installed, etc). We would also be quite dependent on the day they stop supporting us.