We have quite a large project where and tend to apply risk based approach to stringency of unit tests and code reviews. E.g. components classified as A need to have higher coverage than components classified as B. However, it is nearly impossible without a support of static analyser - is there a way how to instruct (e.g. Sonar) to apply different rules on different modules? Is that approach feasible, how to otherwise deal with complex projects with parts that are subject to different quality requirements?
1 Answer
The only way to archive that is to create good architecture. Then you can partition your software into components. For example, in C and C++, one component can be a library. Then in tools like sonar and jenkins, you can checkout just specific components, and do with them whatever you like.
-
1The question indicates that there are already components ("components classified as A need [...]"). Maybe the same term is used for different things? Moreover, having creating multiple builds just to be able to enforce different coverage levels seem like an overkill (although I don't have anything constructive to suggest instead). May 31, 2016 at 13:08