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
Tests run with and without the --sauce flag do not run on Sauce, even with the SAUCE_USERNAME and SAUCE_ACCESS_KEY credentials set in .env.
Expected behavior
Tests run with the --sauce=true flag set should attempt to run tests through a local running Sauce Connect tunnel. (In the past the behavior was also make this the default, so no --sauce flag at all would be equivalent to its value being true.)
Steps to replicate behavior
Set SAUCE_USERNAME and SAUCE_ACCESS_KEY credentials in .env and uncomment SAUCE_SELENIUM_URL.
Run gulp test:acceptance --sauce=true and note that there are no errors around Sauce connect not running and the tests run locally as if gulp test:acceptance --sauce=false were set.
The text was updated successfully, but these errors were encountered:
At some point the Sauce Connect
--sauce
flag broke and doesn't work anymore. Fixing this issue should really address #885 as well.Also, #887 and #886 are Sauce issues.
Current behavior
--sauce
flag do not run on Sauce, even with theSAUCE_USERNAME
andSAUCE_ACCESS_KEY
credentials set in.env
.Expected behavior
--sauce=true
flag set should attempt to run tests through a local running Sauce Connect tunnel. (In the past the behavior was also make this the default, so no--sauce
flag at all would be equivalent to its value being true.)Steps to replicate behavior
SAUCE_USERNAME
andSAUCE_ACCESS_KEY
credentials in.env
and uncommentSAUCE_SELENIUM_URL
.gulp test:acceptance --sauce=true
and note that there are no errors around Sauce connect not running and the tests run locally as ifgulp test:acceptance --sauce=false
were set.The text was updated successfully, but these errors were encountered: