pywb/.travis.yml

language: python

python:
  - "2.7"
  - "3.5"
  - "3.6"

os:
  - linux

addons:
  sauce_connect: true

cache:
  directories:
    - $HOME/.cache/pip
    - node_modules

sudo: false

install:
  #- pip install boto certauth youtube-dl
  #- pip install git+https://github.com/esnme/ultrajson.git
  - python setup.py -q install
  - pip install -r extra_requirements.txt
  - pip install coverage pytest-cov coveralls
  - npm install

before_script:
  - export DISPLAY=:99.0
  - sh -e /etc/init.d/xvfb start

script:
  - python setup.py test
  - cd karma-tests && make test

after_success:
    coveralls
add .travis.yml for Travis CI! 2014-01-23 16:20:51 -08:00			`language: python`
cleanup .travis.yml, remove lxml 2014-08-06 14:01:59 -07:00
add .travis.yml for Travis CI! 2014-01-23 16:20:51 -08:00			`python:`
fixes for 2.6 and pypy 2014-03-04 18:49:36 -08:00			`- "2.7"`
proxy: ensure proxy cert download sets content length proxy options: 'use_default_coll' must specify exact default coll (otherwise a random coll is chosen, as ordering is not defined) travis: add py3.4, py3.5! 2016-02-23 18:09:09 -08:00			`- "3.5"`
build: update gevent, support py3.6 2017-03-09 11:59:54 -08:00			`- "3.6"`
cleanup .travis.yml, remove lxml 2014-08-06 14:01:59 -07:00
travisci: experiment with travis improvements (new container build) 2014-12-23 12:39:33 -08:00			`os:`
			`- linux`
Add configuration for running client tests using Sauce Labs This gives us the capability to test the client-side JS rewriting against a suite of different browsers on different platforms. Note that getting Karma running on Travis CI requires some additional configuration documented at github.com/karma-runner/karma-sauce-launcher/issues/73 which is not made clear in the original documentation. In order to run the Karma tests, the Sauce Labs username and access keys need to be passed in via the SAUCE_USERNAME and SAUCE_ACCESS_KEYS env vars. 2015-11-25 12:18:56 +00:00
Enable Sauce Connect in Travis Rather than specifying the username and encrypted key in the Travis config, we just enable Sauce Connect and require SAUCE_USERNAME and SAUCE_ACCESS_KEY env vars to be set. This is so that the Karma tests have the same env vars available to them which they can use to check whether to run against Sauce Labs or not. 2015-11-26 11:07:07 +00:00			`addons:`
			`sauce_connect: true`

Add Python and node_module caching Speed up Travis CI rebuilds by caching pip and npm dependencies. 2015-11-25 12:49:59 +00:00			`cache:`
			`directories:`
			`- $HOME/.cache/pip`
			`- node_modules`
travisci: experiment with travis improvements (new container build) 2014-12-23 12:39:33 -08:00
			`sudo: false`

add .travis.yml for Travis CI! 2014-01-23 16:20:51 -08:00			`install:`
build process: simplify build process by moving essential deps to requirements.txt, and extras to extra_requirements.txt setup.py just loads from requirements.txt Dockerfile pip installs requirements, then extra requirements for improved cacheing travis runs setup install, then installs extra requirements 2017-03-08 17:03:52 -08:00			`#- pip install boto certauth youtube-dl`
			`#- pip install git+https://github.com/esnme/ultrajson.git`
add unit test to timeutils.py tweak .travis.yml 2014-02-25 15:30:16 -08:00			`- python setup.py -q install`
build process: simplify build process by moving essential deps to requirements.txt, and extras to extra_requirements.txt setup.py just loads from requirements.txt Dockerfile pip installs requirements, then extra requirements for improved cacheing travis runs setup install, then installs extra requirements 2017-03-08 17:03:52 -08:00			`- pip install -r extra_requirements.txt`
travis: remove --use-mirrors 2016-02-23 18:39:27 -08:00			`- pip install coverage pytest-cov coveralls`
Add tests for the client-side part of pywb using Karma * Add a Karma configuration for unit/integration tests for the client-side pywb code. * Add an integration test suite which creates an <iframe> loads the client-side rewriting code (wombat.js) in it and then executes a test script. Since wombat.js monkey-patches the DOM and the exact behavior of DOM objects varies between browsers, which we want to test, the suite does not mock the DOM but instead runs a set of tests in an isolated environment against the DOM. * Add Travis config to run the Karma tests 2015-11-25 11:44:04 +00:00			`- npm install`
cleanup .travis.yml, remove lxml 2014-08-06 14:01:59 -07:00
Configure Travis to make Firefox available for Karma tests For some Karma tests, we can run them faster by running against a local browser in the Travis CI instance rather than Sauce Labs. This is also useful for: - Contributors wishing to run the Travis tests against their own forks and have not set up Sauce Labs credentials. - Running Karma tests against Pull Request builds where Sauce Connect is not available. 2015-11-26 10:27:37 +00:00			`before_script:`
			`- export DISPLAY=:99.0`
			`- sh -e /etc/init.d/xvfb start`

travisci: experiment with travis improvements (new container build) 2014-12-23 12:39:33 -08:00			`script:`
Add tests for the client-side part of pywb using Karma * Add a Karma configuration for unit/integration tests for the client-side pywb code. * Add an integration test suite which creates an <iframe> loads the client-side rewriting code (wombat.js) in it and then executes a test script. Since wombat.js monkey-patches the DOM and the exact behavior of DOM objects varies between browsers, which we want to test, the suite does not mock the DOM but instead runs a set of tests in an isolated environment against the DOM. * Add Travis config to run the Karma tests 2015-11-25 11:44:04 +00:00			`- python setup.py test`
			`- cd karma-tests && make test`
testing coveralls 2014-02-24 23:43:32 -08:00
			`after_success:`
			`coveralls`