#7167 closed defect (rejected)

Automated tests fail on Firefox Windows

Reported by: Ross Assignee:
Priority: Unknown Milestone:
Module: Automation Keywords: closed-in-favor-of-gitlab
Cc: sebastian, kzar Blocked By:
Blocking: Platform: Firefox
Ready: no Confidential: no
Tester: Unknown Verified working: no
Review URL(s):



adblockpluschrome / master / 2207:96eda29ae585

How to reproduce

  1. Run npm test on Windows.

Observed behaviour

Following on from #7166. If I manually add the webdriver binaries to my PATH env, Chrome works fine.

However Firefox/Gecko fails with the following when ran against the current live version of testpages.adblockplus.org:

AssertionError [ERR_ASSERTION]: Element Hiding - Class Selector
+ expected - actual


at takeScreenshot.then.screenshot (test\wrappers\pages.js:240:22)

And fails with the following when run against a locally running version of the test pages:

NoSuchFrameError: Unable to locate frame: undefined
      at Object.throwDecodedError (node_modules\selenium-webdriver\lib\error.js:514:15)
      at parseHttpResponse (node_modules\selenium-webdriver\lib\http.js:519:13)
      at doSend.then.response (node_modules\selenium-webdriver\lib\http.js:441:30)
      at <anonymous>
      at process._tickCallback (internal/process/next_tick.js:188:7)
  From: Task: WebDriver.switchTo().frame(0)
      at thenableWebDriverProxy.schedule (node_modules\selenium-webdriver\lib\webdriver.js:807:17)
      at TargetLocator.frame (node_modules\selenium-webdriver\lib\webdriver.js:1824:25)
      at closeWindow (test\wrappers\pages.js:61:25)
      at resolve (test\wrappers\pages.js:43:52)
      at new Promise (<anonymous>)
      at driver.switchTo.window.then (test\wrappers\pages.js:43:9)

Expected behaviour

The automated tests to run in Firefox succesfully.

Change History (1)

comment:1 Changed 13 months ago by sebastian

  • Keywords closed-in-favor-of-gitlab added
  • Resolution set to rejected
  • Status changed from new to closed

Sorry, but we switched to GitLab. If this issue is still relevant, please file it again in the new issue tracker.

Note: See TracTickets for help on using tickets.