Knowledge Base

  1. Home
  2. Knowledge Base
  3. General
  4. Getting Started
  5. Run options

Run options

This article lists all run options that are available to users.

Run options can be added to the run options entry field in the test script editor. They affect how the script gets executed and add a lot of power and flexibility.

Run optionDescription
#chrome-cli:XAt times, you may want to indicate a specific command line switch for your use case. To that end, you can use this run option in testRTC. Learn more about controlling Chrome command line switches in testRTC.
#disableAudio:XIf you want to force testRTC not to inject its fake audio (and use whatever the browser has by default), then you can use #disableAudio:true

Note that this doesn’t simulate the case where the machine has no mic.

#disableVideo:XIf you want to force testRTC not to inject its fake video (and use whatever the browser has by default), then you can use #disableVideo:true

Note that this doesn’t simulate the case where the machine has no camera.

#ignore-browser-errorstestRTC automatically collects all console logs. If these contain browser errors, they will account as errors of the test and cause it to fail. If you wish to suppress these issues and have testRTC ignore them then use this run option.
#ignore-browser-warningstestRTC automatically collects all console logs. If these contain browser warnings, they will account as warnings of the test and cause it to succeed with warnings. If you wish to suppress these issues and have testRTC ignore them then use this run option.
#ignore-nightwatch-warningstestRTC uses Nightwatch for its scripting language. If there are warnings on Nightwatch they will account for warnings in your test results. If you wish to suppress these issues and have testRTC ignore them then use this run option.
#disable-browser-logstestRTC automatically collects all console logs. Sometimes, these can cause failures or too much “noise”. If you wish to suppress these issues and have testRTC not look and collect browser console logs at all then use this run option.
#random-profileAt times, you may want to run the same test script, but with different machine profiles. To that end, you can use this run option and instead of the usual round robin selection of profiles for probes, it will pick the profiles at random from the list available on the test script.
#session:XThe #session run option is no longer supported. This option has been upgraded to a field in the UI of the test script editor.
Learn more about sessions in testRTC.
#timeout:XThe scripts’ default maximum duration is 3 minutes. In order to keep the system’s resources from endless scripts, the tests manager will stop running scripts if reaching the script’s defined timeout. If you wish to run a longer script, please use the timeout run option #timeout:X.

Try setting the timeout to a reasonable value that isn’t too high – if tests fail and get “stuck”, the time used will be counted to your account.

X is the maximum duration (timeout) in minutes for every test iteration.

#getstatsTells testRTC to collect its metrics using the WebRTC getstats API and not only using webrtc-internals. See collection methods and collection failures for more information
#legacy-getstatsFor applications that collect their own statistics using legacy stats, we might not be able to collect stats on our own. In such a case, try using this run option to instruct testRTC to collect statistics the old way
#no-getstatsIf all else fails and you simply don’t want testRTC to collect statistics using getstats, you can use this run option
#vncYou can open a VNC connection to the tested instance and track the test’s progress. For further information about how to use VNC, please refer to ‘Using VNC’
#webhook:XThe #webhook run option is no longer supported. This option has been upgraded to a field in the UI of the test script editor.
Learn more about integrating webhooks at the end of a test run.
#dynamic-probe:trueForce dynamic allocation of probes when running a test. This slows down allocation and execution of a test for tests with a small number of probes.
#har-fileCollect HAR file, which holds all HTTP network traffic of the browser. To view this file, use netlog-viewer.
#try:NIndicate how many times to retry this test if it fails before deciding this test failed. Useful for monitors who fail intermittently on issues you deem as false positives.

Was this article helpful?

Related Articles

Leave a Reply 0 comments

Leave a Reply: