admin管理员组文章数量:1336663
I have a project to analyze which is only based on Angular framework. The main issue I have is that both source and test files are on the same directories, divided into features.
Here is an example of my structure:
+- client
| +- features
| | +- home
| | | +- home.js [source code]
| | +- home.spec.js [test code]
| +- home.html
| +- home.less
+- admin
| +- admin.js [source code]
| +- admin.spec.js [test code]
| +- admin.html
| +- admin.less
...
In my sonar-project.properties
, it seems impossible to set a pattern instead of a path (for ex. sonar.tests=client/**/*.spec.js
).
Is there a way to run an analysis with this kind of structure?
Thanks.
I have a project to analyze which is only based on Angular framework. The main issue I have is that both source and test files are on the same directories, divided into features.
Here is an example of my structure:
+- client
| +- features
| | +- home
| | | +- home.js [source code]
| | +- home.spec.js [test code]
| +- home.html
| +- home.less
+- admin
| +- admin.js [source code]
| +- admin.spec.js [test code]
| +- admin.html
| +- admin.less
...
In my sonar-project.properties
, it seems impossible to set a pattern instead of a path (for ex. sonar.tests=client/**/*.spec.js
).
Is there a way to run an analysis with this kind of structure?
Thanks.
Share Improve this question asked Mar 17, 2015 at 14:08 Romain LinsolasRomain Linsolas 81.7k52 gold badges205 silver badges276 bronze badges1 Answer
Reset to default 11Thanks to SonarQube mailing list, the solution is to set the following properties:
sonar.sources=client
sonar.tests=client
sonar.exclusions=**/*.spec.js
sonar.test.inclusions=**/*.spec.js
本文标签:
版权声明:本文标题:javascript - How to analyze with SonarQube a project where sources and tests are in the same directories - Stack Overflow 内容由网友自发贡献,该文观点仅代表作者本人, 转载请联系作者并注明出处:http://www.betaflare.com/web/1742272293a2444534.html, 本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌抄袭侵权/违法违规的内容,一经查实,本站将立刻删除。
发表评论