From cfba7fbbc451313c4b12e1c009ef3b293ef2adfa Mon Sep 17 00:00:00 2001 From: cesnimda Date: Sat, 18 Jul 2026 20:47:44 +0200 Subject: [PATCH] fix(ci): actually run the backend test suite MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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 --- .gitea/workflows/ci-deploy.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/.gitea/workflows/ci-deploy.yml b/.gitea/workflows/ci-deploy.yml index 94508ae..462e760 100644 --- a/.gitea/workflows/ci-deploy.yml +++ b/.gitea/workflows/ci-deploy.yml @@ -40,8 +40,11 @@ jobs: - name: Build backend 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 - 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 working-directory: job-tracker-ui