mahara-contributors team mailing list archive

[Mahara Bot <1742600@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://reviews.mahara.org/8424
Committed: https://git.mahara.org/mahara/mahara/commit/226787057fb32bec1a64a74fabf6cea3b7afe618
Submitter: Robert Lyon (robertl@xxxxxxxxxxxxxxx)
Branch:    17.10_STABLE

commit 226787057fb32bec1a64a74fabf6cea3b7afe618
Author: Rebecca Blundell <rebecca.blundell@xxxxxxxxxxxxxxx>
Date:   Thu Jan 11 16:19:03 2018 +1300

Bug 1742600: update chromedriver for behat tests

I have successfully run tests with the new version of chromedriver
(2.35) and chrome (63). I thought the best way to test further was to
let maharabot run the test suite and see if any issues come up.

failing tests are now fixed.

behatnotneeded

Change-Id: I22e45e8a95669e2109ca70ae782aa2c40546db14

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1742600

Title:
  chromedriver version needs updating for running tests

Status in Mahara:
  Fix Committed
Status in Mahara 16.10 series:
  In Progress
Status in Mahara 17.04 series:
  In Progress
Status in Mahara 17.10 series:
  Fix Committed
Status in Mahara 18.04 series:
  Fix Committed

Bug description:
  Chrome has been causing errors in running behat tests since version
  61. As a work around I pinned my version of chrome as in this wiki
  page:
  https://wiki.mahara.org/wiki/Testing/Behat_Testing/Error_%26_Solutions#Tests_failing_erratically_since_Chrome.2FChromium_upgrade_to_version_61

  However, it seems like the issue can be resolved by updating
  chromedriver. Details of chrome versions supported by versions of
  chromedriver:
  https://sites.google.com/a/chromium.org/chromedriver/downloads

  I have now successfully run tests with chrome 63 and chromedriver
  2.35, so this seems to be the fix.

  
  Further info:
  In order to unpin your chrome/chromium versions if you used the workaround, run apt-mark unhold commands on the packages you have installed - e.g:

   sudo apt-mark unhold chromium-browser
   sudo apt-mark unhold chromium-codecs-ffmpeg-extra
   sudo apt-mark unhold chromium-codecs-ffmpeg
   sudo apt-mark unhold google-chrome

  I had an issue upgrading after that, which was solved by reading this: 
  https://askubuntu.com/questions/724093/no-more-updates-for-google-chrome-apt-get-update-error/724146 and running:
  echo "deb http://dl.google.com/linux/chrome/deb/ stable main" | sudo tee /etc/apt/sources.list.d/google-chrome.list  
  wget -q -O - https://dl.google.com/linux/linux_signing_key.pub | sudo apt-key add -  
  sudo apt-get update
  sudo apt-get install google-chrome-stable

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1742600/+subscriptions