Hiding Sensitive Data

When you are running tests on the TestingBot cloud, we automatically gather logs and screenshots/videos of each of your tests.
This feature allows testers to debug potential issues with their tests, or verify if their tests are doing what they are supposed to be doing.

However, it might be important for you to prevent this logging from happening.

For example, you're testing a login/signup page and you are sending a password or secret token.

We offer several options to partially or completely disable logging during your tests:

Strip Parameters

You can choose to remove all parameters from the TestingBot logs, which are sent during your test.

Parameters like passwords, tokens or other sensitive data will no longer appear in our logs.

caps["recordLogs"] = "strip-parameters"
caps.setCapability("recordLogs", "strip-parameters");
$caps["recordLogs"] = "strip-parameters";
caps["recordLogs"] = "strip-parameters"
capabilities['recordLogs'] = 'strip-parameters'
caps.SetCapability("recordLogs", "strip-parameters");

Disable Logging

By default, TestingBot collects several logs during your test. Depending on the browser/platform you're testing on, the log files may include:

  • vm: our logs where we display what the VM is doing, including the Selenium commands it's relaying.
  • selenium: the log file generated by Selenium, which includes parameters and commands your test is sending.
  • firefox: the geckodriver (verbose) log for the test, if the test is running against a Firefox browser.
  • sikuli: if you are using Sikuli, the output of Sikuli will appear here.
  • appium: mobile tests (live and automated) are using Appium. Commands and parameters will be logged here.
  • logcat: if you are running a mobile app test on Android, we will retrieve the Android Logcat file.
  • android: this contains the output of the Android emulator.
  • browser: the console logs of the browser.
  • cypress: output generated by Cypress, if you are using Cypress Testing.

To disable all logs, you can use this capability:

caps["recordLogs"] = false
caps.setCapability("recordLogs", false);
$caps["recordLogs"] = false;
caps["recordLogs"] = False
capabilities['recordLogs'] = false
caps.SetCapability("recordLogs", false);

You can also choose to disable some logs:

caps["disableLogs"] = ['appium', 'browser']
caps.setCapability("recordLogs", {"appium", "browser"});
$caps["recordLogs"] = array('appium', 'browser');
caps["recordLogs"] = ['appium', 'browser']
capabilities['recordLogs'] = ['appium', 'browser']
caps.SetCapability("recordLogs", {"appium", "browser"});

Disable video recordings

By default, we'll record the screen during your test. This makes it easy to troubleshoot or verify the test.

You can choose to disable the video recording with this capability:

caps = Selenium::WebDriver::Remote::Capabilities.new
caps["screenrecorder"] = false
DesiredCapabilities caps = new DesiredCapabilities();
caps.setCapability("screenrecorder", false);
$caps = array(
  "screenrecorder" => false
capabilities = {
  "screenrecorder" : False
const capabilities = {
  "screenrecorder" : false
DesiredCapabilities caps = new DesiredCapabilities();
caps.SetCapability("screenrecorder", false);