Focus chrome after starting in system tests

[seanbudd]

Link to issue number:

None

Summary of the issue:

As discussed in #12293, our systems fail randomly. Usually this is due to another window stealing focus, such as the taskbar or Docker. As system tests are run locally, we shouldn't be killing these processes.

Description of how this pull request fixes the issue:

• Use windows API to make the chrome window gain focus
• Adds logging that lists the foreground window and open windows if chrome doesn't gain focus
• Removes extra sleep time after starting NVDA

Testing strategy:

Run the system tests locally, and prevent chrome from gaining focus by holding alt+tab

Here's an example log from a local test:

checkbox labelled by inner element :: A checkbox labelled by an in... | FAIL |
Unable to focus Chrome.
Foreground Window: speechSpyGlobalPlugin.py (Working Tree) - nvda - Visual Studio Code.
Open Windows: ['speechSpyGlobalPlugin.py (Working Tree) - nvda - Visual Studio Code', 'NVDA Browser Test Case - Google Chrome', 'C:\\nvda\\testOutput\\system', 'Calculator', 'Calculator', 'Settings', 'Settings', 'Microsoft Text Input Application', 'Program Manager']

Known issues with pull request:

None

Change log entries:

None

Code Review Checklist:

• Pull Request description is up to date.
• Unit tests.
• System (end to end) tests.
• Manual tests.
• User Documentation.
• Change log entry.
• Context sensitive help for GUI changes.

[michaelDCurran]

It may be an idea to add some kind of per-test unique value to testCaseTitle, because at the moment it is just "NVDA Browser Test Case". There is a small possibility the code could focus the wrong Chrome window, if one happened to be left arrround.

[AppVeyorBot]

• System test failure
• Build (for testing PR)

See test results for failed build of commit 4d87770046

[AppVeyorBot]

• System test failure
• Build (for testing PR)

See test results for failed build of commit b858e98797

I've changed hash -> abs(hash()) and changed the filter for the window search