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
Copy file name to clipboardExpand all lines: articles/certification/how-to-test-pnp.md
+5-10Lines changed: 5 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ This article shows you how to:
17
17
18
18
- Install the Azure IoT command-line tool extension for the Azure CLI
19
19
- 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
+
21
21
> [!Note]
22
22
> A full walk through the certification process can be found in the [Azure Certified Device certification tutorial](tutorial-00-selecting-your-certification.md).
23
23
@@ -30,14 +30,13 @@ The application code that runs on your IoT Plug and Play must:
30
30
31
31
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.
32
32
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).
34
34
35
35
To meet the certification requirements, your device must:
36
36
37
37
- Connects to Azure IoT Hub using the [DPS](../iot-dps/about-iot-dps.md).
38
38
- Implement of telemetry, properties, or commands following the IoT Plug and Play convention.
39
39
- 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/)
41
40
- Send the model ID during [DPS registration](../iot-develop/concepts-developer-guide-device.md#dps-payload) in the DPS provisioning payload.
42
41
- Announce the model ID during the [MQTT connection](../iot-develop/concepts-developer-guide-device.md#model-id-announcement).
43
42
@@ -48,8 +47,7 @@ The [Azure IoT CLI extension](/cli/azure/ext/azure-iot/iot/product?view=azure-cl
48
47
The following steps show you how to prepare for and run the certification tests using the CLI:
49
48
50
49
### 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.
53
51
54
52
To install the Azure IoT Extension, run the following command:
55
53
@@ -70,9 +68,6 @@ The following command creates a test using DPS with a symmetric key attestation
70
68
az iot product test create --badge-type Pnp --at SymmetricKey --device-type FinishedProduct --models {local folder name}
71
69
```
72
70
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
-
76
71
The JSON output from the command contains the `primaryKey`, `registrationId`, and `scopeID` to use when you connect your device.
77
72
78
73
Expected output:
@@ -101,7 +96,7 @@ When the device is connected and ready to interact with the IoT hub, generate a
101
96
- Use the `--wait` parameter to get the test case.
102
97
103
98
```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
105
100
```
106
101
107
102
Expected output:
@@ -124,7 +119,7 @@ You can use the `az iot product test case update` command to modify the test con
124
119
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`.
125
120
126
121
```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
0 commit comments