Skip to content

Commit fa320b1

Browse files
committed
fixes related to Rido's comments
1 parent 0fc5be7 commit fa320b1

File tree

1 file changed

+5
-10
lines changed

1 file changed

+5
-10
lines changed

articles/certification/how-to-test-pnp.md

Lines changed: 5 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ This article shows you how to:
1717

1818
- Install the Azure IoT command-line tool extension for the Azure CLI
1919
- Run the IoT Plug and Play tests to validate your device application while in-development phase
20-
- Use the Azure Certified Device portal to validate the device application
20+
2121
> [!Note]
2222
> A full walk through the certification process can be found in the [Azure Certified Device certification tutorial](tutorial-00-selecting-your-certification.md).
2323
@@ -30,14 +30,13 @@ The application code that runs on your IoT Plug and Play must:
3030

3131
The application is software that's installed separately from the operating system or is bundled with the operating system in a firmware image that's flashed to the device.
3232

33-
The certification process verifies the device is IoT Plug and Play compatible by validating that the device implementation matches the telemetry, properties and commands defined in the [Digital Twins Definition Language (DTDL)](https://github.com/Azure/opendigitaltwins-dtdl) device model, and that the model is available in the [Azure IoT Public Model Repository](../iot-develop/concepts-model-repository.md).
33+
Prior to certifying your device through the certification process for IoT Plug and Play, you will want to validate that the device implementation matches the telemetry, properties and commands defined in the [Digital Twins Definition Language (DTDL)](https://github.com/Azure/opendigitaltwins-dtdl) device model locally prior to submitting to the [Azure IoT Public Model Repository](../iot-develop/concepts-model-repository.md).
3434

3535
To meet the certification requirements, your device must:
3636

3737
- Connects to Azure IoT Hub using the [DPS](../iot-dps/about-iot-dps.md).
3838
- Implement of telemetry, properties, or commands following the IoT Plug and Play convention.
3939
- Describe the device interactions with a [DTDL v2](https://aka.ms/dtdl) model.
40-
- Publish the model, and all required interfaces, in the [Azure IoT Public Model Repository](https://devicemodels.azureiotsolutions.com/)
4140
- Send the model ID during [DPS registration](../iot-develop/concepts-developer-guide-device.md#dps-payload) in the DPS provisioning payload.
4241
- Announce the model ID during the [MQTT connection](../iot-develop/concepts-developer-guide-device.md#model-id-announcement).
4342

@@ -48,8 +47,7 @@ The [Azure IoT CLI extension](/cli/azure/ext/azure-iot/iot/product?view=azure-cl
4847
The following steps show you how to prepare for and run the certification tests using the CLI:
4948

5049
### Install the Azure IoT extension for the Azure CLI
51-
52-
See the installation instructions to set up the [Azure CLI](https://docs.microsoft.com/cli/azure/iot?view=azure-cli-latest) in your environment.
50+
Install the [Azure CLI](/cli/azure/install-azure-cli) and review the installation instructions to set up the [Azure CLI](/cli/azure/iot?view=azure-cli-latest) in your environment.
5351

5452
To install the Azure IoT Extension, run the following command:
5553

@@ -70,9 +68,6 @@ The following command creates a test using DPS with a symmetric key attestation
7068
az iot product test create --badge-type Pnp --at SymmetricKey --device-type FinishedProduct --models {local folder name}
7169
```
7270

73-
> [!NOTE]
74-
> You need to [sign in](https://docs.microsoft.com/cli/azure/authenticate-azure-cli?view=azure-cli-latest) to your subscription when you use the CLI.
75-
7671
The JSON output from the command contains the `primaryKey`, `registrationId`, and `scopeID` to use when you connect your device.
7772

7873
Expected output:
@@ -101,7 +96,7 @@ When the device is connected and ready to interact with the IoT hub, generate a
10196
- Use the `--wait` parameter to get the test case.
10297

10398
```azurecli
104-
az iot product test task create --type GenerateTestCases --test-id d45d53d9-656d-4be7-9bbf-140bc87e98dc --wait
99+
az iot product test task create --type GenerateTestCases --test-id [YourTestId] --wait
105100
```
106101

107102
Expected output:
@@ -124,7 +119,7 @@ You can use the `az iot product test case update` command to modify the test con
124119
After you generate the test configuration, the next step is to run the tests. Use the same `devicetestId` from the previous commands as parameter to run the tests. Check the test results to make sure that all tests have a status `Passed`.
125120

126121
```azurecli
127-
az iot product test task create --type QueueTestRun --test-id d45d53d9-656d-4be7-9bbf-140bc87e98dc --wait
122+
az iot product test task create --type QueueTestRun --test-id [YourTestId] --wait
128123
```
129124

130125
Example test run output

0 commit comments

Comments
 (0)