Link to issue number:

Part of #17878

Summary of the issue:

System tests are the slowest part of the GitHub actions build, taking about 20min.
System tests could be split up to speed up the build, run in parallel via a matrix.

Description of user facing changes:

None

Description of developer facing changes:

• System tests speed will reduce by 3min.
• System test suite results will be created separately.
• Install logs will be in the same artifact as the rest of each system test suites results.

Description of development approach:

Use a matrix and env variable to set the system test suite up to run test suites simultaneously across runners.

Testing strategy:

This PRs GitHub actions CI/CD results.

Tested a failure using known failing tests: https://github.com/nvaccess/nvda/actions/runs/15410983376.
When this test suite failed, other tests continued on running as intended. i.e. one test failure still allows the rest of the tests to complete for reporting, but doesn't pass the build.

Known issues with pull request:

Ideally we should split up the chrome testing suite into logical subgroups.
We could save about 10min/build splitting it into 4+ groups.
Then we can parallelize more of the chrome tests.
This should be considered in a different issue/PR.

More documentation may be needed in tests/system/readme.md. Any suggestions on what to add?

Code Review Checklist:

• Documentation:
  • Change log entry
  • User Documentation
  • Developer / Technical Documentation
  • Context sensitive help for GUI changes
• Testing:
  • Unit tests
  • System (end to end) tests
  • Manual testing
• UX of all users considered:
  • Speech
  • Braille
  • Low Vision
  • Different web browsers
  • Localization in other languages / culture than English
• API is compatible with existing add-ons.
• Security precautions taken.

@coderabbitai summary