This repository has been archived by the owner on Feb 13, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 115
Troubleshooting
Dylan Lacey edited this page Feb 25, 2014
·
5 revisions
We think this is a corrupt gem tarball; Try removing the tarball and fetching it again. Check out https://github.com/saucelabs/sauce_ruby/issues/171 for more discussion or if this doesn't help
- Ensure your specs are tagged :sauce => true
- Ensure you're requiring the gem in your spec_helper
- Check if the latest version of the gem solves your problem
- Make sure you've tagged your example groups
:sauce => true
- Make sure you've only configured
[:browsers]
, not[:browser]
, in Sauce.config
- Ensure your features are tagged @selenium
- Check if the latest version of the gem solves your problem
Jobs on Sauce Labs can't see the system under test, Or "Test did not receive new commands for 90 seconds"
If Capybara is trying to start multiple servers on the same port, only the first server will start and the rest will freak out and abort.
The gem automatically sets the Capybara port, based on the Sauce Connect usable ports and the TEST_ENV_NUMBER environment variable (Set by parallel tests).
If you have over-ridden this behaviour, or hard-set the Capybara app_host, you will need to take port collisions into account.