Since `python setup.py sdist` provides the actual tarball that will be
installed via `easy_install`, `pip install`, etc. it should also be tested.
The existing `pip install -e $WORKSPACE` tests the .egg-link install format
#------------------------------------------------------------------------------#
#------------------------------------------------------------------------------#
-# test building the source tarball
+# test building the source tarball, then installing it
cd $WORKSPACE
python2 setup.py sdist
cd $WORKSPACE
python2 setup.py sdist
+rm -rf $WORKSPACE/env
+virtualenv --python=python2 $WORKSPACE/env
+. $WORKSPACE/env/bin/activate
+pip install dist/fdroidserver-*.tar.gz
+
+# run tests in new pip+virtualenv install
+fdroid=$WORKSPACE/env/bin/fdroid $WORKSPACE/tests/run-tests $apksource
+
#------------------------------------------------------------------------------#
#------------------------------------------------------------------------------#
-# test install using site packages
+# test install using install direct from git repo
cd $WORKSPACE
rm -rf $WORKSPACE/env
virtualenv --python=python2 --system-site-packages $WORKSPACE/env
cd $WORKSPACE
rm -rf $WORKSPACE/env
virtualenv --python=python2 --system-site-packages $WORKSPACE/env
python2 setup.py install
# run tests in new pip+virtualenv install
python2 setup.py install
# run tests in new pip+virtualenv install
-. $WORKSPACE/env/bin/activate
fdroid=$WORKSPACE/env/bin/fdroid $WORKSPACE/tests/run-tests $apksource
fdroid=$WORKSPACE/env/bin/fdroid $WORKSPACE/tests/run-tests $apksource