Skip to content

Commit aaf7f43

Browse files
authored
Update safe-upgrades-helm-test.md
1 parent 1b07e2b commit aaf7f43

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/operator-service-manager/safe-upgrades-helm-test.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.service: azure-operator-service-manager
99
---
1010

1111
# Run tests after install or upgrade
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 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.
1313

1414
## Overview
1515
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
2727
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.
2828

2929
## 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:
3131

3232
* enable
3333
* 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
4343
* Default value is no filter.
4444

4545
## 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`.
4747

4848
## 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.
5050

5151
```
5252
"roleOverrideValues": [
@@ -82,7 +82,7 @@ Following is an unescaped example `roleOverrideValues` NF Payload with `testOpti
8282
]
8383
```
8484

85-
## NF payload complete example
85+
## NF payload example
8686
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.
8787

8888
```

0 commit comments

Comments
 (0)