Tests needed for ReadKeyAsync changes

[SeeminglyScience]

Opening this issue as a reminder that tests need to be created for the changes to our internal ReadKeyAsync method. From PR #592

[TylerLeonhardt]

:) thanks!

[WernerMairl]

hi
i'm one of the issuer, now ready for a retest on Ubuntu...
where i can download/install the latest master build (assuming that the fix is merged) ?

i have found the following:

https://travis-ci.org/PowerShell/vscode-powershell/builds/333064180
but not able to find/download build output artifacts....

regards
Werner

[SeeminglyScience]

@WernerMairl this issue is about writing automated tests, but we'd love for you to try it out as well :)

1. Grab the build from AppVeyor here. Note that this archive was built on Windows, some compression utilities won't automatically translate the Windows directory separators to Linux. Ubuntu should though.

2. In the integrated console, type ii ((gmo PowerShellEditorServices.Commands).ModuleBase|Split-Path). That should open the PSES folder within the extension in your file explorer.

3. Make sure all instances of VSCode are closed

4. Copy the contents of the PowerShellEditorServices folder from the zip into the window opened in step 2

5. If you get access denied errors, try running gps pwsh|? id -ne $pid|spps in a separate PowerShell window

Note: The changes in their current state could prevent the CPU from entering low power mode if you leave VSCode open. That'll be fixed before this releases.