You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This article describes how Azure Operator Service Manager (AOSM) can run tests on deployed network functions (NFs) as part install or upgrade operations. When enabled, each network function application (nfApp) will be tested after install or upgrade completion. A successful result of all nfApp tests are required for the NF operation status to complete successfully.
12
+
This article describes how Azure Operator Service Manager (AOSM) can run tests on deployed network functions (NFs) as part install or upgrade operations. When enabled, each network function application (nfApp) will be tested after install or upgrade completion. A successful result across all nfApp tests is required for the NF operation status to complete successfully.
13
13
14
14
## Overview
15
15
This feature's scope is to run helm tests as part of the network function install or upgrade operations.
@@ -27,7 +27,7 @@ This feature's scope is to run helm tests as part of the network function instal
27
27
The publisher is responsible for authoring the helm tests during construction of the helm charts. The helm tests are defined in the helm chart under the folder: `<ChartName>/Templates/`. Each test includes a job definition that specifies a container environment and command to run. The container environment should exit successfully for a test to be considered a success. The job definition must include the helm test hook annotation `(helm.sh/hook: test)` to be recognized as a test by helm.
28
28
29
29
## Enable helm tests during operations
30
-
AOSM provides a set of configurable install and upgrade options for each component under an NF. These existing options are extended with a new 'testOptions` parameter. This gives the user the ability to specify testOptions per nfApp and as per the type of operation. The following parameters are supported by the testOptions flag:
30
+
AOSM provides a set of configurable install and upgrade options for each component under an NF. These existing options are extended with a new `testOptions` parameter. This parameter gives the user the ability to specify `testOptions` per nfApp and as per the type of operation. The `testOptions` feature supports the following parameters:
31
31
32
32
* enable
33
33
* Enables or disables the helm test on a nfApp after install or upgrade completes.
@@ -43,10 +43,10 @@ AOSM provides a set of configurable install and upgrade options for each compone
43
43
* Default value is no filter.
44
44
45
45
## Exposing helm test control via parameters
46
-
Users already can use the NF payload parameter `roleOverrideValues` to specify settings for `installOptions` and `upgradeOptions`. These fields are now extended to include settings for `testOptions` which can be specified for each nfApplication and each operation method. See the following example of `roleOverrideValues` usage where the NF Payload speificies`installOptions` and `upgradeOptions` including `TestOptions` for a component named `application1`.
46
+
Users already can use the NF payload parameter `roleOverrideValues` to specify settings for `installOptions` and `upgradeOptions`. These fields are now extended to include settings for `testOptions` which can be specified for each nfApplication and each operation method. See the following example of `roleOverrideValues` usage where the NF Payload defines`installOptions` and `upgradeOptions` including `testOptions` for a component named `application1`.
47
47
48
48
## roleOverrideValues escaped example:
49
-
Following is an escaped example `roleOverrideValues` with `testOptions` under `installOptions` and `upgradeOptions` for a component named `application1`. This example uses a `filter` to execute only those test which match the string provided.
49
+
Following is an escaped example `roleOverrideValues` with `testOptions` under `installOptions` and `upgradeOptions` for a component named `application1`. This example uses a `filter` to execute only tests which match the string provided.
50
50
51
51
```
52
52
"roleOverrideValues": [
@@ -82,7 +82,7 @@ Following is an unescaped example `roleOverrideValues` NF Payload with `testOpti
82
82
]
83
83
```
84
84
85
-
## NF payload complete example
85
+
## NF payload example
86
86
Following is an example NF Payload with `testOptions` under `installOptions` and `upgradeOptions` for a component named `application1`. This example uses a `filter` to execute only those test which match the string provided.
0 commit comments