Karma captureTimeout and browserNoActivityTimeout limits in singleRun mode

Goal

Configure Karma to stop a single-run CI execution when a captured browser stops responding, rather than leaving the run pending indefinitely.

Constraints

captureTimeout governs how long Karma waits for a browser to connect before aborting. browserNoActivityTimeout defines the inactivity window after capture, after which Karma treats the browser as unresponsive and fails the run. Karma does not automatically restart the browser, and disconnect recovery behavior varies by launcher plugin. Default windows may be too short where headless browser startup is slow. This assumes Karma 6.x with a pinned launcher plugin and browser binary.

Questions

• Does browserNoActivityTimeout apply after successful capture in singleRun mode?
• Can captureTimeout and browserNoActivityTimeout be set independently per browser in karma.conf.js?
• What happens to pending test results when browserNoActivityTimeout elapses before completion?