Does Karma resolve a relative basePath against the config file or the CI working directory?
One config file, two effective roots A shared karma.conf.js is expected to drive both local watch runs and CI single runs; assume Karma 6.x. Karma's documented rule is that a relative basePath resolves against the location of the configuration file itself. Pipelines that generate the config into a temporary directory, wrap it in a build tool, or launch the r
karma