diff options
Diffstat (limited to 'tenant-cd/src/main/java/ai/vespa/hosted/cd/StagingTest.java')
| -rw-r--r-- | tenant-cd/src/main/java/ai/vespa/hosted/cd/StagingTest.java | 16 |
1 files changed, 3 insertions, 13 deletions
diff --git a/tenant-cd/src/main/java/ai/vespa/hosted/cd/StagingTest.java b/tenant-cd/src/main/java/ai/vespa/hosted/cd/StagingTest.java index 93a5780da25..4ecc3ce5722 100644 --- a/tenant-cd/src/main/java/ai/vespa/hosted/cd/StagingTest.java +++ b/tenant-cd/src/main/java/ai/vespa/hosted/cd/StagingTest.java @@ -14,15 +14,9 @@ import static java.lang.annotation.RetentionPolicy.RUNTIME; /** * 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? + * Test classes annotated with this annotation are run in the second phase of automated staging tests, + * to verify the upgraded deployment. + * See <a href="https://cloud.vespa.ai/automated-deployments.html#staging-tests">Vespa cloud documentation</a>. * * @author jonmv */ @@ -31,8 +25,4 @@ import static java.lang.annotation.RetentionPolicy.RUNTIME; @IntegrationTest @Tag("staging") public @interface StagingTest { - - // Want to verify documents are not damaged by upgrade. - // May want to verify metrics during upgrade. - } |