karma-sonarqube-unit-reporter
karma-sonarqube-unit-reporter copied to clipboard
A Karma plugin. Unit tests execution report for SonarQube/Generic Coverage Plugin
Adds a silent mode. When silentMode is true, it skips the logging when mapping describe blocks to filenames. SilentMode defaults to false so existing users should not see a change.
Bumps [eslint-utils](https://github.com/mysticatea/eslint-utils) from 1.4.0 to 1.4.3. Commits - [`23f4ddc`](https://github.com/mysticatea/eslint-utils/commit/23f4ddc58eda5e6aec3d6a43c6266acbe19345cd) 🔖 1.4.3 - [`8f9e481`](https://github.com/mysticatea/eslint-utils/commit/8f9e481ecc1204c7a1331b697f97903f90c75154) 🐛 fix reference tracker false positive - [`6633278`](https://github.com/mysticatea/eslint-utils/commit/663327835abfb1f62fc6fc5d69028457e11b5f80) ⚒ fix test scripts - [`7c8e67c`](https://github.com/mysticatea/eslint-utils/commit/7c8e67c22f7222685a6a9154ba5eec2ac4896a3e) ⚒ fix build...
report.xml ` ` generated path doesnt point to test.
I have a project in which `karma-sonarqube-unit-reporter` is a dev dependency. When executing the command `yarn audit` it reports a vulnerability due to this package. I believe this would also...
Our current project has a requirement to have spec files in both `spec.js` and `spec.ts` format. But current plugin doesn't have option to specify multiple file types and raising exceptions....
If we use karma parallel plugin, karma-sonarqube-unit-reporter picks the very first report(I was using 4 browsers concurrently- headlesschrome) and leave the other browsers test report
12 09 2018 17:50:06.534:ERROR [config]: Invalid config file! Error: Cannot find module './gulp/conf' at Function.Module._resolveFilename (module.js:547:15) at Function.Module._load (module.js:474:25) at Module.require (module.js:596:17) at require (internal/module.js:11:18) at Object. (C:\Users\junior.paulo\workspace\repositories\Javascript\protheus-tface\karma.conf.js:6:12) at Module._compile...
This is one possible way to add test file paths relative to `basePath`, to make it consistent and not break backwards compatibility of `testPaths` and `testFilePattern`. Note that I'm not...
Seems like there's a problem with a parameter for filenameFormatter function which you can set using the configuration. So in index.js line 128 you have this call - nextPath =...