fix(tests): configure Travis CI to use PhantomJS2

*  @see https://mediocre.com/forum/topics/phantomjs-2-and-travis-ci-we-beat-our-heads-against-a-wall-so-you-dont-have-to

Author: ThomasBurleson

.travis.yml

@@ -11,6 +11,12 @@ branches:
     - master
     - patch
 
+before_install:
+  - mkdir travis-phantomjs
+  - wget https://bitbucket.org/ariya/phantomjs/downloads/phantomjs-2.1.1-linux-x86_64.tar.bz2 -O $PWD/travis-phantomjs/phantomjs-2.1.1-linux-x86_64.tar.bz2
+  - tar -xvf $PWD/travis-phantomjs/phantomjs-2.1.1-linux-x86_64.tar.bz2 -C $PWD/travis-phantomjs
+  - export PATH=$PWD/travis-phantomjs/phantomjs-2.1.1-linux-x86_64/bin:$PATH
+
 before_script:
   - export DISPLAY=:99.0 # firefox virtual screen
   - sh -e /etc/init.d/xvfb start # firefox virtual screen
@@ -27,3 +33,5 @@ after_success:
 
 notifications:
   flowdock: ca58afe1354053b15fe75a763138829d
+
+

package.json

@@ -59,7 +59,7 @@
     "karma-chrome-launcher": "^0.1.4",
     "karma-firefox-launcher": "^0.1.3",
     "karma-jasmine": "^0.3.6",
-    "karma-phantomjs2-launcher": "~0.1.4",
+    "karma-phantomjs2-launcher": "0.4.0",
     "karma-safari-launcher": "^0.1.1",
     "karma-sauce-launcher": "^0.2.10",
     "lazypipe": "^0.2.2",