QA and Test Coverage

Current quality gates, automated test stages, and where to read coverage and execution reports in local and CI environments.

QA strategy overview

CI entrypoint: .github/workflows/ci-pipeline.yml.
Pipeline includes static quality analysis, unit tests, integration tests, security scans, and functional tests.
Most test jobs are configured with continue-on-error: true so the dashboard always collects evidence and artifacts for review.

Unit test coverage scope

Layer	Current unit test scope	Coverage output
`backend`	Unit tests are filtered using `FullyQualifiedName~.UnitTests.` and currently focus on service-level scenarios in `TuCreditoOnline.Tests/UnitTests/Services`.	Coverage is collected in Cobertura format and transformed into HTML via ReportGenerator.
`frontend`	Jest + React Testing Library tests under `frontend/src/**/__tests__`, currently including wizard flow and credit calculator hooks.	Jest coverage is generated with `--coverage` and exported as part of the unit test job artifacts/reports.

How to run tests locally

Target	Command
Frontend unit tests	`cd frontend && npm test`
Frontend coverage	`cd frontend && npm run test:coverage`
Backend unit tests	`cd backend && dotnet test tests/TuCreditoOnline.Tests/TuCreditoOnline.Tests.csproj --filter "FullyQualifiedName~.UnitTests."`
Backend integration tests	`cd backend && dotnet test TuCreditoOnline.sln --filter "FullyQualifiedName~.IntegrationTests."`

CI report outputs

backend-unit-test-report: backend unit summary, detailed HTML report, and coverage report files.
frontend-unit-test-report: frontend unit summary and detailed HTML report generated from Jest JUnit results.
integration-test-report: integration execution logs and TRX output.
security-test-report: OWASP ZAP baseline and API scan outputs.
functional-report: Applied AI Aura functional evidence and report artifacts.

The CI dashboard comment on each pull request links to live report previews (Surge) when publishing succeeds; otherwise, artifacts remain the source of truth.

Coverage interpretation notes

Coverage is measured and published, but there is currently no hard repository-level minimum threshold configured in CI.
Backend coverage focuses on line and branch coverage from Cobertura exports.
Frontend unit reports emphasize pass/fail and suite trends; raw Jest coverage output remains available in pipeline artifacts.
Quality gate checks for backend and frontend are provided through SonarQube when project access tokens are correctly configured.