cesnimda/jobtrackingapp
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

fix(ci): actually run the backend test suite
CI and Deploy / test (push) Failing after 1m3s
Details
CI and Deploy / deploy (push) Has been skipped
Details

Browse Source 
The build step only builds JobTrackerApi, so the test project was never
compiled — and `dotnet test --no-build` then made the step a ~1s no-op
(locally it errors "test source file not found"; on the persistent
self-hosted runner it can silently run a stale binary). The 306 backend
tests have not been gating CI.

Drop --no-build so the test project is compiled and the suite runs.
Verified locally: 306 passed in 14s instead of "succeeding" in 1s.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
cesnimda
2026-07-18 20:47:44 +02:00
parent 1430313a20
commit cfba7fbbc4
1 changed files with 4 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.gitea/workflows/ci-deploy.yml
+4 -1
View File
@@ -40,8 +40,11 @@ jobs:
- name: Build backend - name: Build backend
run: dotnet build JobTrackerApi/JobTrackerApi.csproj --configuration Release run: dotnet build JobTrackerApi/JobTrackerApi.csproj --configuration Release
# No --no-build: the build step above only builds JobTrackerApi, so the test project was never
# compiled and `--no-build` made this step a ~1s no-op (or ran a stale binary left on the
# self-hosted runner). The backend suite was therefore not actually gating CI.
- name: Test backend - name: Test backend
run: dotnet test JobTrackerApi.Tests/JobTrackerApi.Tests.csproj --configuration Release --no-build run: dotnet test JobTrackerApi.Tests/JobTrackerApi.Tests.csproj --configuration Release
- name: Install frontend deps - name: Install frontend deps
working-directory: job-tracker-ui working-directory: job-tracker-ui