[GH-ISSUE #281] FIx Safari tests in Selenium on Travis CI #243

New issue

Open

opened 2026-02-25 21:34:32 +03:00 by kerem · 1 comment

kerem commented

2026-02-25 21:34:32 +03:00

Owner

Originally created by @jasonmunro on GitHub (Aug 28, 2018).
Original GitHub issue: https://github.com/cypht-org/cypht/issues/281

Originally assigned to: @jasonmunro on GitHub.

Safari in Browserstack is a bit temperamental. Most of the issues are resolved, need to figure out the rest and enable in Travis builds

Originally created by @jasonmunro on GitHub (Aug 28, 2018). Original GitHub issue: https://github.com/cypht-org/cypht/issues/281 Originally assigned to: @jasonmunro on GitHub. Safari in Browserstack is a bit temperamental. Most of the issues are resolved, need to figure out the rest and enable in Travis builds

kerem added the

research

tests

labels

2026-02-25 21:34:32 +03:00

kerem commented

2026-02-25 21:34:32 +03:00

Author

Owner

@jasonmunro commented on GitHub (Aug 28, 2018):

I have enabled Safari tests in Travis/Browserstack, but the situation is pretty bleak.

Using Browserstack from my local dev environment, 5 tests fail. Same tests every time, which is promising since I can probably code work arounds
Using Browserstack from Travis, tons of test fail for various reason. Many fail because I can't get the browser window to maximize from Travis, which works from my local environment. Likely this is due to a version difference between the two environments somewhere (selenium?).
For all other browsers, we exit on error if a Selenium test fails, but for now we don't for Safari. This way we still get notified if tests expected to pass fail, but I can keep Safari running in Travis while I work on figuring out solutions.

@jasonmunro commented on GitHub (Aug 28, 2018): I have enabled Safari tests in Travis/Browserstack, but the situation is pretty bleak. - Using Browserstack from my local dev environment, 5 tests fail. Same tests every time, which is promising since I can probably code work arounds - Using Browserstack from Travis, tons of test fail for various reason. Many fail because I can't get the browser window to maximize from Travis, which works from my local environment. Likely this is due to a version difference between the two environments somewhere (selenium?). - For all other browsers, we exit on error if a Selenium test fails, but for now we don't for Safari. This way we still get notified if tests expected to pass fail, but I can keep Safari running in Travis while I work on figuring out solutions.