Similar effects to me as we also use codeception for acceptance testing for one of our company internal web applications. The application is running within FF as this is the only approved and deployed browser by our IT. Thus using Chrome for testing is not an option.
As I recently updated my codeception (within Ubuntu 16.04) to 2.3.5, new I also updated the tool chain to FF 55.0.3, geckdriver v0.18.0, Selenium 3.5.3
but I get attached error returned when executing my test:
If I start the same test with the tool chain:
codeception 2.3.5, old FF 41.0.1, geckdriver v0.11.1, Selenium 2.53.1
The test is working fine.
Is there a recommended setup/tool chain for FF codeception (2.3.5) acceptance testing?
Is there regular testing/recommandation done for a FF setup when releasing codeception? Or is it out of scope of codeception development and user has to check for appropriate tool chain?