- Platform Configurator
- Getting Started with Selenium for Automated Website Testing
- Getting Started with Appium for Mobile Native Application Testing
- Selenium Bootcamp by Dave Haeffner
- Appium Bootcamp by Dave Haeffner and Matthew Edwards
Sauce Labs test logs are securely stored, protecting them from external access. However, there are still some groups that can see test logs, including Sauce Support, your parent account, and other accounts in your company (depending on test privacy settings).
Solution - Don't use real credentials
The best way to avoid this is to avoid using "real" credentials in tests, through the creation of temporary accounts.
Workaround - Transmit session tokens only
You can also avoid sensitive credentials using Selenium's ability to extract and inject cookies into accounts:
- Create a session in your environment, either directly in the application engine, or by using a local Selenium session or headless browser.
- Extract the session tokens (local storage objects, credentials, cookies, etc.).
- Use Selenium to push these objects and tokens into the browser under Sauce Labs' control
This technique avoids sending plain text passwords, however, the sent tokens and cookies are still logged. If your session tokens are not time-sensitive, this provides only security through obscurity. We recommend using time-sensitive session tokens.
Workaround - Change passwords after tests
If generating tokens and using unique temporary accounts is not possible, we recommend you have test actions your suite always takes, in order to change to a new, randomly generated password.
After each test, use a locally automated browser, a direct connection to your application database or a headless browser to change your test account's password to a new, randomly generated password. Ensure this password is stored in your CI environment, a credential store, or some other method.
In order to prevent credential loss from blocking test suites, you may want to start each test suite by changing the password, again, either by using a headless browser or local Selenium session to perform your password recovery process, or by directly interacting with your application's database.