SonarQube Dashboard
🧩 SonarQube Dashboard
এটাই engineers সবচেয়ে বেশি use করে।
✅ Project
একটা project = একটা repo।
Example:
Sure Pay API
Event Flow Backend
✅ Analysis
প্রতিবার scan = নতুন analysis।
মানে:
analysis history
✅ Issue
Detected problem।
Issue Types
🔴 Bug
Future crash risk।
Example:
a = 10 / 0
🟠 Vulnerability
Security problem।
Example:
SQL injection
weak encryption
hardcoded password
🟡 Code Smell
Code কাজ করছে কিন্তু professional না।
Example:
if active == True:
Better:
if active:
✅ Severity
Problem কত dangerous।
| Level | Meaning |
|---|---|
| Blocker | System break করবে |
| Critical | High risk |
| Major | Important |
| Minor | Small |
| Info | Suggestion |
✅ Quality Gate
Project pass/fail decision।
Example rule:
No critical bug
Coverage > 80%
Result:
✅ Passed → Merge Allowed
❌ Failed → Fix Needed
✅ Coverage
Test কত percent code check করেছে।
Example:
Coverage: 45%
মানে:
👉 55% code untested 😬
✅ Code Smell Count
Bad design কত আছে।
✅ Technical Debt
Bad code fix করতে কত সময় লাগবে।
Example:
Technical Debt: 2h
✅ Duplication
Same code কতবার লেখা হয়েছে।
Bad practice।
✅ Maintainability Rating
Code future এ maintain করা কত easy।
| Grade | Meaning |
|---|---|
| A | Excellent |
| B | Good |
| C | OK |
| D | Bad |
| E | Dangerous |
✅ Reliability Rating
Bug risk level।
✅ Security Rating
Security strength।
✅ Security Hotspot
Security sensitive code।
Example:
login
file upload
encryption
Manual review দরকার।
🔥 Real Example (Full Flow)
ধরো তুমি backend বানাও।
Developer Code Push
git push
CI/CD Start
GitHub Action run
SonarQube Scan
sonar-scanner
Report
Bug: 2
Vulnerability: 1
Coverage: 62%
Quality Gate
FAILED ❌
Developer Fix
Bug remove → coverage add → pass ✅
⭐ Engineer Mindset
Professional developer mindset:
Write Code
→ Test
→ SonarQube Check
→ Merge