From 5a444ff0195a5e7bf41a76756dbfd42e93ba9f14 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?S=C3=BCthe=C3=B6=20Istv=C3=A1n?= <91149030+sutheo17@users.noreply.github.com> Date: Sun, 19 May 2024 23:27:15 +0200 Subject: [PATCH] Update SonarCloud docuemantion's formatting --- doc/sonarcloud.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/doc/sonarcloud.md b/doc/sonarcloud.md index fed370b..d2c0856 100644 --- a/doc/sonarcloud.md +++ b/doc/sonarcloud.md @@ -1,18 +1,18 @@ -**SonarCloud documentation** +# SonarCloud documentation -*What is SonarCloud?* +### What is SonarCloud? SonarCloud is a cloud-based code analysis service designed to detect coding issues. The code is checked against an extensive set of rules that cover many attributes of code, such as maintainability, reliability, and security issues on each merge/pull request. SonarCloud completes the analysis loop to deliver clean code that meets high-quality standards. -*Why did we decide to add it?* +### Why did we decide to add it? Since we knew that it would be beneficial to check the existing code's quality, and also to analyze future code additions. -*How do you see the details / measures?* +### How do you see the details / measures? It also shows its result on the GitHub website, but you can also find the detailed facts on the SonarCloud website under https://sonarcloud.io/project/overview?id=BME-MIT-IET_iet-hf-2024-i01 -*What was the aftermath of adding SonarCloud?* +### What was the aftermath of adding SonarCloud? SC detected more than 40 high severity issues. It consisted of the following problems: @@ -28,9 +28,9 @@ SC detected more than 40 high severity issues. It consisted of the following pro So all of these issues have been fixed. It was pretty time-consuming to fix all of these, especially the function refactoring (to reduce method complexity). Also I have marked the existing problems as intentional on the SonarCloud webiste (e.g. a Logger class would be unnecessary to add in our case). -**Results:** +## Results: This tool proved to be useful not only by pointing out code-smells, but also identified security hotspots, gave us test code-coverage detailed data and its quality gates helped us with reviewing new code. All in all we started out with 370 active issues, and ended with just 187 issues (only 1/4 of this is medium, the other 3/4 are classified with small severity). -//to do add image!!! \ No newline at end of file +//to do add image!!!