GPII-1898: Merge 'upstream/master' into GPII-1898

* upstream/master:
  GPII-1108: Merged up with master
  GPII-1540: Fixed indentation.
  GPII-1540: Make test-window.exe build automatically
  GPII-1540: Removed the test application executable
  GPII-1540: Flipped options.force to option.cleanOnly. Off by default feels better.
  GPII-1540: Unit tests for closeProcessByName always pass Waiting for process start sometimes triggers just before the window is created.
  GPII-1540: Unit tests for closeProcessByName Created test-window, a dummy application that creates a window for testing.
  GPII-1540: rollback; Put findProcessByName back to how it was. It turned out to be better to enumerate the windows, rather than enumerate every thread.
  GPII-1540: Made the process enumeration in findProcessByName re-usable. Refactored it out into eachProcess, in preparation for a "get the windows of each process" routine.
  GPII-1540: Merge from master
  GPII-1540: Implemented closeProcessByName. Terminate a process less aggressively.
  GPII-1828: Allows for retrieval of updated env vars
  GPII-1108: Fixed logic for allowing deletion of subkeys of nonexistent parents in the registry to be a noop

Author: javihernandez

.gitignore

@@ -1,2 +1,3 @@
 /node_modules/
 .vagrant
+**/test/*.exe

README.md

@@ -25,12 +25,14 @@ It is possible to provision a Windows VM for testing purposes. Please ensure you
 
 If this is your first time creating this VM an 8 GB download will take place. The downloaded image will be valid for 90 days after which the Windows installation will no longer be useable. To remove an expired image you can use the ``vagrant box remove "inclusivedesign/windows10-eval"`` command.
 
-Once the VM has finished booting up you will need to type the ``vagrant reload`` command to cause it to restart. This is required so changes made to the Windows VM's ``PATH`` environment variable as part of the provisioning process are available in terminal sessions. This step is a temporary workaround and will be removed in the near future. 
-
 Now you can open a command prompt window and use the following commands to test the framework:
 
 ```
+refreshenv
 cd c:\vagrant
 node tests\UnitTests.js
 node tests\AcceptanceTests.js builtIn
 ```
+
+*Note:* The [refreshenv](https://github.com/chocolatey/chocolatey/blob/a09e15896fbc5e790b17b6699cd6b50bc7eb14e4/src/redirects/RefreshEnv.cmd) command only needs to be used if you are about to issue commands after having just created the VM. If the VM has been restarted since its creation then the command is not required.
+