For the headless (i.e. non-saucelabs) browsertests: Is there a way to assert the absence of or log network errors? Currently it is hard to know what may have caused a failure that is not immediately reproducible.
Description
Description
Related Objects
Related Objects
- Mentioned In
- T118182: headless browsertests: browser console output
- Mentioned Here
- T139740: Port Selenium tests from Ruby to Node.js
Event Timeline
Comment Actions
There is nothing integrated in selenium for this. Can probably be achieved by a network proxy. For Firefox maybe the export to HAR feature of the developer console can be leveraged.
Comment Actions
Unlikely to ever be resolved because of T139740: Port Selenium tests from Ruby to Node.js.