Submit an idea and make Sauce Labs even better!
Capture tunnel traffic. Make an option to get it by rest api call passing session ID as param
BrowserMob+SauceConnect combination doesnt work because:
1. While 50x tests are using the same tunnel at a time, it is impossible to separate traffic produced by test in particular thread.
2. Browsermob also sucks to route the heavy traffic produced by dozens of tests properly. We cant afford individual tunnel per test.
Essentially, we would like to have an option to download the traffic produced by the app during the session for further analysis.
Example case is app crash. In that case having har file we could determine what happened just before the crash (e. g. server not responded). Also requests may contain session id used by every particular test, so being able to track this data back (e. g. for night run) would make us able to better troubleshoot whats happened with the backend team.
Third case is capturing the latest request produced by app ui manipulation, then repeating it 10x times by test framework making requirwd updates on the way (e. g. instead of filling the form 10 times).
And lots and lots more useful scenarios.
I'd like to find out more about what you are trying to do if you had this data. What is the use case / why do you need to capture tunnel traffic? Would BrowserMob help you? (See https://wiki.saucelabs.com/display/DOCS/Sauce+Connect+Proxy+with+an+Additional+Proxy+Setup#SauceConnectProxywithanAdditionalProxySetup-BrowserMobProxyConfiguration and http://bmp.lightbody.net/)
You won't be notified about changes to this idea.