Add readme

doc/devdocs/UITests.md

@@ -0,0 +1,77 @@
+# UI tests framework
+
+ A specialized UI test framework for PowerToys that makes it easy to write UI tests for PowerToys modules or settings. Let's start writing UI tests!
+
+## Before running tests  
+
+- Install Windows Application Driver v1.2.1 from https://github.com/microsoft/WinAppDriver/releases/tag/v1.2.1 to the default directory (`C:\Program Files (x86)\Windows Application Driver`)
+
+- Enable Developer Mode in Windows settings
+
+## Running tests
+
+- Exit PowerToys if it's running.
+
+- Open `PowerToys.sln` in Visual Studio and build the solution.
+
+- Run tests in the Test Explorer (`Test > Test Explorer` or `Ctrl+E, T`).
+
+
+## How to add the first UI tests for your modules
+
+- Create a new project and add the following references to the project file. Change the OutputPath to your own module's path.
+```
+	<PropertyGroup>
+		<OutputType>Library</OutputType>
+		<!-- This is a UI test, so don't run as part of MSBuild -->
+		<RunVSTest>false</RunVSTest>
+	</PropertyGroup>
+
+	<PropertyGroup>
+		<OutputPath>..\..\..\..\$(Platform)\$(Configuration)\tests\KeyboardManagerUITests\</OutputPath>
+	</PropertyGroup>
+
+	<ItemGroup>
+	    <PackageReference Include="MSTest" />
+	    <ProjectReference Include="..\..\..\common\UITestAutomation\UITestAutomation.csproj" />
+	    <Folder Include="Properties\" />
+	</ItemGroup>
+```
+- Inherit your test class from UITestBase.
+>Set Scope: The default scope starts from the PowerToys settings UI. If you want to start from your own module, set the constructor as shown below:
+
+ >Default Scope:
+```
+[TestClass]
+public class RunFancyZonesTest : UITestBase
+{
+    public RunFancyZonesTest()
+        : base()
+    {
+    }
+}
+```
+>Specify Score:
+```
+[TestClass]
+public class RunFancyZonesTest : UITestBase
+{
+    public RunFancyZonesTest()
+        : base(PowerToysModule.FancyZone)
+    {
+    }
+}
+```
+
+- Then you can start using session to perform the UI operations.
+
+**Example**
+See the file: 
+```PowerToys\src\modules\keyboardmanager\KeyboardManagerUITests\RunKeyboardManagerUITests.cs```
+
+
+## Extra tools and information
+
+
+ **Accessibility Tools**:
+While working on tests, you may need a tool that helps you to view the element's accessibility data, e.g. for finding the button to click. For this purpose, you could use [AccessibilityInsights](https://accessibilityinsights.io/docs/windows/overview) 

src/common/UITestAutomation/Element/FindElementHelper.cs

@@ -51,7 +51,7 @@ public static T FindElement<T, TW>(Func<TW> findElementFunc, int timeoutInMillis
             return res == null ? null : new ReadOnlyCollection<T>((IList<T>)res);
         }
 
-        // Method to create a new element of type T
+        // Create a new element of type T
         public static T NewElement<T>(WindowsElement element, WindowsDriver<WindowsElement>? driver)
              where T : Element, new()
         {

src/modules/keyboardmanager/KeyboardManagerUITests/KeyboardManagerUITests.csproj

@@ -18,7 +18,6 @@
 
 	<ItemGroup>
 		<PackageReference Include="MSTest" />
-		<PackageReference Include="System.IO.Abstractions" />
 	</ItemGroup>
 
 	<ItemGroup>