Skip to content

Commit d9c631e

Browse files
Merge pull request #204822 from chuckb1300/julyUpdates
Update to image
2 parents 7101f56 + f9ff6ae commit d9c631e

File tree

6 files changed

+20
-23
lines changed

6 files changed

+20
-23
lines changed

articles/certification/how-to-test-device-update.md

Lines changed: 20 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -19,38 +19,35 @@ The [Device Update for IoT Hub](..\iot-hub-device-update\understand-device-updat
1919
* Upload your .SWU file to a blob storage location of your choice.
2020
* Create a SAS URL for accessing the uploaded .SWU file.
2121

22-
## Testing the device
23-
1. On the Connect + test page, select **"Yes"** for the **"Are you able to test Device Update for IoT Hub?"** question.
24-
> [!Note]
25-
> If you are not able to test Device Update and select No, you will still be able to run all other Secured-core tests, but your product will not be eligible for certification.
22+
## Test the device
23+
1. On the Connect + test page, select **"Yes"** for the **"Are you able to test Device Update for IoT Hub?"** question.
24+
> [!Note]
25+
> If you are not able to test Device Update and select No, you will still be able to run all other Secured-core tests, but your product will not be eligible for certification.
2626

27-
:::image type="content" source="./media/how-to-adu/connect-test.png" alt-text="Dialog that shows the Connect + test user interface to select OS and Firmware interface.":::
27+
:::image type="content" source="./media/how-to-adu/connect-test.png" alt-text="Dialog to confirm that you are able to test device for IoT Hub.":::
2828

2929
2. Proceed with connecting your device to the test infrastructure.
3030

31-
3. Select **"Upload"** to upload the ".manifest.json" file.
31+
3. On the Select Requirement Validation step, select **"Upload"**.
32+
:::image type="content" source="./media/how-to-adu/connect-and-test.png" alt-text="Dialog that shows the selected tests that will be validated.":::
3233

33-
4. On the Select Requirement Validation step, select the **"Upload"** button at the bottom of the page.
34-
35-
:::image type="content" source="./media/how-to-adu/select-tests.png" alt-text="Dialog that shows the selected tests that will be validated.":::
36-
37-
5. Upload your .importmanifest.json file by selecting the **Choose File** button. Select your file and then select the **Upload** button.
38-
> [!Note]
39-
> The file extension must be .importmanifest.json.
34+
4. Upload your .importmanifest.json file by selecting the **Choose File** button. Select your file and then select the **Upload** button.
35+
> [!Note]
36+
> The file extension must be .importmanifest.json.
4037

41-
:::image type="content" source="./media/how-to-adu/upload-swu.png" alt-text="Dialog that shows how the SWU file can be uploaded.":::
38+
:::image type="content" source="./media/how-to-adu/upload-manifest.png" alt-text="Dialog to instruct the user to upload the .importmanifest.json file by selecting the choose File button.":::
4239

43-
6. Copy and Paste the SAS URL to the location of your .SWU file in the provided input box, then select the **Validate** button.
44-
:::image type="content" source="./media/how-to-adu/validate-swu.png" alt-text="Dialog that shows how the SAS url is applied.":::
40+
5. Copy and Paste the SAS URL to the location of your .SWU file in the provided input box, then select the **Validate** button.
41+
:::image type="content" source="./media/how-to-adu/input-sas-url.png" alt-text="Dialog that shows how the SAS url is applied.":::
4542

46-
7. Once we’ve validated our service can reach the provided URL, select **Import**.
47-
:::image type="content" source="./media/how-to-adu/staging-complete.png" alt-text="Dialog that shows the staging process is complete":::
43+
6. Once we’ve validated our service can reach the provided URL, select **Import**.
44+
:::image type="content" source="./media/how-to-adu/finalize-import.png" alt-text="Dialog to inform the user that the SAS URL was reachable and that the user needs to click import.":::
4845

49-
> [!Note]
50-
> If you receive an “Invalid SAS URL” message, generate a new SAS URL from your storage blob and try again.
46+
> [!Note]
47+
> If you receive an “Invalid SAS URL” message, generate a new SAS URL from your storage blob and try again.
5148

52-
8. Select **Continue** to proceed
49+
7. Select **Continue** to proceed
5350

54-
9. Congratulations! You're now ready to proceed with Edge Secured-core testing.
51+
8. Congratulations! You're now ready to proceed with Edge Secured-core testing.
5552

56-
10. Select the **Run tests** button to begin the testing process. Your device will be updated as the final step in our Edge Secured-core testing.
53+
9. Select the **Run tests** button to begin the testing process. Your device will be updated as the final step in our Edge Secured-core testing.
99.9 KB
Loading
36.5 KB
Loading
193 KB
Loading
120 KB
Loading
99.9 KB
Loading

0 commit comments

Comments
 (0)