TechPrufer
Get started
GitLab
GitLab logoGitLab · Feature trail

Browser Testing Frameworks

1 post · Dec 2017

What this trail covers

GitLab transitioned its frontend and RSpec feature tests from PhantomJS to headless Chrome. This involved updating the Karma test runner for frontend tests and switching Capybara's driver from Poltergeist to Selenium/ChromeDriver for backend feature tests. The migration addressed limitations of PhantomJS, such as its outdated rendering engine and JavaScript support, and improved test accuracy and debugging capabilities. Challenges included adapting to Selenium's API differences, such as handling JavaScript modals and element visibility, and refactoring tests that relied on Poltergeist-specific methods like `.trigger('click')`. The new setup allows for running tests in a real, modern browser environment, improving test representativeness and reducing technical debt.

All GitLab trails
  1. How GitLab switched to Headless Chrome for testingThis post details the technical migration from PhantomJS to headless Chrome for GitLab's testing infrastructure. It outlines the reasons for the switch, including PhantomJS's outdated components and lack of modern browser features. For frontend tests using Karma, the change involved updating the `karma-chrome-launcher` plugin. For backend feature tests using RSpec and Capybara, the migration required switching from the Poltergeist driver to Selenium and ChromeDriver. Key challenges and solutions are presented, including adapting to Selenium's handling of JavaScript modals (`accept_alert`, `accept_confirm`), differences in element visibility checks (`visible: :any`), and the absence of Poltergeist's `.trigger('click')` method, necessitating test refactoring to use standard `.click` actions or alternative event simulation. The post also provides configuration examples for Capybara and discusses the benefits of running tests in a real browser environment.