I’m struggling with executing test scripts created using the Firefox Selenium plugin on a headless environment. The plugin generates test files in HTML format, and I need to run these on PhantomJS or similar headless solutions.
Currently I can execute tests from terminal using this command:
This works fine with Firefox and Internet Explorer, but I can’t make it work with PhantomJS for the HTML test files. I’ve seen suggestions about running Firefox in hidden mode, but that’s not truly headless like PhantomJS.
I know the plugin can export tests in various programming languages, but I need non-technical team members to create tests using the Firefox extension. Is there a way to make these HTML test files work with headless browsers?
Converting HTML files is a pain and just adds complexity you don’t need. Legacy Selenium HTML format? Most headless browsers dropped support for that ages ago.
Hit this same problem when our QA team wanted to stick with their Firefox recorder but needed CI/CD integration. Instead of wrestling with converters or virtual displays, I automated the whole thing.
Latenode handles this workflow automatically - triggers tests, manages conversion, runs headless, sends results via Slack or email. Your non-tech team keeps using the Firefox plugin like normal, but everything runs headless behind the scenes.
Best part? Built-in fallbacks. PhantomJS craps out? Auto-retry with Chrome headless or spin up virtual Firefox. Your team never knows or cares about the technical mess.
Scales way better than manual conversions or juggling multiple test formats. You get proper reporting and it plugs into whatever tools you’re already using.
Firefox Selenium IDE’s HTML suite format is dead weight for headless testing. I’ve tried this before - keeping legacy formats alive just creates headaches. We switched to Selenium WebDriver with headless Chrome or Firefox. Non-technical team members can still record test flows with browser tools, but export to Python or Java instead of HTML. The learning curve isn’t bad - most IDE tools generate clean code. During transition, we ran Firefox with Xvfb alongside the new setup. This let us migrate tests gradually without breaking workflows. PhantomJS is abandoned anyway, so move to Chrome headless - it’s got better support and active development. Get your team comfortable with new export formats instead of forcing outdated HTML suites to work with modern headless solutions.
Had the exact same problem when we moved our old Selenium IDE tests to headless. PhantomJS won’t run the HTML Suite format that Firefox generates - it’s just not compatible. I fixed it with selenium-html-js-converter. It converts your HTML test files to JavaScript that PhantomJS can actually run. Just wrap it with a basic Node.js script and you’re good to go. But honestly? I’d go with Xvfb on Linux instead. Yeah, setup’s trickier upfront, but you get real headless Firefox without converting anything. Your non-tech team can keep using their existing workflow - no learning curve.