blob: 93a5780da2501cc5413ff95ba3d74629a2f63def (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
|
// Copyright 2018 Yahoo Holdings. Licensed under the terms of the Apache 2.0 license. See LICENSE in the project root.
package ai.vespa.hosted.cd;
import org.junit.jupiter.api.Tag;
import org.junit.jupiter.api.Test;
import java.lang.annotation.Retention;
import java.lang.annotation.Target;
import static java.lang.annotation.ElementType.ANNOTATION_TYPE;
import static java.lang.annotation.ElementType.TYPE;
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?
*
* @author jonmv
*/
@Target({TYPE, ANNOTATION_TYPE})
@Retention(RUNTIME)
@IntegrationTest
@Tag("staging")
public @interface StagingTest {
// Want to verify documents are not damaged by upgrade.
// May want to verify metrics during upgrade.
}
|
