Add QuickStart section to README.md (#41)

* Update README.md

* Fixed review comments

* Fix typos and wrong verb forms

README.md

@@ -13,5 +13,102 @@ Most of performed methods are logged using NLog, so you can easily see a history
 
 We use interfaces where is possible, so you can implement your own version of target interface with no need to rewrite other classes.
 
+### Quick start
+
+1. To start work with this package, simply add the nuget dependency Aquality.WinAppDriver to your project.
+
+2. Configure path to your application executable at settings.json:
+ - Create a `Resources` folder in your project and copy [settings.json](Aquality.WinAppDriver/src/Aquality.WinAppDriver/Resources/settings.json) into it. 
+ - Select `Copy to Output Directory`: `Copy always` option at settings.json file properties.
+ - Open settings.json and find `applicationPath` option under the `driverSettings` section. Replace the value with the path to your app.
+
+3. Ensure that [WinAppDriver](https://github.com/microsoft/WinAppDriver) is set up at your machine where the code would be executed.
+
+4. Start WinAppDriver service before your code execution. There are several options to do this:
+ - Start WinAppDriver.exe via external tool or command (e.g. manually with cmd/PS from the installation directory; via [task for you CI](https://marketplace.visualstudio.com/items?itemName=WinAppDriver.winappdriver-pipelines-task) )
+ - Start WinAppDriver automatically via AppiumLocalService - this option is integrated in our package, just set `"isRemote"` to `false` at your settings.json. This option requires specific version of node.js to be preinstalled on your machine (Please read more [here](http://appium.io/docs/en/contributing-to-appium/appium-from-source/#nodejs) and [here](https://github.com/appium/appium-dotnet-driver/wiki/How-to-start-an-AppiumDriver-locally)).
+ - Start WinAppDriver.exe manually calling the method `AqualityServices.WinAppDriverLauncher.StartWinAppDriverIfRequired();` from your code.
+
+5. (optional) Launch an application directly by calling `AqualityServices.Application.Launch();`. 
+
+> Note: 
+If you don't start an Application directly, it would be started with the first call of any Aquality service or class requiring interacting with the Application.
+
+6. That's it! Now you are able work with Application via AqualityServices or via element services.
+```csharp
+
+ AqualityServices.Application.MouseActions.Click();
+ AqualityServices.Application.KeyboardActions.SendKeysWithKeyHold("n", ModifierKey.Control);
+```
+
+7. To interact with Application's windows, forms and elements, we recommend following the PageObjects pattern. This approach is fully integrated into our package.
+To start with that, you will need to create a separate class for each window/form of your application, and inherit this class from the [Window](Aquality.WinAppDriver/src/Aquality.WinAppDriver/Forms/Window.cs) or [Form](Aquality.WinAppDriver/src/Aquality.WinAppDriver/Forms/Form.cs) respectively. 
+
+
+> Note: 
+> - By "Form" we mean part of the main window of your application (by default) or part of the any other window (specified as a constructor parameter). An example of form is a MenuBar or some section.
+> - By "Window" we mean the separate window of your application (would be searched from the [RootSession](https://github.com/microsoft/WinAppDriver/wiki/Frequently-Asked-Questions#when-and-how-to-create-a-desktop-session) by default). In other words, the "Window" is a form which is separate from the main application window. There are several cases where you should use Window class instead of Form:
+>   - Your application consists of several Windows;
+>   - You need to interact with more than one application;
+>   - You need to perform actions before/after the main application run (e.g. reinstall, update).
+
+8. From the PageObject perspective, each Form consists of elements on it (e.g. Buttons, TextBox, Labels and so on). 
+To interact with elements, on your form class create fields of type IButton, ITextBox, ILabel, and initialize them using the ElementFactory. Created elements have a various methods to interact with them. We recommend combining actions into a business-level methods:
+
+```csharp
+
+using Aquality.Selenium.Core.Configurations;
+using Aquality.WinAppDriver.Applications;
+using Aquality.WinAppDriver.Elements.Interfaces;
+using Aquality.WinAppDriver.Forms;
+using OpenQA.Selenium;
+using OpenQA.Selenium.Appium;
+
+namespace CalcApp.Forms
+{
+    public class CalculatorForm : Form
+    {
+        private readonly ITextBox LeftArgumentTextBox;
+        private readonly IButton OneButton;
+        private readonly IButton TwoButton;
+        private readonly IButton PlusButton;
+        private readonly IButton EqualsButton;
+        private readonly ILabel ResultsLabel;
+
+        public CalculatorForm() : base(By.Name("Day Maxi Calc  v.1.5 Freeware"), "Calculator")
+        {
+            LeftArgumentTextBox = ElementFactory.GetTextBox(MobileBy.AccessibilityId("50"), "Left Argument");
+            OneButton = ElementFactory.GetButton(By.Name("1"), "1");
+            TwoButton = RelativeElementFactory.GetButton(By.Name("2"), "2");
+            PlusButton = ElementFactory.FindChildElement<IButton>(this, By.Name("+"), "+");
+            EqualsButton = FindChildElement<IButton>(By.Name("="), "=");
+            ResultsLabel = ElementFactory.GetLabel(By.XPath("//*[@AutomationId='48']"), "Results bar");
+        }
+
+        private ITimeoutConfiguration TimeoutConfiguration => AqualityServices.Get<ITimeoutConfiguration>();
+
+        public int CountOnePlusTwo()
+        {
+            const string expectedRightArgument = "1";
+            OneButton.Click();
+            ConditionalWait.WaitForTrue(() => LeftArgumentTextBox.Value == expectedRightArgument, 
+                timeout: TimeoutConfiguration.Condition,
+                message: $"Right argument should become '{expectedRightArgument}' after click on {OneButton.Name}");
+
+            PlusButton.MouseActions.DoubleClick();
+            TwoButton.MouseActions.Click();
+            EqualsButton.State.WaitForClickable();
+            EqualsButton.Click();
+            return int.Parse(ResultsLabel.Text);
+        }
+    }
+}
+```
+
+
+
+Please take a look at more examples in our tests at https://github.com/aquality-automation/aquality-winappdriver-dotnet/tree/master/Aquality.WinAppDriver/tests/Aquality.WinAppDriver.Tests/Forms.
+
+
 ### License
 Library's source code is made available under the [Apache 2.0 license](https://github.com/aquality-automation/aquality-winappdriver-dotnet/blob/master/LICENSE).