Remove APIv1 test server from functional tests.

There are too many exceptions required, and this is now very old.
photo · Sep 14, 2013 · 379f332 · 379f332
1 parent 9721fb2
commit 379f332
Show file tree

Hide file tree

Showing 2 changed files with 0 additions and 12 deletions.
diff --git a/run_functional_tests b/run_functional_tests
@@ -14,17 +14,6 @@ export TROVEBOX_TEST_CONFIG=test
 unset TROVEBOX_TEST_SERVER_API
 python -m unittest discover --catch tests/functional
 
-# Test server running APIv1 Trovebox instance
-# Install from photo/frontend commit 660b2ab
-tput setaf 3
-echo
-echo "Testing APIv1 self-hosted site..."
-tput sgr0
-sleep 1
-export TROVEBOX_TEST_CONFIG=test-apiv1
-export TROVEBOX_TEST_SERVER_API=1
-python -m unittest discover --catch tests/functional
-
 # Test server running v3.0.8 Trovebox instance
 # Install from photo/frontend commit e9d81de57b
 tput setaf 3

diff --git a/tests/functional/README.markdown b/tests/functional/README.markdown
@@ -100,7 +100,6 @@ To use it, you must set up multiple Trovebox instances and create the following
 config files containing your credentials:
 
     test              : Latest self-hosted site (from photo/frontend master branch)
-    test-apiv1        : APIv1 self-hosted site (from photo/frontend commit 660b2ab)
     test-3.0.8        : v3.0.8 self-hosted site (from photo/frontend commit e9d81de57b)
     test-hosted       : Credentials for test account on http://<xxxx>.trovebox.com
     test-hosted-https : Same as test-hosted, but with https://