Improve test coverage and SonarQube quality gate readiness

[5000user5000]

Summary

This PR improves frontend/backend test coverage readiness and SonarQube Quality Gate stability for the project.

Key updates:

• added and refined frontend tests for important user-facing flows
• added backend service-level test coverage for core configuration/change/version/export behavior
• aligned frontend and backend coverage reports with SonarQube scan inputs
• resolved SonarQube new violations that caused standalone frontend/backend Quality Gates to fail
• documented the canonical root SonarQube scan workflow in the README and docs

Quality / SonarQube

The canonical SonarQube project is the root aggregate project:

• cloud-native

Standalone projects were also checked:

• cloud-native-frontend
• cloud-native-backend

Current local Quality Gate status:

• cloud-native: OK
• cloud-native-frontend: OK
• cloud-native-backend: OK

The expected scan flow is:

cd frontend
npm run test:coverage

cd ../backend
mvn clean verify

cd ..
npx @sonar/scan \
  -Dsonar.host.url=http://localhost:9000 \
  -Dsonar.token=$SONAR_TOKEN

Verification

• Frontend targeted tests passed
• Backend targeted tests passed
• SonarQube Quality Gate passed for root aggregate project
• SonarQube Quality Gate passed for frontend/backend standalone projects

Notes

• SonarQube tokens are not committed and should be provided through environment variables or CI secrets.
• Coverage exclusions are documented as conservative exclusions for bootstrap, data, framework wiring, DTO/repository/controller, enum, and prototype/demo files.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
cloud-native	Ready	Preview, Comment	May 29, 2026 12:28am