Now you need to config the tests: Enabling the coverage testing, you could disable abort on error check of code with critics issues, because these errors you would analyze it from SonarQube Dashboard, and don't forget add your jacoco reports.
Wait for a bit moment while it will be finishing the tasks.
5. Export Metrics
Run Gradle task
On sonar dashboard you could go over your projects, issues, rules, quality metrics, and more engineering features If all components works well, execute a test task, and send it with exportTestResultToSonarqube task:
./gradlew exportTestResultToSonarqube
Confirm message:
6. View Your Metrics
On dashboard, you have a analyzed new project
Into the project, Look four metric: count of bug, security vulnerabilities, percentage of testing coverage, and percentage of duplicate codes:
You could verificate the id project in url on web browser:
On Sonarqube project dashboard, thats look like:
7. Stop SonarQube Server
Finally, if you need to stop sonar service, run the sentence:
sh sonar.sh stop
8. License
by Romell DomÃnguez
Copyright 2018 Romell D.Z.
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and limitations under the License.