Try tox.

Author: theengineear

.gitignore

@@ -8,10 +8,12 @@
 
 *.coverage
 
+*.tox
+
 build
 
 dist
 
 debug_script.py
 
-test_output.txt
+test_output.txt

circle.yml

@@ -2,45 +2,47 @@ machine:
 
   environment:
 
-    PLOTLY_PACKAGE_ROOT: /home/ubuntu/${CIRCLE_PROJECT_REPONAME}
     PLOTLY_CONFIG_DIR: ${HOME}/.plotly
-    PLOTLY_PYTHON_VERSIONS: 2.7.8 3.3.3 3.4.1
-    PLOTLY_CORE_REQUIREMENTS_FILE: ${PLOTLY_PACKAGE_ROOT}/requirements.txt
-    PLOTLY_OPTIONAL_REQUIREMENTS_FILE: ${PLOTLY_PACKAGE_ROOT}/optional-requirements.txt
+    TOX_TESTENV_PASSENV: PLOTLY_TOX_*
+    PLOTLY_TOX_PYTHON_27: /home/ubuntu/.pyenv/versions/2.7.10/bin/python2.7
+    PLOTLY_TOX_PYTHON_34: /home/ubuntu/.pyenv/versions/3.4.3/bin/python3.4
+    PLOTLY_TOX_PYTHON_35: /home/ubuntu/.pyenv/versions/3.5.0/bin/python3.5
 
 dependencies:
 
   override:
 
-    # run all the pre-written installers (this will take a *while*)
-    - bash circle/setup.sh
-
-    # install testing tools for circle's version of things
-    - pip install nose coverage
+    # install everything tox knows about and the plotly package.
+    - pip install tox
+    - tox --notest
     - pip install -I .
 
     # we need to cd out of the project root to ensure the install worked
     - cd ~ && python -c "import plotly"
 
   cache_directories:
 
-    - "~/.pyenv/versions"  # attempt to just cache installed pyenv things
+    # cache everything that tox installs for us.
+    - .tox
 
 test:
 
   override:
 
-    # run test suite in all our python versions
-    - bash circle/test.sh
+    # test in 2.7 with coverage.
+    - tox -e py27-core,py27-optional -- --with-coverage --cover-package=plotly
+    - mkdir "${CIRCLE_ARTIFACTS}/2.7" || true
+    - coverage html --omit="*/tests*" -d "${CIRCLE_ARTIFACTS}/2.7" --title=2.7
+
+    # test everything else. see "envlist" matrix in tox.ini for more info.
+    - tox -e py34-core,py34-optional,py35-core,py35-optional
+
+    # import it once normally (ensures .plotly exists)
+    - python -c "import plotly"
 
     # test that it imports when you don't have write permissions
     - sudo chmod -R 444 ${PLOTLY_CONFIG_DIR} && python -c "import plotly"
 
     # test that giving back write permissions works again
     # this also has to pass the test suite that follows
     - sudo chmod -R 777 ${PLOTLY_CONFIG_DIR} && python -c "import plotly"
-
-    # test core things in the general 2.7 version that circle has
-    - nosetests -x plotly/tests/test_core --with-coverage --cover-package=plotly
-    - mkdir "${CIRCLE_ARTIFACTS}/2.7" || true
-    - coverage html -d "${CIRCLE_ARTIFACTS}/2.7" --title=2.7

circle/setup.sh

@@ -0,0 +1,83 @@
+; Tox is a testing tool that manages virtualenvs for testing multiple Python
+; environments in a consistent/controlled way.
+
+; SETTING ENVIRONMENT VARIABLES AND TOX TESTING VARIABLES
+;
+; You can limit tox testing to certain environments via the `-e` (envlist)
+; command line option:
+;    tox -e py27-core,py34-core
+; OR, you can just set the `TOXENV` environment variable, which is handy:
+;    TOXENV=py27-core,py34-core
+;
+; Integrating with the virtualenvs in Circle CI is a bit of a pain. For
+; whatever reason the "executable" `python35` (at the time of writing) cannot
+; be activated directly. Instead the circle.yml file specifies the actual
+; binary directly. Because of this, you too have to set the following env
+; variables:
+;    PLOTLY_TOX_PYTHON_27=python2.7
+;    PLOTLY_TOX_PYTHON_34=python3.4
+;    ...
+; These will be specific to your machine and may not look like the ones above.
+; If you're not testing with all the python versions (see TOXENV above),
+; there's no need to install and map other versions.
+
+; PASSING ADDITONAL ARGUMENTS TO TEST COMMANDS
+; The {posargs} is tox-specific and passes in any command line args after `--`.
+; For example, given the testing command in *this* file:
+;   nosetests {posargs} -x plotly/tests/test_core
+;
+; The following command:
+;   tox -- -a '!slow'
+;
+; Tells tox to call:
+;   nosetests -a '!slow' -x plotly/tests/test_core
+;
+; Which is a nice way to skip slow tests for faster testing cycles.
+
+[tox]
+; The py{A,B,C}-{X,Y} generates a matrix of envs:
+;   pyA-X,pyA-Y,pyB-X,pyB-Y,pyC-X,pyC-Y
+envlist = py{27,34,35}-{core,optional}
+
+; Note that envs can be targeted by deps using the <target>: dep syntax.
+; Only one dep is allowed per line as of the time of writing. The <target>
+; can be a `-` (hyphen) concatenated string of the environments to target
+; with the given dep.
+
+; These commands are general and will be run for *all* environments.
+[testenv]
+deps=
+    mock==2.0.0
+    nose==1.3.7
+    requests==2.12.4
+    six==1.10.0
+    pytz==2016.10
+    optional: numpy==1.11.3
+    optional: ipython[all]==5.1.0
+    optional: pandas==0.19.2
+    optional: scipy==0.18.1
+commands=
+;   Sanity check that we're testing what we *think* we're testing.
+    python --version
+;    core: nosetests {posargs} -x plotly/tests/test_core
+;    optional: nosetests {posargs} -x -a '!matplotlib' plotly/tests
+
+; CORE ENVIRONMENTS
+[testenv:py27-core]
+basepython={env:PLOTLY_TOX_PYTHON_27:}
+
+[testenv:py34-core]
+basepython={env:PLOTLY_TOX_PYTHON_34:}
+
+[testenv:py35-core]
+basepython={env:PLOTLY_TOX_PYTHON_35:}
+
+; OPTIONAL ENVIRONMENTS
+[testenv:py27-optional]
+basepython={env:PLOTLY_TOX_PYTHON_27:}
+
+[testenv:py34-optional]
+basepython={env:PLOTLY_TOX_PYTHON_34:}
+
+[testenv:py35-optional]
+basepython={env:PLOTLY_TOX_PYTHON_35:}