diff --git a/.travis.yml b/.travis.yml index eb944a515..8c77bccb4 100644 --- a/.travis.yml +++ b/.travis.yml @@ -9,6 +9,10 @@ branches: only: - master - browserstack +script: + # - bundle exec rake + - CONFIG_NAME=windows/windows_chrome_latest.config.yaml bundle exec rspec --tag run_on_browserstack + - CONFIG_NAME=osx/osx_safari_latest.config.yaml bundle exec rspec --tag run_on_browserstack addons: apt: packages: diff --git a/Gemfile b/Gemfile index 4e4b8367a..44419a387 100644 --- a/Gemfile +++ b/Gemfile @@ -89,3 +89,5 @@ source 'https://rubygems.org' + +gem "browserstack-local", "~> 1.3" diff --git a/Rakefile b/Rakefile index 5b142b335..a376b9b57 100644 --- a/Rakefile +++ b/Rakefile @@ -18,10 +18,7 @@ end ## RSPEC require 'rspec/core/rake_task' -RSpec::Core::RakeTask.new(:spec) - - - +RSpec::Core::RakeTask.new(:spec) ################################ # SSL/TLS certificate diff --git a/local.log b/local.log new file mode 100644 index 000000000..ef3c137ab --- /dev/null +++ b/local.log @@ -0,0 +1,1976 @@ + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + + *** Error: Either another browserstack local client is running on your machine or some server is listening on port 45691 + +To test an internal server, run: +./BrowserStackLocal --key +Example: +./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 + +To test HTML files, run: +./BrowserStackLocal --key --folder +Example: +./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 --folder /Applications/MAMP/htdocs/example/ + + +The following options are available: + -k, --key Browserstack Access Key. This information is available in the local testing section of the Settings page: https://www.browserstack.com/accounts/settings + -f, --folder Specify the Local folder to be used for testing. This option is to be used when testing a local folder. Example: /home/ubuntu/mysite/ or C:\windows\mysite\ + -h, --help Display the help text. + -V, --version Display the current version of the binary. + -F, --force Using this option kills all other instances of BrowserStack Local binary running on this machine with the same --local-identifier options. This option will not affect binaries running in remote servers and instances running with different --local-identifier options. + --only If you want to restrict BrowserStackLocal Binary access to few local servers and/or folders, use this option to restrict them. Usage: host1,port1,ssl?,host2,port2,ssl?. Example: localhost,8000,0,abc.example.com,8080,1 + --force-local Route all traffic via machine where BrowserStackLocal Binary is running. Local tries to fetch public urls directly, unless this option is specified. + --verbose This option sets the level of logging required. Set 1 to debug issues related to setting up connections. Set 2 for logs related to network information. Set 3 to dump all communication to local servers for each request and response. The default value for this option is 1. + --only-automate This option restricts Binary usage to Automate product, and it cannot be used for Live/Screenshot testing. + --proxy-host If you are behind corporate proxy setup, please specify your proxy host using this option. + --proxy-port If you are behind corporate proxy setup, please specify your proxy port using this option. Default value is 3128. + --proxy-user If you are behind corporate proxy which requires authentication, please specify your proxy username using this option. As of now, only HTTP Basic authentication is supported. + --proxy-pass If you are behind corporate proxy which requires authentication, please specify your proxy password using this option. As of now, only HTTP Basic authentication is supported. + --local-identifier If you are running multiple copies of BrowserStackLocal binary (for better performance or other reasons), please specify unique strings for BrowserStack to uniquely identify them. You will need to specify the same string in Automate tests as well. + --force-proxy This options routes all traffic via the proxy specified - otherwise, binary tries to connect directly as well for better performance. + --local-proxy-host If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy host using this option. + --local-proxy-port If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy port using this option. Default assumed is 8081. + --local-proxy-user If your local server is behind a proxy, and it requies authentication - please specify your proxy username using this option. + --local-proxy-pass If your local server is behind a proxy, and it requies authentication - please specify your proxy password using this option. + --daemon Starts or stop the binary as a daemon. Accepts only 2 commands: start, stop. Start will start binary in background. Primarily used in Continous Integration server scripts. + --enable-logging-for-api Include this option to make sure this binary is exposed to Local API for debugging. For more information refer to https://www.browserstack.com/local-testing#local-api-debugging + --log-file Logs all the output to the file specified. + --pac-file Path to pac file with which the proxy needs to be set. + --parallel-runs Specify the number of parallel runs. + --disable-proxy-discovery Disables the Auto-Proxy Discovery + --debug-utility Start BrowserStackLocal in debug mode. + --debug-url Internal/Staging URL BrowserStackLocal will try to connect when started in debug mode. + --https-ports If you want to test local HTTPS server which behind a proxy, in addition to port 443, please pass comma separated port values. Example: --https-ports 8443,9443 + +View more configuration options at https://www.browserstack.com/local-testing + + +BrowserStackLocal v7.6 + + *** Error: Either another browserstack local client is running on your machine or some server is listening on port 45691 + +To test an internal server, run: +./BrowserStackLocal --key +Example: +./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 + +To test HTML files, run: +./BrowserStackLocal --key --folder +Example: +./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 --folder /Applications/MAMP/htdocs/example/ + + +The following options are available: + -k, --key Browserstack Access Key. This information is available in the local testing section of the Settings page: https://www.browserstack.com/accounts/settings + -f, --folder Specify the Local folder to be used for testing. This option is to be used when testing a local folder. Example: /home/ubuntu/mysite/ or C:\windows\mysite\ + -h, --help Display the help text. + -V, --version Display the current version of the binary. + -F, --force Using this option kills all other instances of BrowserStack Local binary running on this machine with the same --local-identifier options. This option will not affect binaries running in remote servers and instances running with different --local-identifier options. + --only If you want to restrict BrowserStackLocal Binary access to few local servers and/or folders, use this option to restrict them. Usage: host1,port1,ssl?,host2,port2,ssl?. Example: localhost,8000,0,abc.example.com,8080,1 + --force-local Route all traffic via machine where BrowserStackLocal Binary is running. Local tries to fetch public urls directly, unless this option is specified. + --verbose This option sets the level of logging required. Set 1 to debug issues related to setting up connections. Set 2 for logs related to network information. Set 3 to dump all communication to local servers for each request and response. The default value for this option is 1. + --only-automate This option restricts Binary usage to Automate product, and it cannot be used for Live/Screenshot testing. + --proxy-host If you are behind corporate proxy setup, please specify your proxy host using this option. + --proxy-port If you are behind corporate proxy setup, please specify your proxy port using this option. Default value is 3128. + --proxy-user If you are behind corporate proxy which requires authentication, please specify your proxy username using this option. As of now, only HTTP Basic authentication is supported. + --proxy-pass If you are behind corporate proxy which requires authentication, please specify your proxy password using this option. As of now, only HTTP Basic authentication is supported. + --local-identifier If you are running multiple copies of BrowserStackLocal binary (for better performance or other reasons), please specify unique strings for BrowserStack to uniquely identify them. You will need to specify the same string in Automate tests as well. + --force-proxy This options routes all traffic via the proxy specified - otherwise, binary tries to connect directly as well for better performance. + --local-proxy-host If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy host using this option. + --local-proxy-port If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy port using this option. Default assumed is 8081. + --local-proxy-user If your local server is behind a proxy, and it requies authentication - please specify your proxy username using this option. + --local-proxy-pass If your local server is behind a proxy, and it requies authentication - please specify your proxy password using this option. + --daemon Starts or stop the binary as a daemon. Accepts only 2 commands: start, stop. Start will start binary in background. Primarily used in Continous Integration server scripts. + --enable-logging-for-api Include this option to make sure this binary is exposed to Local API for debugging. For more information refer to https://www.browserstack.com/local-testing#local-api-debugging + --log-file Logs all the output to the file specified. + --pac-file Path to pac file with which the proxy needs to be set. + --parallel-runs Specify the number of parallel runs. + --disable-proxy-discovery Disables the Auto-Proxy Discovery + --debug-utility Start BrowserStackLocal in debug mode. + --debug-url Internal/Staging URL BrowserStackLocal will try to connect when started in debug mode. + --https-ports If you want to test local HTTPS server which behind a proxy, in addition to port 443, please pass comma separated port values. Example: --https-ports 8443,9443 + +View more configuration options at https://www.browserstack.com/local-testing + + +BrowserStackLocal v7.6 + + *** Error: Either another browserstack local client is running on your machine or some server is listening on port 45691 + +To test an internal server, run: +./BrowserStackLocal --key +Example: +./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 + +To test HTML files, run: +./BrowserStackLocal --key --folder +Example: +./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 --folder /Applications/MAMP/htdocs/example/ + + +The following options are available: + -k, --key Browserstack Access Key. This information is available in the local testing section of the Settings page: https://www.browserstack.com/accounts/settings + -f, --folder Specify the Local folder to be used for testing. This option is to be used when testing a local folder. Example: /home/ubuntu/mysite/ or C:\windows\mysite\ + -h, --help Display the help text. + -V, --version Display the current version of the binary. + -F, --force Using this option kills all other instances of BrowserStack Local binary running on this machine with the same --local-identifier options. This option will not affect binaries running in remote servers and instances running with different --local-identifier options. + --only If you want to restrict BrowserStackLocal Binary access to few local servers and/or folders, use this option to restrict them. Usage: host1,port1,ssl?,host2,port2,ssl?. Example: localhost,8000,0,abc.example.com,8080,1 + --force-local Route all traffic via machine where BrowserStackLocal Binary is running. Local tries to fetch public urls directly, unless this option is specified. + --verbose This option sets the level of logging required. Set 1 to debug issues related to setting up connections. Set 2 for logs related to network information. Set 3 to dump all communication to local servers for each request and response. The default value for this option is 1. + --only-automate This option restricts Binary usage to Automate product, and it cannot be used for Live/Screenshot testing. + --proxy-host If you are behind corporate proxy setup, please specify your proxy host using this option. + --proxy-port If you are behind corporate proxy setup, please specify your proxy port using this option. Default value is 3128. + --proxy-user If you are behind corporate proxy which requires authentication, please specify your proxy username using this option. As of now, only HTTP Basic authentication is supported. + --proxy-pass If you are behind corporate proxy which requires authentication, please specify your proxy password using this option. As of now, only HTTP Basic authentication is supported. + --local-identifier If you are running multiple copies of BrowserStackLocal binary (for better performance or other reasons), please specify unique strings for BrowserStack to uniquely identify them. You will need to specify the same string in Automate tests as well. + --force-proxy This options routes all traffic via the proxy specified - otherwise, binary tries to connect directly as well for better performance. + --local-proxy-host If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy host using this option. + --local-proxy-port If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy port using this option. Default assumed is 8081. + --local-proxy-user If your local server is behind a proxy, and it requies authentication - please specify your proxy username using this option. + --local-proxy-pass If your local server is behind a proxy, and it requies authentication - please specify your proxy password using this option. + --daemon Starts or stop the binary as a daemon. Accepts only 2 commands: start, stop. Start will start binary in background. Primarily used in Continous Integration server scripts. + --enable-logging-for-api Include this option to make sure this binary is exposed to Local API for debugging. For more information refer to https://www.browserstack.com/local-testing#local-api-debugging + --log-file Logs all the output to the file specified. + --pac-file Path to pac file with which the proxy needs to be set. + --parallel-runs Specify the number of parallel runs. + --disable-proxy-discovery Disables the Auto-Proxy Discovery + --debug-utility Start BrowserStackLocal in debug mode. + --debug-url Internal/Staging URL BrowserStackLocal will try to connect when started in debug mode. + --https-ports If you want to test local HTTPS server which behind a proxy, in addition to port 443, please pass comma separated port values. Example: --https-ports 8443,9443 + +View more configuration options at https://www.browserstack.com/local-testing + + +BrowserStackLocal v7.6 + + *** Error: Either another browserstack local client is running on your machine or some server is listening on port 45691 + +To test an internal server, run: +./BrowserStackLocal --key +Example: +./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 + +To test HTML files, run: +./BrowserStackLocal --key --folder +Example: +./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 --folder /Applications/MAMP/htdocs/example/ + + +The following options are available: + -k, --key Browserstack Access Key. This information is available in the local testing section of the Settings page: https://www.browserstack.com/accounts/settings + -f, --folder Specify the Local folder to be used for testing. This option is to be used when testing a local folder. Example: /home/ubuntu/mysite/ or C:\windows\mysite\ + -h, --help Display the help text. + -V, --version Display the current version of the binary. + -F, --force Using this option kills all other instances of BrowserStack Local binary running on this machine with the same --local-identifier options. This option will not affect binaries running in remote servers and instances running with different --local-identifier options. + --only If you want to restrict BrowserStackLocal Binary access to few local servers and/or folders, use this option to restrict them. Usage: host1,port1,ssl?,host2,port2,ssl?. Example: localhost,8000,0,abc.example.com,8080,1 + --force-local Route all traffic via machine where BrowserStackLocal Binary is running. Local tries to fetch public urls directly, unless this option is specified. + --verbose This option sets the level of logging required. Set 1 to debug issues related to setting up connections. Set 2 for logs related to network information. Set 3 to dump all communication to local servers for each request and response. The default value for this option is 1. + --only-automate This option restricts Binary usage to Automate product, and it cannot be used for Live/Screenshot testing. + --proxy-host If you are behind corporate proxy setup, please specify your proxy host using this option. + --proxy-port If you are behind corporate proxy setup, please specify your proxy port using this option. Default value is 3128. + --proxy-user If you are behind corporate proxy which requires authentication, please specify your proxy username using this option. As of now, only HTTP Basic authentication is supported. + --proxy-pass If you are behind corporate proxy which requires authentication, please specify your proxy password using this option. As of now, only HTTP Basic authentication is supported. + --local-identifier If you are running multiple copies of BrowserStackLocal binary (for better performance or other reasons), please specify unique strings for BrowserStack to uniquely identify them. You will need to specify the same string in Automate tests as well. + --force-proxy This options routes all traffic via the proxy specified - otherwise, binary tries to connect directly as well for better performance. + --local-proxy-host If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy host using this option. + --local-proxy-port If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy port using this option. Default assumed is 8081. + --local-proxy-user If your local server is behind a proxy, and it requies authentication - please specify your proxy username using this option. + --local-proxy-pass If your local server is behind a proxy, and it requies authentication - please specify your proxy password using this option. + --daemon Starts or stop the binary as a daemon. Accepts only 2 commands: start, stop. Start will start binary in background. Primarily used in Continous Integration server scripts. + --enable-logging-for-api Include this option to make sure this binary is exposed to Local API for debugging. For more information refer to https://www.browserstack.com/local-testing#local-api-debugging + --log-file Logs all the output to the file specified. + --pac-file Path to pac file with which the proxy needs to be set. + --parallel-runs Specify the number of parallel runs. + --disable-proxy-discovery Disables the Auto-Proxy Discovery + --debug-utility Start BrowserStackLocal in debug mode. + --debug-url Internal/Staging URL BrowserStackLocal will try to connect when started in debug mode. + --https-ports If you want to test local HTTPS server which behind a proxy, in addition to port 443, please pass comma separated port values. Example: --https-ports 8443,9443 + +View more configuration options at https://www.browserstack.com/local-testing + + +BrowserStackLocal v7.6 + + *** Error: Either another browserstack local client is running on your machine or some server is listening on port 45691 + +To test an internal server, run: +./BrowserStackLocal --key +Example: +./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 + +To test HTML files, run: +./BrowserStackLocal --key --folder +Example: +./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 --folder /Applications/MAMP/htdocs/example/ + + +The following options are available: + -k, --key Browserstack Access Key. This information is available in the local testing section of the Settings page: https://www.browserstack.com/accounts/settings + -f, --folder Specify the Local folder to be used for testing. This option is to be used when testing a local folder. Example: /home/ubuntu/mysite/ or C:\windows\mysite\ + -h, --help Display the help text. + -V, --version Display the current version of the binary. + -F, --force Using this option kills all other instances of BrowserStack Local binary running on this machine with the same --local-identifier options. This option will not affect binaries running in remote servers and instances running with different --local-identifier options. + --only If you want to restrict BrowserStackLocal Binary access to few local servers and/or folders, use this option to restrict them. Usage: host1,port1,ssl?,host2,port2,ssl?. Example: localhost,8000,0,abc.example.com,8080,1 + --force-local Route all traffic via machine where BrowserStackLocal Binary is running. Local tries to fetch public urls directly, unless this option is specified. + --verbose This option sets the level of logging required. Set 1 to debug issues related to setting up connections. Set 2 for logs related to network information. Set 3 to dump all communication to local servers for each request and response. The default value for this option is 1. + --only-automate This option restricts Binary usage to Automate product, and it cannot be used for Live/Screenshot testing. + --proxy-host If you are behind corporate proxy setup, please specify your proxy host using this option. + --proxy-port If you are behind corporate proxy setup, please specify your proxy port using this option. Default value is 3128. + --proxy-user If you are behind corporate proxy which requires authentication, please specify your proxy username using this option. As of now, only HTTP Basic authentication is supported. + --proxy-pass If you are behind corporate proxy which requires authentication, please specify your proxy password using this option. As of now, only HTTP Basic authentication is supported. + --local-identifier If you are running multiple copies of BrowserStackLocal binary (for better performance or other reasons), please specify unique strings for BrowserStack to uniquely identify them. You will need to specify the same string in Automate tests as well. + --force-proxy This options routes all traffic via the proxy specified - otherwise, binary tries to connect directly as well for better performance. + --local-proxy-host If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy host using this option. + --local-proxy-port If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy port using this option. Default assumed is 8081. + --local-proxy-user If your local server is behind a proxy, and it requies authentication - please specify your proxy username using this option. + --local-proxy-pass If your local server is behind a proxy, and it requies authentication - please specify your proxy password using this option. + --daemon Starts or stop the binary as a daemon. Accepts only 2 commands: start, stop. Start will start binary in background. Primarily used in Continous Integration server scripts. + --enable-logging-for-api Include this option to make sure this binary is exposed to Local API for debugging. For more information refer to https://www.browserstack.com/local-testing#local-api-debugging + --log-file Logs all the output to the file specified. + --pac-file Path to pac file with which the proxy needs to be set. + --parallel-runs Specify the number of parallel runs. + --disable-proxy-discovery Disables the Auto-Proxy Discovery + --debug-utility Start BrowserStackLocal in debug mode. + --debug-url Internal/Staging URL BrowserStackLocal will try to connect when started in debug mode. + --https-ports If you want to test local HTTPS server which behind a proxy, in addition to port 443, please pass comma separated port values. Example: --https-ports 8443,9443 + +View more configuration options at https://www.browserstack.com/local-testing + + +BrowserStackLocal v7.6 + + *** Error: Either another browserstack local client is running on your machine or some server is listening on port 45691 + +To test an internal server, run: +./BrowserStackLocal --key +Example: +./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 + +To test HTML files, run: +./BrowserStackLocal --key --folder +Example: +./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 --folder /Applications/MAMP/htdocs/example/ + + +The following options are available: + -k, --key Browserstack Access Key. This information is available in the local testing section of the Settings page: https://www.browserstack.com/accounts/settings + -f, --folder Specify the Local folder to be used for testing. This option is to be used when testing a local folder. Example: /home/ubuntu/mysite/ or C:\windows\mysite\ + -h, --help Display the help text. + -V, --version Display the current version of the binary. + -F, --force Using this option kills all other instances of BrowserStack Local binary running on this machine with the same --local-identifier options. This option will not affect binaries running in remote servers and instances running with different --local-identifier options. + --only If you want to restrict BrowserStackLocal Binary access to few local servers and/or folders, use this option to restrict them. Usage: host1,port1,ssl?,host2,port2,ssl?. Example: localhost,8000,0,abc.example.com,8080,1 + --force-local Route all traffic via machine where BrowserStackLocal Binary is running. Local tries to fetch public urls directly, unless this option is specified. + --verbose This option sets the level of logging required. Set 1 to debug issues related to setting up connections. Set 2 for logs related to network information. Set 3 to dump all communication to local servers for each request and response. The default value for this option is 1. + --only-automate This option restricts Binary usage to Automate product, and it cannot be used for Live/Screenshot testing. + --proxy-host If you are behind corporate proxy setup, please specify your proxy host using this option. + --proxy-port If you are behind corporate proxy setup, please specify your proxy port using this option. Default value is 3128. + --proxy-user If you are behind corporate proxy which requires authentication, please specify your proxy username using this option. As of now, only HTTP Basic authentication is supported. + --proxy-pass If you are behind corporate proxy which requires authentication, please specify your proxy password using this option. As of now, only HTTP Basic authentication is supported. + --local-identifier If you are running multiple copies of BrowserStackLocal binary (for better performance or other reasons), please specify unique strings for BrowserStack to uniquely identify them. You will need to specify the same string in Automate tests as well. + --force-proxy This options routes all traffic via the proxy specified - otherwise, binary tries to connect directly as well for better performance. + --local-proxy-host If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy host using this option. + --local-proxy-port If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy port using this option. Default assumed is 8081. + --local-proxy-user If your local server is behind a proxy, and it requies authentication - please specify your proxy username using this option. + --local-proxy-pass If your local server is behind a proxy, and it requies authentication - please specify your proxy password using this option. + --daemon Starts or stop the binary as a daemon. Accepts only 2 commands: start, stop. Start will start binary in background. Primarily used in Continous Integration server scripts. + --enable-logging-for-api Include this option to make sure this binary is exposed to Local API for debugging. For more information refer to https://www.browserstack.com/local-testing#local-api-debugging + --log-file Logs all the output to the file specified. + --pac-file Path to pac file with which the proxy needs to be set. + --parallel-runs Specify the number of parallel runs. + --disable-proxy-discovery Disables the Auto-Proxy Discovery + --debug-utility Start BrowserStackLocal in debug mode. + --debug-url Internal/Staging URL BrowserStackLocal will try to connect when started in debug mode. + --https-ports If you want to test local HTTPS server which behind a proxy, in addition to port 443, please pass comma separated port values. Example: --https-ports 8443,9443 + +View more configuration options at https://www.browserstack.com/local-testing + + +BrowserStackLocal v7.6 + + *** Error: Either another browserstack local client is running on your machine or some server is listening on port 45691 + +To test an internal server, run: +./BrowserStackLocal --key +Example: +./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 + +To test HTML files, run: +./BrowserStackLocal --key --folder +Example: +./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 --folder /Applications/MAMP/htdocs/example/ + + +The following options are available: + -k, --key Browserstack Access Key. This information is available in the local testing section of the Settings page: https://www.browserstack.com/accounts/settings + -f, --folder Specify the Local folder to be used for testing. This option is to be used when testing a local folder. Example: /home/ubuntu/mysite/ or C:\windows\mysite\ + -h, --help Display the help text. + -V, --version Display the current version of the binary. + -F, --force Using this option kills all other instances of BrowserStack Local binary running on this machine with the same --local-identifier options. This option will not affect binaries running in remote servers and instances running with different --local-identifier options. + --only If you want to restrict BrowserStackLocal Binary access to few local servers and/or folders, use this option to restrict them. Usage: host1,port1,ssl?,host2,port2,ssl?. Example: localhost,8000,0,abc.example.com,8080,1 + --force-local Route all traffic via machine where BrowserStackLocal Binary is running. Local tries to fetch public urls directly, unless this option is specified. + --verbose This option sets the level of logging required. Set 1 to debug issues related to setting up connections. Set 2 for logs related to network information. Set 3 to dump all communication to local servers for each request and response. The default value for this option is 1. + --only-automate This option restricts Binary usage to Automate product, and it cannot be used for Live/Screenshot testing. + --proxy-host If you are behind corporate proxy setup, please specify your proxy host using this option. + --proxy-port If you are behind corporate proxy setup, please specify your proxy port using this option. Default value is 3128. + --proxy-user If you are behind corporate proxy which requires authentication, please specify your proxy username using this option. As of now, only HTTP Basic authentication is supported. + --proxy-pass If you are behind corporate proxy which requires authentication, please specify your proxy password using this option. As of now, only HTTP Basic authentication is supported. + --local-identifier If you are running multiple copies of BrowserStackLocal binary (for better performance or other reasons), please specify unique strings for BrowserStack to uniquely identify them. You will need to specify the same string in Automate tests as well. + --force-proxy This options routes all traffic via the proxy specified - otherwise, binary tries to connect directly as well for better performance. + --local-proxy-host If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy host using this option. + --local-proxy-port If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy port using this option. Default assumed is 8081. + --local-proxy-user If your local server is behind a proxy, and it requies authentication - please specify your proxy username using this option. + --local-proxy-pass If your local server is behind a proxy, and it requies authentication - please specify your proxy password using this option. + --daemon Starts or stop the binary as a daemon. Accepts only 2 commands: start, stop. Start will start binary in background. Primarily used in Continous Integration server scripts. + --enable-logging-for-api Include this option to make sure this binary is exposed to Local API for debugging. For more information refer to https://www.browserstack.com/local-testing#local-api-debugging + --log-file Logs all the output to the file specified. + --pac-file Path to pac file with which the proxy needs to be set. + --parallel-runs Specify the number of parallel runs. + --disable-proxy-discovery Disables the Auto-Proxy Discovery + --debug-utility Start BrowserStackLocal in debug mode. + --debug-url Internal/Staging URL BrowserStackLocal will try to connect when started in debug mode. + --https-ports If you want to test local HTTPS server which behind a proxy, in addition to port 443, please pass comma separated port values. Example: --https-ports 8443,9443 + +View more configuration options at https://www.browserstack.com/local-testing + + +BrowserStackLocal v7.6 + + *** Error: Either another browserstack local client is running on your machine or some server is listening on port 45691 + +To test an internal server, run: +./BrowserStackLocal --key +Example: +./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 + +To test HTML files, run: +./BrowserStackLocal --key --folder +Example: +./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 --folder /Applications/MAMP/htdocs/example/ + + +The following options are available: + -k, --key Browserstack Access Key. This information is available in the local testing section of the Settings page: https://www.browserstack.com/accounts/settings + -f, --folder Specify the Local folder to be used for testing. This option is to be used when testing a local folder. Example: /home/ubuntu/mysite/ or C:\windows\mysite\ + -h, --help Display the help text. + -V, --version Display the current version of the binary. + -F, --force Using this option kills all other instances of BrowserStack Local binary running on this machine with the same --local-identifier options. This option will not affect binaries running in remote servers and instances running with different --local-identifier options. + --only If you want to restrict BrowserStackLocal Binary access to few local servers and/or folders, use this option to restrict them. Usage: host1,port1,ssl?,host2,port2,ssl?. Example: localhost,8000,0,abc.example.com,8080,1 + --force-local Route all traffic via machine where BrowserStackLocal Binary is running. Local tries to fetch public urls directly, unless this option is specified. + --verbose This option sets the level of logging required. Set 1 to debug issues related to setting up connections. Set 2 for logs related to network information. Set 3 to dump all communication to local servers for each request and response. The default value for this option is 1. + --only-automate This option restricts Binary usage to Automate product, and it cannot be used for Live/Screenshot testing. + --proxy-host If you are behind corporate proxy setup, please specify your proxy host using this option. + --proxy-port If you are behind corporate proxy setup, please specify your proxy port using this option. Default value is 3128. + --proxy-user If you are behind corporate proxy which requires authentication, please specify your proxy username using this option. As of now, only HTTP Basic authentication is supported. + --proxy-pass If you are behind corporate proxy which requires authentication, please specify your proxy password using this option. As of now, only HTTP Basic authentication is supported. + --local-identifier If you are running multiple copies of BrowserStackLocal binary (for better performance or other reasons), please specify unique strings for BrowserStack to uniquely identify them. You will need to specify the same string in Automate tests as well. + --force-proxy This options routes all traffic via the proxy specified - otherwise, binary tries to connect directly as well for better performance. + --local-proxy-host If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy host using this option. + --local-proxy-port If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy port using this option. Default assumed is 8081. + --local-proxy-user If your local server is behind a proxy, and it requies authentication - please specify your proxy username using this option. + --local-proxy-pass If your local server is behind a proxy, and it requies authentication - please specify your proxy password using this option. + --daemon Starts or stop the binary as a daemon. Accepts only 2 commands: start, stop. Start will start binary in background. Primarily used in Continous Integration server scripts. + --enable-logging-for-api Include this option to make sure this binary is exposed to Local API for debugging. For more information refer to https://www.browserstack.com/local-testing#local-api-debugging + --log-file Logs all the output to the file specified. + --pac-file Path to pac file with which the proxy needs to be set. + --parallel-runs Specify the number of parallel runs. + --disable-proxy-discovery Disables the Auto-Proxy Discovery + --debug-utility Start BrowserStackLocal in debug mode. + --debug-url Internal/Staging URL BrowserStackLocal will try to connect when started in debug mode. + --https-ports If you want to test local HTTPS server which behind a proxy, in addition to port 443, please pass comma separated port values. Example: --https-ports 8443,9443 + +View more configuration options at https://www.browserstack.com/local-testing + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + + *** Error: Either another browserstack local client is running on your machine or some server is listening on port 45691 + +To test an internal server, run: +./BrowserStackLocal --key +Example: +./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 + +To test HTML files, run: +./BrowserStackLocal --key --folder +Example: +./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 --folder /Applications/MAMP/htdocs/example/ + + +The following options are available: + -k, --key Browserstack Access Key. This information is available in the local testing section of the Settings page: https://www.browserstack.com/accounts/settings + -f, --folder Specify the Local folder to be used for testing. This option is to be used when testing a local folder. Example: /home/ubuntu/mysite/ or C:\windows\mysite\ + -h, --help Display the help text. + -V, --version Display the current version of the binary. + -F, --force Using this option kills all other instances of BrowserStack Local binary running on this machine with the same --local-identifier options. This option will not affect binaries running in remote servers and instances running with different --local-identifier options. + --only If you want to restrict BrowserStackLocal Binary access to few local servers and/or folders, use this option to restrict them. Usage: host1,port1,ssl?,host2,port2,ssl?. Example: localhost,8000,0,abc.example.com,8080,1 + --force-local Route all traffic via machine where BrowserStackLocal Binary is running. Local tries to fetch public urls directly, unless this option is specified. + --verbose This option sets the level of logging required. Set 1 to debug issues related to setting up connections. Set 2 for logs related to network information. Set 3 to dump all communication to local servers for each request and response. The default value for this option is 1. + --only-automate This option restricts Binary usage to Automate product, and it cannot be used for Live/Screenshot testing. + --proxy-host If you are behind corporate proxy setup, please specify your proxy host using this option. + --proxy-port If you are behind corporate proxy setup, please specify your proxy port using this option. Default value is 3128. + --proxy-user If you are behind corporate proxy which requires authentication, please specify your proxy username using this option. As of now, only HTTP Basic authentication is supported. + --proxy-pass If you are behind corporate proxy which requires authentication, please specify your proxy password using this option. As of now, only HTTP Basic authentication is supported. + --local-identifier If you are running multiple copies of BrowserStackLocal binary (for better performance or other reasons), please specify unique strings for BrowserStack to uniquely identify them. You will need to specify the same string in Automate tests as well. + --force-proxy This options routes all traffic via the proxy specified - otherwise, binary tries to connect directly as well for better performance. + --local-proxy-host If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy host using this option. + --local-proxy-port If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy port using this option. Default assumed is 8081. + --local-proxy-user If your local server is behind a proxy, and it requies authentication - please specify your proxy username using this option. + --local-proxy-pass If your local server is behind a proxy, and it requies authentication - please specify your proxy password using this option. + --daemon Starts or stop the binary as a daemon. Accepts only 2 commands: start, stop. Start will start binary in background. Primarily used in Continous Integration server scripts. + --enable-logging-for-api Include this option to make sure this binary is exposed to Local API for debugging. For more information refer to https://www.browserstack.com/local-testing#local-api-debugging + --log-file Logs all the output to the file specified. + --pac-file Path to pac file with which the proxy needs to be set. + --parallel-runs Specify the number of parallel runs. + --disable-proxy-discovery Disables the Auto-Proxy Discovery + --debug-utility Start BrowserStackLocal in debug mode. + --debug-url Internal/Staging URL BrowserStackLocal will try to connect when started in debug mode. + --https-ports If you want to test local HTTPS server which behind a proxy, in addition to port 443, please pass comma separated port values. Example: --https-ports 8443,9443 + +View more configuration options at https://www.browserstack.com/local-testing + + +BrowserStackLocal v7.6 + + *** Error: Either another browserstack local client is running on your machine or some server is listening on port 45691 + +To test an internal server, run: +./BrowserStackLocal --key +Example: +./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 + +To test HTML files, run: +./BrowserStackLocal --key --folder +Example: +./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 --folder /Applications/MAMP/htdocs/example/ + + +The following options are available: + -k, --key Browserstack Access Key. This information is available in the local testing section of the Settings page: https://www.browserstack.com/accounts/settings + -f, --folder Specify the Local folder to be used for testing. This option is to be used when testing a local folder. Example: /home/ubuntu/mysite/ or C:\windows\mysite\ + -h, --help Display the help text. + -V, --version Display the current version of the binary. + -F, --force Using this option kills all other instances of BrowserStack Local binary running on this machine with the same --local-identifier options. This option will not affect binaries running in remote servers and instances running with different --local-identifier options. + --only If you want to restrict BrowserStackLocal Binary access to few local servers and/or folders, use this option to restrict them. Usage: host1,port1,ssl?,host2,port2,ssl?. Example: localhost,8000,0,abc.example.com,8080,1 + --force-local Route all traffic via machine where BrowserStackLocal Binary is running. Local tries to fetch public urls directly, unless this option is specified. + --verbose This option sets the level of logging required. Set 1 to debug issues related to setting up connections. Set 2 for logs related to network information. Set 3 to dump all communication to local servers for each request and response. The default value for this option is 1. + --only-automate This option restricts Binary usage to Automate product, and it cannot be used for Live/Screenshot testing. + --proxy-host If you are behind corporate proxy setup, please specify your proxy host using this option. + --proxy-port If you are behind corporate proxy setup, please specify your proxy port using this option. Default value is 3128. + --proxy-user If you are behind corporate proxy which requires authentication, please specify your proxy username using this option. As of now, only HTTP Basic authentication is supported. + --proxy-pass If you are behind corporate proxy which requires authentication, please specify your proxy password using this option. As of now, only HTTP Basic authentication is supported. + --local-identifier If you are running multiple copies of BrowserStackLocal binary (for better performance or other reasons), please specify unique strings for BrowserStack to uniquely identify them. You will need to specify the same string in Automate tests as well. + --force-proxy This options routes all traffic via the proxy specified - otherwise, binary tries to connect directly as well for better performance. + --local-proxy-host If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy host using this option. + --local-proxy-port If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy port using this option. Default assumed is 8081. + --local-proxy-user If your local server is behind a proxy, and it requies authentication - please specify your proxy username using this option. + --local-proxy-pass If your local server is behind a proxy, and it requies authentication - please specify your proxy password using this option. + --daemon Starts or stop the binary as a daemon. Accepts only 2 commands: start, stop. Start will start binary in background. Primarily used in Continous Integration server scripts. + --enable-logging-for-api Include this option to make sure this binary is exposed to Local API for debugging. For more information refer to https://www.browserstack.com/local-testing#local-api-debugging + --log-file Logs all the output to the file specified. + --pac-file Path to pac file with which the proxy needs to be set. + --parallel-runs Specify the number of parallel runs. + --disable-proxy-discovery Disables the Auto-Proxy Discovery + --debug-utility Start BrowserStackLocal in debug mode. + --debug-url Internal/Staging URL BrowserStackLocal will try to connect when started in debug mode. + --https-ports If you want to test local HTTPS server which behind a proxy, in addition to port 443, please pass comma separated port values. Example: --https-ports 8443,9443 + +View more configuration options at https://www.browserstack.com/local-testing + + +BrowserStackLocal v7.6 + + *** Error: Either another browserstack local client is running on your machine or some server is listening on port 45691 + +To test an internal server, run: +./BrowserStackLocal --key +Example: +./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 + +To test HTML files, run: +./BrowserStackLocal --key --folder +Example: +./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 --folder /Applications/MAMP/htdocs/example/ + + +The following options are available: + -k, --key Browserstack Access Key. This information is available in the local testing section of the Settings page: https://www.browserstack.com/accounts/settings + -f, --folder Specify the Local folder to be used for testing. This option is to be used when testing a local folder. Example: /home/ubuntu/mysite/ or C:\windows\mysite\ + -h, --help Display the help text. + -V, --version Display the current version of the binary. + -F, --force Using this option kills all other instances of BrowserStack Local binary running on this machine with the same --local-identifier options. This option will not affect binaries running in remote servers and instances running with different --local-identifier options. + --only If you want to restrict BrowserStackLocal Binary access to few local servers and/or folders, use this option to restrict them. Usage: host1,port1,ssl?,host2,port2,ssl?. Example: localhost,8000,0,abc.example.com,8080,1 + --force-local Route all traffic via machine where BrowserStackLocal Binary is running. Local tries to fetch public urls directly, unless this option is specified. + --verbose This option sets the level of logging required. Set 1 to debug issues related to setting up connections. Set 2 for logs related to network information. Set 3 to dump all communication to local servers for each request and response. The default value for this option is 1. + --only-automate This option restricts Binary usage to Automate product, and it cannot be used for Live/Screenshot testing. + --proxy-host If you are behind corporate proxy setup, please specify your proxy host using this option. + --proxy-port If you are behind corporate proxy setup, please specify your proxy port using this option. Default value is 3128. + --proxy-user If you are behind corporate proxy which requires authentication, please specify your proxy username using this option. As of now, only HTTP Basic authentication is supported. + --proxy-pass If you are behind corporate proxy which requires authentication, please specify your proxy password using this option. As of now, only HTTP Basic authentication is supported. + --local-identifier If you are running multiple copies of BrowserStackLocal binary (for better performance or other reasons), please specify unique strings for BrowserStack to uniquely identify them. You will need to specify the same string in Automate tests as well. + --force-proxy This options routes all traffic via the proxy specified - otherwise, binary tries to connect directly as well for better performance. + --local-proxy-host If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy host using this option. + --local-proxy-port If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy port using this option. Default assumed is 8081. + --local-proxy-user If your local server is behind a proxy, and it requies authentication - please specify your proxy username using this option. + --local-proxy-pass If your local server is behind a proxy, and it requies authentication - please specify your proxy password using this option. + --daemon Starts or stop the binary as a daemon. Accepts only 2 commands: start, stop. Start will start binary in background. Primarily used in Continous Integration server scripts. + --enable-logging-for-api Include this option to make sure this binary is exposed to Local API for debugging. For more information refer to https://www.browserstack.com/local-testing#local-api-debugging + --log-file Logs all the output to the file specified. + --pac-file Path to pac file with which the proxy needs to be set. + --parallel-runs Specify the number of parallel runs. + --disable-proxy-discovery Disables the Auto-Proxy Discovery + --debug-utility Start BrowserStackLocal in debug mode. + --debug-url Internal/Staging URL BrowserStackLocal will try to connect when started in debug mode. + --https-ports If you want to test local HTTPS server which behind a proxy, in addition to port 443, please pass comma separated port values. Example: --https-ports 8443,9443 + +View more configuration options at https://www.browserstack.com/local-testing + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + + *** Error: Either another browserstack local client is running on your machine or some server is listening on port 45691 + +To test an internal server, run: +./BrowserStackLocal --key +Example: +./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 + +To test HTML files, run: +./BrowserStackLocal --key --folder +Example: +./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 --folder /Applications/MAMP/htdocs/example/ + + +The following options are available: + -k, --key Browserstack Access Key. This information is available in the local testing section of the Settings page: https://www.browserstack.com/accounts/settings + -f, --folder Specify the Local folder to be used for testing. This option is to be used when testing a local folder. Example: /home/ubuntu/mysite/ or C:\windows\mysite\ + -h, --help Display the help text. + -V, --version Display the current version of the binary. + -F, --force Using this option kills all other instances of BrowserStack Local binary running on this machine with the same --local-identifier options. This option will not affect binaries running in remote servers and instances running with different --local-identifier options. + --only If you want to restrict BrowserStackLocal Binary access to few local servers and/or folders, use this option to restrict them. Usage: host1,port1,ssl?,host2,port2,ssl?. Example: localhost,8000,0,abc.example.com,8080,1 + --force-local Route all traffic via machine where BrowserStackLocal Binary is running. Local tries to fetch public urls directly, unless this option is specified. + --verbose This option sets the level of logging required. Set 1 to debug issues related to setting up connections. Set 2 for logs related to network information. Set 3 to dump all communication to local servers for each request and response. The default value for this option is 1. + --only-automate This option restricts Binary usage to Automate product, and it cannot be used for Live/Screenshot testing. + --proxy-host If you are behind corporate proxy setup, please specify your proxy host using this option. + --proxy-port If you are behind corporate proxy setup, please specify your proxy port using this option. Default value is 3128. + --proxy-user If you are behind corporate proxy which requires authentication, please specify your proxy username using this option. As of now, only HTTP Basic authentication is supported. + --proxy-pass If you are behind corporate proxy which requires authentication, please specify your proxy password using this option. As of now, only HTTP Basic authentication is supported. + --local-identifier If you are running multiple copies of BrowserStackLocal binary (for better performance or other reasons), please specify unique strings for BrowserStack to uniquely identify them. You will need to specify the same string in Automate tests as well. + --force-proxy This options routes all traffic via the proxy specified - otherwise, binary tries to connect directly as well for better performance. + --local-proxy-host If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy host using this option. + --local-proxy-port If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy port using this option. Default assumed is 8081. + --local-proxy-user If your local server is behind a proxy, and it requies authentication - please specify your proxy username using this option. + --local-proxy-pass If your local server is behind a proxy, and it requies authentication - please specify your proxy password using this option. + --daemon Starts or stop the binary as a daemon. Accepts only 2 commands: start, stop. Start will start binary in background. Primarily used in Continous Integration server scripts. + --enable-logging-for-api Include this option to make sure this binary is exposed to Local API for debugging. For more information refer to https://www.browserstack.com/local-testing#local-api-debugging + --log-file Logs all the output to the file specified. + --pac-file Path to pac file with which the proxy needs to be set. + --parallel-runs Specify the number of parallel runs. + --disable-proxy-discovery Disables the Auto-Proxy Discovery + --debug-utility Start BrowserStackLocal in debug mode. + --debug-url Internal/Staging URL BrowserStackLocal will try to connect when started in debug mode. + --https-ports If you want to test local HTTPS server which behind a proxy, in addition to port 443, please pass comma separated port values. Example: --https-ports 8443,9443 + +View more configuration options at https://www.browserstack.com/local-testing + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + + *** Error: Either another browserstack local client is running on your machine or some server is listening on port 45691 + +To test an internal server, run: +./BrowserStackLocal --key +Example: +./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 + +To test HTML files, run: +./BrowserStackLocal --key --folder +Example: +./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 --folder /Applications/MAMP/htdocs/example/ + + +The following options are available: + -k, --key Browserstack Access Key. This information is available in the local testing section of the Settings page: https://www.browserstack.com/accounts/settings + -f, --folder Specify the Local folder to be used for testing. This option is to be used when testing a local folder. Example: /home/ubuntu/mysite/ or C:\windows\mysite\ + -h, --help Display the help text. + -V, --version Display the current version of the binary. + -F, --force Using this option kills all other instances of BrowserStack Local binary running on this machine with the same --local-identifier options. This option will not affect binaries running in remote servers and instances running with different --local-identifier options. + --only If you want to restrict BrowserStackLocal Binary access to few local servers and/or folders, use this option to restrict them. Usage: host1,port1,ssl?,host2,port2,ssl?. Example: localhost,8000,0,abc.example.com,8080,1 + --force-local Route all traffic via machine where BrowserStackLocal Binary is running. Local tries to fetch public urls directly, unless this option is specified. + --verbose This option sets the level of logging required. Set 1 to debug issues related to setting up connections. Set 2 for logs related to network information. Set 3 to dump all communication to local servers for each request and response. The default value for this option is 1. + --only-automate This option restricts Binary usage to Automate product, and it cannot be used for Live/Screenshot testing. + --proxy-host If you are behind corporate proxy setup, please specify your proxy host using this option. + --proxy-port If you are behind corporate proxy setup, please specify your proxy port using this option. Default value is 3128. + --proxy-user If you are behind corporate proxy which requires authentication, please specify your proxy username using this option. As of now, only HTTP Basic authentication is supported. + --proxy-pass If you are behind corporate proxy which requires authentication, please specify your proxy password using this option. As of now, only HTTP Basic authentication is supported. + --local-identifier If you are running multiple copies of BrowserStackLocal binary (for better performance or other reasons), please specify unique strings for BrowserStack to uniquely identify them. You will need to specify the same string in Automate tests as well. + --force-proxy This options routes all traffic via the proxy specified - otherwise, binary tries to connect directly as well for better performance. + --local-proxy-host If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy host using this option. + --local-proxy-port If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy port using this option. Default assumed is 8081. + --local-proxy-user If your local server is behind a proxy, and it requies authentication - please specify your proxy username using this option. + --local-proxy-pass If your local server is behind a proxy, and it requies authentication - please specify your proxy password using this option. + --daemon Starts or stop the binary as a daemon. Accepts only 2 commands: start, stop. Start will start binary in background. Primarily used in Continous Integration server scripts. + --enable-logging-for-api Include this option to make sure this binary is exposed to Local API for debugging. For more information refer to https://www.browserstack.com/local-testing#local-api-debugging + --log-file Logs all the output to the file specified. + --pac-file Path to pac file with which the proxy needs to be set. + --parallel-runs Specify the number of parallel runs. + --disable-proxy-discovery Disables the Auto-Proxy Discovery + --debug-utility Start BrowserStackLocal in debug mode. + --debug-url Internal/Staging URL BrowserStackLocal will try to connect when started in debug mode. + --https-ports If you want to test local HTTPS server which behind a proxy, in addition to port 443, please pass comma separated port values. Example: --https-ports 8443,9443 + +View more configuration options at https://www.browserstack.com/local-testing + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + + *** Error: Either another browserstack local client is running on your machine or some server is listening on port 45691 + +To test an internal server, run: +./BrowserStackLocal --key +Example: +./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 + +To test HTML files, run: +./BrowserStackLocal --key --folder +Example: +./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 --folder /Applications/MAMP/htdocs/example/ + + +The following options are available: + -k, --key Browserstack Access Key. This information is available in the local testing section of the Settings page: https://www.browserstack.com/accounts/settings + -f, --folder Specify the Local folder to be used for testing. This option is to be used when testing a local folder. Example: /home/ubuntu/mysite/ or C:\windows\mysite\ + -h, --help Display the help text. + -V, --version Display the current version of the binary. + -F, --force Using this option kills all other instances of BrowserStack Local binary running on this machine with the same --local-identifier options. This option will not affect binaries running in remote servers and instances running with different --local-identifier options. + --only If you want to restrict BrowserStackLocal Binary access to few local servers and/or folders, use this option to restrict them. Usage: host1,port1,ssl?,host2,port2,ssl?. Example: localhost,8000,0,abc.example.com,8080,1 + --force-local Route all traffic via machine where BrowserStackLocal Binary is running. Local tries to fetch public urls directly, unless this option is specified. + --verbose This option sets the level of logging required. Set 1 to debug issues related to setting up connections. Set 2 for logs related to network information. Set 3 to dump all communication to local servers for each request and response. The default value for this option is 1. + --only-automate This option restricts Binary usage to Automate product, and it cannot be used for Live/Screenshot testing. + --proxy-host If you are behind corporate proxy setup, please specify your proxy host using this option. + --proxy-port If you are behind corporate proxy setup, please specify your proxy port using this option. Default value is 3128. + --proxy-user If you are behind corporate proxy which requires authentication, please specify your proxy username using this option. As of now, only HTTP Basic authentication is supported. + --proxy-pass If you are behind corporate proxy which requires authentication, please specify your proxy password using this option. As of now, only HTTP Basic authentication is supported. + --local-identifier If you are running multiple copies of BrowserStackLocal binary (for better performance or other reasons), please specify unique strings for BrowserStack to uniquely identify them. You will need to specify the same string in Automate tests as well. + --force-proxy This options routes all traffic via the proxy specified - otherwise, binary tries to connect directly as well for better performance. + --local-proxy-host If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy host using this option. + --local-proxy-port If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy port using this option. Default assumed is 8081. + --local-proxy-user If your local server is behind a proxy, and it requies authentication - please specify your proxy username using this option. + --local-proxy-pass If your local server is behind a proxy, and it requies authentication - please specify your proxy password using this option. + --daemon Starts or stop the binary as a daemon. Accepts only 2 commands: start, stop. Start will start binary in background. Primarily used in Continous Integration server scripts. + --enable-logging-for-api Include this option to make sure this binary is exposed to Local API for debugging. For more information refer to https://www.browserstack.com/local-testing#local-api-debugging + --log-file Logs all the output to the file specified. + --pac-file Path to pac file with which the proxy needs to be set. + --parallel-runs Specify the number of parallel runs. + --disable-proxy-discovery Disables the Auto-Proxy Discovery + --debug-utility Start BrowserStackLocal in debug mode. + --debug-url Internal/Staging URL BrowserStackLocal will try to connect when started in debug mode. + --https-ports If you want to test local HTTPS server which behind a proxy, in addition to port 443, please pass comma separated port values. Example: --https-ports 8443,9443 + +View more configuration options at https://www.browserstack.com/local-testing + + +BrowserStackLocal v7.6 + + *** Error: Either another browserstack local client is running on your machine or some server is listening on port 45691 + +To test an internal server, run: +./BrowserStackLocal --key +Example: +./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 + +To test HTML files, run: +./BrowserStackLocal --key --folder +Example: +./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 --folder /Applications/MAMP/htdocs/example/ + + +The following options are available: + -k, --key Browserstack Access Key. This information is available in the local testing section of the Settings page: https://www.browserstack.com/accounts/settings + -f, --folder Specify the Local folder to be used for testing. This option is to be used when testing a local folder. Example: /home/ubuntu/mysite/ or C:\windows\mysite\ + -h, --help Display the help text. + -V, --version Display the current version of the binary. + -F, --force Using this option kills all other instances of BrowserStack Local binary running on this machine with the same --local-identifier options. This option will not affect binaries running in remote servers and instances running with different --local-identifier options. + --only If you want to restrict BrowserStackLocal Binary access to few local servers and/or folders, use this option to restrict them. Usage: host1,port1,ssl?,host2,port2,ssl?. Example: localhost,8000,0,abc.example.com,8080,1 + --force-local Route all traffic via machine where BrowserStackLocal Binary is running. Local tries to fetch public urls directly, unless this option is specified. + --verbose This option sets the level of logging required. Set 1 to debug issues related to setting up connections. Set 2 for logs related to network information. Set 3 to dump all communication to local servers for each request and response. The default value for this option is 1. + --only-automate This option restricts Binary usage to Automate product, and it cannot be used for Live/Screenshot testing. + --proxy-host If you are behind corporate proxy setup, please specify your proxy host using this option. + --proxy-port If you are behind corporate proxy setup, please specify your proxy port using this option. Default value is 3128. + --proxy-user If you are behind corporate proxy which requires authentication, please specify your proxy username using this option. As of now, only HTTP Basic authentication is supported. + --proxy-pass If you are behind corporate proxy which requires authentication, please specify your proxy password using this option. As of now, only HTTP Basic authentication is supported. + --local-identifier If you are running multiple copies of BrowserStackLocal binary (for better performance or other reasons), please specify unique strings for BrowserStack to uniquely identify them. You will need to specify the same string in Automate tests as well. + --force-proxy This options routes all traffic via the proxy specified - otherwise, binary tries to connect directly as well for better performance. + --local-proxy-host If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy host using this option. + --local-proxy-port If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy port using this option. Default assumed is 8081. + --local-proxy-user If your local server is behind a proxy, and it requies authentication - please specify your proxy username using this option. + --local-proxy-pass If your local server is behind a proxy, and it requies authentication - please specify your proxy password using this option. + --daemon Starts or stop the binary as a daemon. Accepts only 2 commands: start, stop. Start will start binary in background. Primarily used in Continous Integration server scripts. + --enable-logging-for-api Include this option to make sure this binary is exposed to Local API for debugging. For more information refer to https://www.browserstack.com/local-testing#local-api-debugging + --log-file Logs all the output to the file specified. + --pac-file Path to pac file with which the proxy needs to be set. + --parallel-runs Specify the number of parallel runs. + --disable-proxy-discovery Disables the Auto-Proxy Discovery + --debug-utility Start BrowserStackLocal in debug mode. + --debug-url Internal/Staging URL BrowserStackLocal will try to connect when started in debug mode. + --https-ports If you want to test local HTTPS server which behind a proxy, in addition to port 443, please pass comma separated port values. Example: --https-ports 8443,9443 + +View more configuration options at https://www.browserstack.com/local-testing + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + + *** Error: Either another browserstack local client is running on your machine or some server is listening on port 45691 + +To test an internal server, run: +./BrowserStackLocal --key +Example: +./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 + +To test HTML files, run: +./BrowserStackLocal --key --folder +Example: +./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 --folder /Applications/MAMP/htdocs/example/ + + +The following options are available: + -k, --key Browserstack Access Key. This information is available in the local testing section of the Settings page: https://www.browserstack.com/accounts/settings + -f, --folder Specify the Local folder to be used for testing. This option is to be used when testing a local folder. Example: /home/ubuntu/mysite/ or C:\windows\mysite\ + -h, --help Display the help text. + -V, --version Display the current version of the binary. + -F, --force Using this option kills all other instances of BrowserStack Local binary running on this machine with the same --local-identifier options. This option will not affect binaries running in remote servers and instances running with different --local-identifier options. + --only If you want to restrict BrowserStackLocal Binary access to few local servers and/or folders, use this option to restrict them. Usage: host1,port1,ssl?,host2,port2,ssl?. Example: localhost,8000,0,abc.example.com,8080,1 + --force-local Route all traffic via machine where BrowserStackLocal Binary is running. Local tries to fetch public urls directly, unless this option is specified. + --verbose This option sets the level of logging required. Set 1 to debug issues related to setting up connections. Set 2 for logs related to network information. Set 3 to dump all communication to local servers for each request and response. The default value for this option is 1. + --only-automate This option restricts Binary usage to Automate product, and it cannot be used for Live/Screenshot testing. + --proxy-host If you are behind corporate proxy setup, please specify your proxy host using this option. + --proxy-port If you are behind corporate proxy setup, please specify your proxy port using this option. Default value is 3128. + --proxy-user If you are behind corporate proxy which requires authentication, please specify your proxy username using this option. As of now, only HTTP Basic authentication is supported. + --proxy-pass If you are behind corporate proxy which requires authentication, please specify your proxy password using this option. As of now, only HTTP Basic authentication is supported. + --local-identifier If you are running multiple copies of BrowserStackLocal binary (for better performance or other reasons), please specify unique strings for BrowserStack to uniquely identify them. You will need to specify the same string in Automate tests as well. + --force-proxy This options routes all traffic via the proxy specified - otherwise, binary tries to connect directly as well for better performance. + --local-proxy-host If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy host using this option. + --local-proxy-port If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy port using this option. Default assumed is 8081. + --local-proxy-user If your local server is behind a proxy, and it requies authentication - please specify your proxy username using this option. + --local-proxy-pass If your local server is behind a proxy, and it requies authentication - please specify your proxy password using this option. + --daemon Starts or stop the binary as a daemon. Accepts only 2 commands: start, stop. Start will start binary in background. Primarily used in Continous Integration server scripts. + --enable-logging-for-api Include this option to make sure this binary is exposed to Local API for debugging. For more information refer to https://www.browserstack.com/local-testing#local-api-debugging + --log-file Logs all the output to the file specified. + --pac-file Path to pac file with which the proxy needs to be set. + --parallel-runs Specify the number of parallel runs. + --disable-proxy-discovery Disables the Auto-Proxy Discovery + --debug-utility Start BrowserStackLocal in debug mode. + --debug-url Internal/Staging URL BrowserStackLocal will try to connect when started in debug mode. + --https-ports If you want to test local HTTPS server which behind a proxy, in addition to port 443, please pass comma separated port values. Example: --https-ports 8443,9443 + +View more configuration options at https://www.browserstack.com/local-testing + + +BrowserStackLocal v7.6 + + *** Error: Either another browserstack local client is running on your machine or some server is listening on port 45691 + +To test an internal server, run: +./BrowserStackLocal --key +Example: +./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 + +To test HTML files, run: +./BrowserStackLocal --key --folder +Example: +./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 --folder /Applications/MAMP/htdocs/example/ + + +The following options are available: + -k, --key Browserstack Access Key. This information is available in the local testing section of the Settings page: https://www.browserstack.com/accounts/settings + -f, --folder Specify the Local folder to be used for testing. This option is to be used when testing a local folder. Example: /home/ubuntu/mysite/ or C:\windows\mysite\ + -h, --help Display the help text. + -V, --version Display the current version of the binary. + -F, --force Using this option kills all other instances of BrowserStack Local binary running on this machine with the same --local-identifier options. This option will not affect binaries running in remote servers and instances running with different --local-identifier options. + --only If you want to restrict BrowserStackLocal Binary access to few local servers and/or folders, use this option to restrict them. Usage: host1,port1,ssl?,host2,port2,ssl?. Example: localhost,8000,0,abc.example.com,8080,1 + --force-local Route all traffic via machine where BrowserStackLocal Binary is running. Local tries to fetch public urls directly, unless this option is specified. + --verbose This option sets the level of logging required. Set 1 to debug issues related to setting up connections. Set 2 for logs related to network information. Set 3 to dump all communication to local servers for each request and response. The default value for this option is 1. + --only-automate This option restricts Binary usage to Automate product, and it cannot be used for Live/Screenshot testing. + --proxy-host If you are behind corporate proxy setup, please specify your proxy host using this option. + --proxy-port If you are behind corporate proxy setup, please specify your proxy port using this option. Default value is 3128. + --proxy-user If you are behind corporate proxy which requires authentication, please specify your proxy username using this option. As of now, only HTTP Basic authentication is supported. + --proxy-pass If you are behind corporate proxy which requires authentication, please specify your proxy password using this option. As of now, only HTTP Basic authentication is supported. + --local-identifier If you are running multiple copies of BrowserStackLocal binary (for better performance or other reasons), please specify unique strings for BrowserStack to uniquely identify them. You will need to specify the same string in Automate tests as well. + --force-proxy This options routes all traffic via the proxy specified - otherwise, binary tries to connect directly as well for better performance. + --local-proxy-host If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy host using this option. + --local-proxy-port If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy port using this option. Default assumed is 8081. + --local-proxy-user If your local server is behind a proxy, and it requies authentication - please specify your proxy username using this option. + --local-proxy-pass If your local server is behind a proxy, and it requies authentication - please specify your proxy password using this option. + --daemon Starts or stop the binary as a daemon. Accepts only 2 commands: start, stop. Start will start binary in background. Primarily used in Continous Integration server scripts. + --enable-logging-for-api Include this option to make sure this binary is exposed to Local API for debugging. For more information refer to https://www.browserstack.com/local-testing#local-api-debugging + --log-file Logs all the output to the file specified. + --pac-file Path to pac file with which the proxy needs to be set. + --parallel-runs Specify the number of parallel runs. + --disable-proxy-discovery Disables the Auto-Proxy Discovery + --debug-utility Start BrowserStackLocal in debug mode. + --debug-url Internal/Staging URL BrowserStackLocal will try to connect when started in debug mode. + --https-ports If you want to test local HTTPS server which behind a proxy, in addition to port 443, please pass comma separated port values. Example: --https-ports 8443,9443 + +View more configuration options at https://www.browserstack.com/local-testing + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + + +BrowserStackLocal v7.6 + +You can now access your local server(s) in our remote browser. + +Press Ctrl-C to exit + + diff --git a/spec/beef/api/auth_rate_spec.rb b/spec/beef/api/auth_rate_spec.rb index 0fae341f7..34b6e6a0c 100644 --- a/spec/beef/api/auth_rate_spec.rb +++ b/spec/beef/api/auth_rate_spec.rb @@ -16,6 +16,7 @@ RSpec.describe 'BeEF API Rate Limit' do # Load BeEF extensions and modules # Always load Extensions, as previous changes to the config from other tests may affect # whether or not this test passes. + print_info "Loading in BeEF::Extensions" BeEF::Extensions.load sleep 2 diff --git a/spec/beef/core/main/autorun_engine/autorun_engine_spec.rb b/spec/beef/core/main/autorun_engine/autorun_engine_spec.rb index e908d24f9..98043d35a 100644 --- a/spec/beef/core/main/autorun_engine/autorun_engine_spec.rb +++ b/spec/beef/core/main/autorun_engine/autorun_engine_spec.rb @@ -21,6 +21,7 @@ RSpec.describe 'AutoRunEngine test' do # Load BeEF extensions and modules # Always load Extensions, as previous changes to the config from other tests may affect # whether or not this test passes. + print_info "Loading in BeEF::Extensions" BeEF::Extensions.load sleep 2 @@ -86,6 +87,19 @@ RSpec.describe 'AutoRunEngine test' do @response = RestClient.post "#{RESTAPI_ADMIN}/login", { 'username': "#{@username}", 'password': "#{@password}" }.to_json, :content_type => :json @token = JSON.parse(@response)['token'] end + + before(:each) do + # Hook new victim + print_info 'Hooking a new victim, waiting a few seconds...' + @victim = @driver.navigate.to "#{VICTIM_URL}" + + # Give time for browser hook to occur + sleep 3 + + # Identify Session ID of victim generated above + @hooks = RestClient.get "#{RESTAPI_HOOKS}?token=#{@token}" + @session = JSON.parse(@hooks)['hooked-browsers']['online']['0']['session'] + end after(:all) do print_info "Shutting down server" @@ -93,12 +107,7 @@ RSpec.describe 'AutoRunEngine test' do Process.kill("KILL",@pids) end - it 'AutoRunEngine is working' do - print_info 'Hooking a new victim, waiting a few seconds...' - victim = BeefTest.new_victim - - sleep 3 - + it 'AutoRunEngine is working', :run_on_browserstack => true do response = RestClient.get "#{RESTAPI_HOOKS}?token=#{@token}" result_data = JSON.parse(response) diff --git a/spec/beef/core/main/handlers/browser_details_handler_spec.rb b/spec/beef/core/main/handlers/browser_details_handler_spec.rb index cbff8845b..5ec5204e9 100644 --- a/spec/beef/core/main/handlers/browser_details_handler_spec.rb +++ b/spec/beef/core/main/handlers/browser_details_handler_spec.rb @@ -20,6 +20,7 @@ RSpec.describe 'Browser details handler' do # Load BeEF extensions and modules # Always load Extensions, as previous changes to the config from other tests may affect # whether or not this test passes. + print_info "Loading in BeEF::Extensions" BeEF::Extensions.load sleep 2 @@ -78,15 +79,19 @@ RSpec.describe 'Browser details handler' do # Authenticate to REST API & pull the token from the response @response = RestClient.post "#{RESTAPI_ADMIN}/login", { 'username': "#{@username}", 'password': "#{@password}" }.to_json, :content_type => :json @token = JSON.parse(@response)['token'] + end + before(:each) do # Hook new victim print_info 'Hooking a new victim, waiting a few seconds...' - @victim = BeefTest.new_victim + @victim = @driver.navigate.to "#{VICTIM_URL}" - sleep 3 + # Give time for browser hook to occur + sleep 3 # Identify Session ID of victim generated above - @hooks = JSON.parse(RestClient.get "#{RESTAPI_HOOKS}?token=#{@token}") + @hooks = RestClient.get "#{RESTAPI_HOOKS}?token=#{@token}" + @session = JSON.parse(@hooks)['hooked-browsers']['online']['0']['session'] end after(:all) do @@ -95,18 +100,16 @@ RSpec.describe 'Browser details handler' do Process.kill("KILL",@pids) end - it 'can successfully hook a browser' do - expect(@hooks['hooked-browsers']['online']).not_to be_empty + it 'can successfully hook a browser', :run_on_browserstack => true do + expect(JSON.parse(@hooks)['hooked-browsers']['online']).not_to be_empty end - it 'browser details handler working' do - session_id = @hooks['hooked-browsers']['online']['0']['session'] - + it 'browser details handler working', :run_on_browserstack => true do print_info "Getting browser details" - response = RestClient.get "#{RESTAPI_HOOKS}/#{session_id}?token=#{@token}" + response = RestClient.get "#{RESTAPI_HOOKS}/#{@session}?token=#{@token}" details = JSON.parse(response.body) - - expect(@victim.driver.browser.browser.to_s.downcase).to eql (details['browser.name.friendly'].downcase) + + expect(@driver.browser.to_s.downcase).to eql (details['browser.name.friendly'].downcase) end diff --git a/spec/beef/extensions/requester_spec.rb b/spec/beef/extensions/requester_spec.rb index 70a4c7ecb..eeef705ae 100644 --- a/spec/beef/extensions/requester_spec.rb +++ b/spec/beef/extensions/requester_spec.rb @@ -19,7 +19,7 @@ RSpec.describe 'BeEF Extension Requester' do end # default skipped because browser hooking not working properly in travis-CI - xit 'requester works' do + xit 'requester works', :run_on_browserstack => true do # start beef server @config = BeEF::Core::Configuration.instance @@ -63,10 +63,13 @@ RSpec.describe 'BeEF Extension Requester' do response = api.auth() @token = response[:token] puts "authenticated. api token: #{@token}" - puts 'hooking a new victim, waiting a few seconds...' - victim = BeefTest.new_victim - sleep 3 + # Hook new victim + print_info 'Hooking a new victim, waiting a few seconds...' + victim = @driver.navigate.to "#{VICTIM_URL}" + + # Give time for browser hook to occur + sleep 3 response = RestClient.get "#{RESTAPI_HOOKS}", {:params => {:token => @token}} puts "hooks response: #{response}" diff --git a/spec/beef/extensions/websocket_hooked_browser_spec.rb b/spec/beef/extensions/websocket_hooked_browser_spec.rb index ac5476a27..1d3633c9e 100644 --- a/spec/beef/extensions/websocket_hooked_browser_spec.rb +++ b/spec/beef/extensions/websocket_hooked_browser_spec.rb @@ -19,6 +19,7 @@ RSpec.describe 'BeEF WebSockets enabled' do @username = @config.get('beef.credentials.user') @password = @config.get('beef.credentials.passwd') #load extensions, best practice is to reload as previous tests can potentially cause issues. + print_info "Loading in BeEF::Extensions" BeEF::Extensions.load sleep 2 if @config.get('beef.module').nil? @@ -53,7 +54,7 @@ RSpec.describe 'BeEF WebSockets enabled' do sleep 1 end - it 'can hook a browser with websockets' do + it 'can hook a browser with websockets', :run_on_browserstack => true do #prepare for the HTTP model https = BeEF::Core::Models::Http @@ -62,22 +63,20 @@ RSpec.describe 'BeEF WebSockets enabled' do api = BeefRestClient.new('http', ATTACK_DOMAIN, '3000', BEEF_USER, BEEF_PASSWD) response = api.auth() @token = response[:token] - puts 'hooking a new victim, waiting a few seconds...' - victim = BeefTest.new_victim - sleep 2 + + # Hook new victim + print_info 'Hooking a new victim, waiting a few seconds...' + victim = @driver.navigate.to "#{VICTIM_URL}" + + # Give time for browser hook to occur + sleep 3 + #Uses the response and hooked browser details to get the response response = RestClient.get "#{RESTAPI_HOOKS}", {:params => {:token => @token}} #test for the response if errors and weirdness there # puts "#{response} from the rest client " hb_details = JSON.parse(response.body) - while hb_details["hooked-browsers"]["online"].empty? - # get victim session - response = RestClient.get "#{RESTAPI_HOOKS}", {:params => {:token => @token}} - hb_details = JSON.parse(response.body) - puts "json: #{hb_details}" - puts "can hook a browser" - puts "online hooked browsers empty: #{hb_details["hooked-browsers"]["online"].empty?}" - end + #get the hooked browser details hb_session = hb_details["hooked-browsers"]["online"]["0"]["session"] #show the address of what is being hooked diff --git a/spec/beef/modules/debug/test_beef_debugs_spec.rb b/spec/beef/modules/debug/test_beef_debugs_spec.rb index 272300670..b4f3d54fb 100644 --- a/spec/beef/modules/debug/test_beef_debugs_spec.rb +++ b/spec/beef/modules/debug/test_beef_debugs_spec.rb @@ -19,7 +19,8 @@ RSpec.describe 'BeEF Debug Command Modules:' do # Load BeEF extensions and modules # Always load Extensions, as previous changes to the config from other tests may affect - # whether or not this test passes. + # whether or not this test passes. + print_info "Loading in BeEF::Extensions" BeEF::Extensions.load sleep 2 @@ -79,16 +80,6 @@ RSpec.describe 'BeEF Debug Command Modules:' do @response = RestClient.post "#{RESTAPI_ADMIN}/login", { 'username': "#{@username}", 'password': "#{@password}" }.to_json, :content_type => :json @token = JSON.parse(@response)['token'] - # Hook new victim - print_info 'Hooking a new victim, waiting a few seconds...' - @victim = BeefTest.new_victim - - sleep 3 - - # Identify Session ID of victim generated above - @hooks = RestClient.get "#{RESTAPI_HOOKS}?token=#{@token}" - @session = JSON.parse(@hooks)['hooked-browsers']['online']['0']['session'] - # Grab Command Module IDs as they can differ from machine to machine @debug_mod_ids = JSON.parse(RestClient.get "#{RESTAPI_MODULES}?token=#{@token}") @debug_mod_names_ids = {} @@ -98,6 +89,19 @@ RSpec.describe 'BeEF Debug Command Modules:' do end end + before(:each) do + # Hook new victim + print_info 'Hooking a new victim, waiting a few seconds...' + @victim = @driver.navigate.to "#{VICTIM_URL}" + + # Give time for browser hook to occur + sleep 3 + + # Identify Session ID of victim generated above + @hooks = RestClient.get "#{RESTAPI_HOOKS}?token=#{@token}" + @session = JSON.parse(@hooks)['hooked-browsers']['online']['0']['session'] + end + after(:all) do print_info "Shutting down server" Process.kill("KILL",@pid) diff --git a/spec/spec_helper.rb b/spec/spec_helper.rb index 724bb0e77..3aa82e9e9 100644 --- a/spec/spec_helper.rb +++ b/spec/spec_helper.rb @@ -36,10 +36,10 @@ class Capybara::Selenium::Driver < Capybara::Driver::Base end TASK_ID = (ENV['TASK_ID'] || 0).to_i -CONFIG_NAME = ENV['CONFIG_NAME'] || 'windows_chrome' -CONFIG = YAML.safe_load(File.read("./spec/support/#{CONFIG_NAME}.config.yml")) -CONFIG['user'] = ENV['BROWSERSTACK_USERNAME'] || CONFIG['user'] -CONFIG['key'] = ENV['BROWSERSTACK_ACCESS_KEY'] || CONFIG['key'] +CONFIG_FILE = ENV['CONFIG_FILE'] || 'windows/windows_chrome_latest.config.yml' +CONFIG = YAML.safe_load(File.read("./spec/support/browserstack/#{CONFIG_FILE}")) +CONFIG['user'] = ENV['BROWSERSTACK_USERNAME'] || '' +CONFIG['key'] = ENV['BROWSERSTACK_ACCESS_KEY'] || '' ## DB config ActiveRecord::Base.logger = nil diff --git a/spec/support/osx_chrome.config.yml b/spec/support/browserstack/osx/osx_chrome_latest.config.yml similarity index 86% rename from spec/support/osx_chrome.config.yml rename to spec/support/browserstack/osx/osx_chrome_latest.config.yml index 1ca53fc1d..867ea597c 100644 --- a/spec/support/osx_chrome.config.yml +++ b/spec/support/browserstack/osx/osx_chrome_latest.config.yml @@ -2,9 +2,9 @@ server: "hub-cloud.browserstack.com" common_caps: "build": "OSX Chrome" - "browserstack.debug": true "name": "BStack Test Run" "project": "My Project" + "browserstack.local": true browser_caps: - diff --git a/spec/support/osx_firefox.config.yml b/spec/support/browserstack/osx/osx_firefox_latest.config.yml similarity index 86% rename from spec/support/osx_firefox.config.yml rename to spec/support/browserstack/osx/osx_firefox_latest.config.yml index 5ee0a8436..2d8a72f15 100644 --- a/spec/support/osx_firefox.config.yml +++ b/spec/support/browserstack/osx/osx_firefox_latest.config.yml @@ -2,9 +2,9 @@ server: "hub-cloud.browserstack.com" common_caps: "build": "OSX Firefox" - "browserstack.debug": true "name": "BStack Test Run" "project": "My Project" + "browserstack.local": true browser_caps: - diff --git a/spec/support/osx_safari.config.yml b/spec/support/browserstack/osx/osx_safari_latest.config.yml similarity index 86% rename from spec/support/osx_safari.config.yml rename to spec/support/browserstack/osx/osx_safari_latest.config.yml index 63186b9bd..3eab34b3d 100644 --- a/spec/support/osx_safari.config.yml +++ b/spec/support/browserstack/osx/osx_safari_latest.config.yml @@ -2,9 +2,9 @@ server: "hub-cloud.browserstack.com" common_caps: "build": "OSX Safari" - "browserstack.debug": true "name": "BStack Test Run" "project": "My Project" + "browserstack.local": true browser_caps: - diff --git a/spec/support/windows_chrome.config.yml b/spec/support/browserstack/windows/windows_chrome_latest.config.yml similarity index 78% rename from spec/support/windows_chrome.config.yml rename to spec/support/browserstack/windows/windows_chrome_latest.config.yml index 13d6be1a3..cc3f7eed6 100644 --- a/spec/support/windows_chrome.config.yml +++ b/spec/support/browserstack/windows/windows_chrome_latest.config.yml @@ -2,11 +2,11 @@ server: "hub-cloud.browserstack.com" common_caps: "build": "Windows Chrome" - "browserstack.debug": true "name": "BStack Test Run" "project": "My Project" + "browserstack.local": true browser_caps: - "browser": "chrome" - "os": "Windows" \ No newline at end of file + "os": "windows" \ No newline at end of file diff --git a/spec/support/windows_edge.config.yml b/spec/support/browserstack/windows/windows_edge_latest.config.yml similarity index 86% rename from spec/support/windows_edge.config.yml rename to spec/support/browserstack/windows/windows_edge_latest.config.yml index 6842b7dce..ca83f6860 100644 --- a/spec/support/windows_edge.config.yml +++ b/spec/support/browserstack/windows/windows_edge_latest.config.yml @@ -2,9 +2,9 @@ server: "hub-cloud.browserstack.com" common_caps: "build": "Windows Edge" - "browserstack.debug": true "name": "BStack Test Run" "project": "My Project" + "browserstack.local": true browser_caps: - diff --git a/spec/support/windows_firefox.config.yml b/spec/support/browserstack/windows/windows_firefox_latest.config.yml similarity index 87% rename from spec/support/windows_firefox.config.yml rename to spec/support/browserstack/windows/windows_firefox_latest.config.yml index 76671339e..7e70c936c 100644 --- a/spec/support/windows_firefox.config.yml +++ b/spec/support/browserstack/windows/windows_firefox_latest.config.yml @@ -2,9 +2,9 @@ server: "hub-cloud.browserstack.com" common_caps: "build": "Windows Firefox" - "browserstack.debug": true "name": "BStack Test Run" "project": "My Project" + "browserstack.local": true browser_caps: - diff --git a/spec/support/windows_ie.config.yml b/spec/support/browserstack/windows/windows_ie_latest.config.yml similarity index 87% rename from spec/support/windows_ie.config.yml rename to spec/support/browserstack/windows/windows_ie_latest.config.yml index 7b0105f80..e16295522 100644 --- a/spec/support/windows_ie.config.yml +++ b/spec/support/browserstack/windows/windows_ie_latest.config.yml @@ -2,9 +2,9 @@ server: "hub-cloud.browserstack.com" common_caps: "build": "Windows IE" - "browserstack.debug": true "name": "BStack Test Run" "project": "My Project" + "browserstack.local": true browser_caps: -