Use this during code reviews to see if there are bugs in the code we are reviewing.Ĭode view indicates test coverage with color-coded green and red stripes. Project code viewĬlicking on "Code" from any project view lets you drill in by folder to see any file of code. You can also catch these same issues in real time while code is written in IntelliJ using SonarLint (see below). It is based on the Sonar philosophy of Fixing the Water Leak.Ĭlicking any of the links (on the bug count, code small count, etc) takes you to a specific list of the bugs/issues and shows where they happen in the source code. We can focus on fixing the issues as we introduce them. That allows us to focus on what has gotten worse or better most recently, like over the course of a sprint. The 'Leak Period' shows how these statistics have changed in the last period, currently set to 14 days. this one for the OpenLMIS v3 Fulfillment service) show specific metrics and trends: It allows you to click to drill in to find coverage gaps. The homepage also has a 'tree map' showing color-coded unit test coverage statistics. The project links take you to the project overview showing specific issues tracked over time for that project (see below). Start at the OpenLMIS SonarQube homepage: In addition, Sonar also tracks test coverage and complexity, thereby serving as a tool to look broadly at code quality. OpenLMIS has its own SonarQube server and recommends that developers use the SonarLint IntelliJ plug-in as a comprehensive way to track and improve code quality over time. The Sonar configuration is aligned with the OpenLMIS OpenLMIS Coding Standards including the v3 Service Style Guide.
0 Comments
Leave a Reply. |