Github user michellephung commented on the pull request:
https://github.com/apache/couchdb-fauxton/pull/168#issuecomment-65713505
ahh! i just rebased....
Some context:
Our travis tests are connecting with SauceLabs using SauceConnect (which is
an improvement),
however when the tests go to login to Fauxton, the username and password
being passed is
> username : Fauxton
password : testerpass
instead of
> username : tester
password: testerpass
so our saucelabs tests are not making it past the login screen. [View
test](https://saucelabs.com/tests/f2d3d6ce14b849e9b27814d2915f88fc)
On the left-hand side of the saucelabs test, you can scroll to view what
the browser is doing at each second. At 9 seconds and 10 seconds, we see that
value being passed are 'Fauxton' and 'testerpass'.
In
[nightwatch.json.underscore](https://github.com/apache/couchdb-fauxton/blob/master/test/nightwatch_tests/nightwatch.json.underscore#L25),
the default `username`/`password` variables are being correct assigned
'tester' and 'testerpass', but then soon gets overwritten by our 'saucelabs'
object, which has a key named `username`, as well.
The tests use the most recent assignment of `username`, which is what is
being passed in our `${SAUCE_USERNAME}`.
In this fix (19e753d) I've done two things:
1. added `curl -X PUT $HOST/_config/admins/Fauxton -d '"testerpass"'`, in
the .travis.yml file, which creates an admin with username `Fauxton`, and
password `testerpass`
2. I added more wait time to the loginToGUI.js file, since the browser in
saucelabs takes longer to find the login link initially.
> username : tester
password: testerpass
so our saucelabs tests are not making it past the login screen.
On the left-hand side of the saucelabs test, you can scroll to view what
the browser is doing at each second. At 9 seconds and 10 seconds, we see that
value being passed are 'Fauxton' and 'testerpass'.
In
https://github.com/apache/couchdb-fauxton/blob/master/test/nightwatch_tests/nightwatch.json.underscore#L25
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
