Vote count:
0
I'm trying to run functional tests in Firefox of some javascript code that relies on an extension to be loaded. In Chrome, I'm able to do this by telling the browser launcher to launch Chrome with --load-extension=<path>. I have not found an analog to this in Firefox, nor any other clear way to do this.
My first attempt was to try to launch Firefox with a custom profile using the -profile <path> command line switch, but when trying to reverse-engineer the firefox profile extension metadata it looks like there are some absolute paths in there that would make the profile not portable (i.e. i couldn't check it into git and have another developer be able to clone and run tests, because it would be looking for my machine's paths).
Does anyone know a good way to handle this? I'd really like it if I wasn't forced to generate the extensions.json each time the tests are run.
How can I load a Firefox extension cross-platform in a functional test CI environment?
Aucun commentaire:
Enregistrer un commentaire