Related issues, PRs or discussions

N/A, sub issues to be created for each application

What is the current state of the codebase?

We only run system tests interacting Chrome and Notepad.
We don't run system tests checking how NVDA works with other popular applications.

Why are changes required?

Previously on AppVeyor we were running into a 60min time limit on builds, limiting our system test coverage.
We can now run system tests in parallel, allowing for more tests without as much of a build time increase.

Increased system test coverage for other applications will reduce the introduction of regressions.

What technical changes are required?

Create a simple smoke test for each application serves a base for the expansion of other system tests.
I think we can only consider using free software that is easy to install via GitHub actions for system tests.

I suggest we create system tests as PRs are opened related to the following applications.
We may also consider creating these smoke tests as part of the 64bit migration.

• Windows calculator
• Windows terminals
• Firefox
• VLC
• PoEdit
• LibreOffice
• Codium or VS code: Detect and report the status bar in Visual Studio Code #18724 (thanks @codeofdusk!), add VS code system tests and manual test plans #19208
• Thorium Reader
• Foobar2k
• Visual studio
• Thunderbird (this may be hard to configure for useful testing)

Are the proposed technical changes API breaking?

No

Are there potential risks or issues with the proposed implementation?

No