Vagrant and Chef are here used to launch and provision an Ubuntu 14.04 virtual machine for the purpose of running headless browser end to end tests against AngularJS web applications using Protractor, a test tool that works with the established Selenium and WebDriver ecosystem framework.
The following items are installed on the VM:
Download the latest Vagrant installer for your platform from http://downloads.vagrantup.com. Don't use the Vagrant version in the default package repositories because it is far too old.
To obtain a suitably recent version of Virtualbox, just follow the instructions at the Virtualbox website. You can either download a package, or set up your package management system to use the latest branches:
For example, for Ubuntu 14.04 (Trusty) add this line to
deb trusty contrib
wget -q -O- | sudo apt-key add -sudo apt-get updatesudo apt-get install virtualbox-4.3
The vagrant-omnibus plugin installs or updates the version of Chef in the Vagrant VM:
vagrant plugin install vagrant-omnibus
Librarian-chef is a tool for managing your cookbooks, and will fetch them based on the contents of the Cheffile in the project directory. To install on Ubuntu 14.04 you will have to first update to Ruby 2.*, such by using RVM, and then:
sudo gem install chef librarian-chef
Adjust as appropriate for other distributions.
To use this VM to test an AngularJS applications with Protractor first alter the Vagrantfile to create synced folders that include the relevant Protractor configuration files. E.g.:
config.vm.synced_folder "/my-workspace/project", "/project"config.vm.synced_folder "/my-workspace", "/workspace"
A running instance of the AngularJS application is also needed, but this can be on another VM or remote server. Since Protractor uses Selenium, the tested application can be anywhere so long as its web server is accessible from the Protractor VM.
Once the above pieces are in place:
cd /path/to/protractor-selenium-server-vagrantlibrarian-chef installvagrant up
This will launch and provision your virtual machine. Note that installing the Oracle JDK can take a while. Once done you can set up and run Protractor tests in the server, using configuration scripts from your synced project directories.
A trivial test Express server, Jasmine test cases, and Protractor configuration
are included under the
test directory in this repository. To verify that the
Vagrant VM setup is correct and functional, log in via SSH:
cd /path/to/protractor-selenium-server-vagrantvagrant ssh
Then install Express globally and run the Protractor tests for various browsers. All should pass:
sudo npm install -g expresscd /vagrant/testprotractor protractor.conf.chromium.jsprotractor protractor.conf.firefox.jsprotractor protractor.conf.phantomjs.js
These Protractor configuration files launch the Express server before tests run and then shut it down afterwards. This is neither common nor recommended as an approach to end to end testing, but it is helpful here.
Bringing up a new server is a lengthy provisioning process. Many packages are required to install Chromium and Firefox on a headless server, and this can take quite the long time. This is not well suited to creating servers on demand: you are better off provisioning once, creating an image, and then instantiating new VMs from that image.
Since late 2013 it has frequently been the case that at least one of Chromium, Firefox, or PhantomJS does not function in this setup when using the latest stable versions of every package from the default Ubuntu and NPM repositories.
For example, in Q2 2014 there was a blocking issue in the interaction between the libGL library and Chromium in Ubuntu 14.04. In Q1 2015 for Ubuntu 14.04 there was a blocking issue in the interaction between current latest release versions of Protractor and PhantomJS, and another blocking issue in the interaction between Selenium 2.44.0 and Firefox 35.0. You are not even safe to back down to Ubuntu 12.04 where things have been more stable in the past, as there versions of Chromedriver and Chromium slipped out of sync with one another in Q1 2015.
The provisioning used here installs the latest generally available releases for all items of interest exception for Selenium, where the version must be specified. Depending on the situation at the time of use, you may want to either update to versions yet to make it into the general repositories, or downgrade selectively. The best approach to take depends on the details of the issue at the time, so there is little advice to be given, unfortunately.