Firefox use default profile about tachometer HOT 5 CLOSED

I'm currently trawling through selenium / Firefox docs working out how to change this, even just documenting it could help.

from tachometer.

My thinking has been that it makes sense to have a clean-room browser by default, so that extensions etc. won't interfere with the benchmark. (This is also the Selenium default). I could definitely see a useDefaultProfile: true or similar setting, though, which would know how to do that for all browsers.

We do have instructions for changing profiles in Chrome using the addArguments setting: https://github.com/Polymer/tachometer#profiles

However, it seems that we don't currently support addArguments for Firefox. I'll add that, test out profile switching, and update the docs.

from tachometer.

However, it seems that we don't currently support addArguments for Firefox. I'll add that, test out profile switching, and update the docs.

This would be an absolutely massive help thanks for considering it. Even just persisting a unique profile that can be shared between runs would be fine as well, the annoying part is having to uniquely update the certificate chain on each run.

from tachometer.

I've added a new browser.profile setting in #226, which works for Firefox and Chrome. I also fixed the addArguments bug, though you shouldn't need that now that browser.profile exists.

I also published a pre-release version so you can test this out early: npm i tachometer@^0.5.10-pre.0.

See https://github.com/Polymer/tachometer/blob/4b3faa4dc12e539dd19a6db1ef3ebb37eb8b1798/README.md#profiles for documentation.

Would love to hear if it works for you. It worked for me so far on macOS and Linux.

from tachometer.

I also published a pre-release version so you can test this out early: npm i tachometer@^0.5.10-pre.0.

Just released 0.5.10 final FYI

from tachometer.