From b89af7e54afab8a27fcb5aae0c71bb97cc17d65a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E5=AE=89=E9=9D=99=E7=9A=84=E6=8D=82=E4=BD=8F=E8=80=B3?= =?UTF-8?q?=E6=9C=B5?= <34530046+msglog@users.noreply.github.com> Date: Fri, 2 Sep 2022 17:09:54 +0800 Subject: [PATCH] Update AuthoringTestScripts.md --- Docs/AuthoringTestScripts.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Docs/AuthoringTestScripts.md b/Docs/AuthoringTestScripts.md index e14316b2..b4db4e46 100644 --- a/Docs/AuthoringTestScripts.md +++ b/Docs/AuthoringTestScripts.md @@ -59,7 +59,8 @@ NotepadSession.FindElementByClassName("Edit").SendKeys("This is some text"); There are three tools help you inspect UI elements: - inspect.exe -The latest Microsoft Visual Studio version by default includes the Windows SDK with a great tool to inspect the application you are testing. This tool allows you to see every UI element/node that you can query using Windows Application Driver. This **inspect.exe** tool can be found under the Windows SDK folder which is typically `C:\Program Files (x86)\Windows Kits\10\bin\x86` +The latest Microsoft Visual Studio version by default includes the Windows SDK with a great tool to inspect the application you are testing. This tool allows you to see every UI element/node that you can query using Windows Application Driver. This **inspect.exe** tool can be found under the Windows SDK folder which is typically `C:\Program Files (x86)\Windows Kits\10\bin\XXXXXX\x86` +![image](https://user-images.githubusercontent.com/34530046/188105681-99657fb2-fb0c-4dc1-9ad4-87e4529625ee.png) More detailed documentation on Inspect is available on MSDN .