Choosing between browserNoActivityTimeout and captureTimeout for CI flake reduction
Karma's browserNoActivityTimeout and captureTimeout both govern how long the runner waits before treating a browser as unresponsive, yet they trigger at different stages of the test lifecycle. A CI pipeline needs deterministic job termination without failing legitimate slow tests, but the two settings interact in ways the documentation does not fully disambi
karma