Remove unused test classes

2 files changed, 0 insertions, 54 deletions

diff --git a/tenant-cd/src/main/java/ai/vespa/hosted/cd/FunctionalTest.java b/tenant-cd/src/main/java/ai/vespa/hosted/cd/FunctionalTest.java
deleted file mode 100644
index e6beb313d28..00000000000
--- a/tenant-cd/src/main/java/ai/vespa/hosted/cd/FunctionalTest.java
+++ /dev/null
@@ -1,31 +0,0 @@
-package ai.vespa.hosted.cd;
-
-/**
- * Tests that compare the behaviour of a Vespa application deployment against a fixed specification.
- *
- * These tests are run whenever a change is pushed to a Vespa application, and whenever the Vespa platform
- * is upgraded, and before any deployments to production zones. When these tests fails, the tested change to
- * the Vespa application is not rolled out.
- *
- * A typical functional test is to feed some documents, optionally verifying that the documents have been processed
- * as expected, and then to see that queries give the expected results. Another common use is to verify integration
- * with external services.
- *
- * @author jonmv
- */
-public interface FunctionalTest {
-
-    // Want to feed some documents.
-    // Want to verify document processing and routing is as expected.
-    // Want to check recall on those documents.
-    // Want to verify queries give expected documents.
-    // Want to verify searchers.
-    // Want to verify updates.
-    // Want to verify deletion.
-    // May want to verify reprocessing.
-    // Must likely delete documents between tests.
-    // Must be able to feed documents, setting route.
-    // Must be able to search.
-    // Must be able to visit.
-
-}
diff --git a/tenant-cd/src/main/java/ai/vespa/hosted/cd/UpgradeTest.java b/tenant-cd/src/main/java/ai/vespa/hosted/cd/UpgradeTest.java
deleted file mode 100644
index 32083fbd5f6..00000000000
--- a/tenant-cd/src/main/java/ai/vespa/hosted/cd/UpgradeTest.java
+++ /dev/null
@@ -1,23 +0,0 @@
-package ai.vespa.hosted.cd;
-
-/**
- * Tests that assert continuity of behaviour for Vespa application deployments, through upgrades.
- *
- * These tests are run whenever a change is pushed to a Vespa application, and whenever the Vespa platform
- * is upgraded, and before any deployments to production zones. When these tests fails, the tested change to
- * the Vespa application is not rolled out.
- *
- * A typical upgrade test is to do some operations against a test deployment prior to upgrade, like feed and
- * search for some documents, perhaps recording some metrics from the deployment, and then to upgrade it,
- * repeat the exercise, and compare the results from pre and post upgrade.
- *
- * TODO Split in platform upgrades and application upgrades?
- *
- * @author jonmv
- */
-public interface UpgradeTest {
-
-    // Want to verify documents are not damaged by upgrade.
-    // May want to verify metrics during upgrade.
-
-}