[Arthurvdv]

Summary

The scheduled build is green although two net10.0 test legs (Test v16.10.44.19458, Test v17.10.44.19457) compile none of the cop test projects.

Root cause: the CI compile floor for net10.0 moved down to SDK 16.10.44.19458 when Microsoft published net10.0 VSIX builds for older AL majors (2026-10-18). ALCops.RoslynTestKit 1.5.0 references 18.0.41.39415, so every leg with an SDK below that fails with CS1705. Every Run *.Test step was continue-on-error, which hid the compile error: no trx, nothing reported, job green.

This PR:

• builds each test project in its own step without continue-on-error, then runs dotnet test --no-build (still continue-on-error) so a compile error fails the job while test failures still let every cop x AL version report;
• bumps ALCops.RoslynTestKit to 1.5.1 (net10.0 lib compiled against 16.10.44.19458, the lowest marketplace net10.0 release);
• pins the local net10.0 SDK in .vscode/Setup-BCDevTools.ps1 to the same 16.10 floor, and updates the rules docs.

Commits

1. fix(ci): fail the test job when a test project does not compile - the CI gate and docs. Pushed first on purpose: its run is the failing-first proof of the gate.
2. chore: bump RoslynTestKit to 1.5.1 and pin the local net10.0 SDK to the 16.10 floor - the fix.
3. chore(ci): name the build steps in the no-trx error and keep the floor doc to current state - review follow-up.

Developers

Re-run .vscode/Setup-BCDevTools.ps1 so the local net10.0 SDK matches the 16.10 floor.

Test plan

• Locally with RoslynTestKit 1.5.0 against SDK 16.10.44.19458: dotnet test ALCops.sln fails with CS1705
• Run of commit 1 (39409566734): Test v16.10.44.19458 and Test v17.10.44.19457 fail at Build ALCops.ApplicationCop.Test with CS1705, all other legs green, merge/report steps still run
• Locally with RoslynTestKit 1.5.1: dotnet test ALCops.sln passes
• Run of commit 2 (39410728615): all legs green, seven Build ALCops.*.Test steps per leg, no CS1705, "Test results" check green
• Run of commit 3 green

Review notes

• A hard Build step skips the later cops on that leg: deliberate. A compile error must fail the job at its own step; the other legs plus merge and report still run (run 39409566734), and compile failures are systemic (same SDK), so skipped cops carry no extra signal.
• Download/Restore are soft but Build is hard: not a regression. A restore failure made the leg useless before as well; it used to surface later via the missing-trx check.
• The NuGet branch of Setup-BCDevTools.ps1 is unused but kept, so the pin can move back to a NuGet source when the floor does.
• The seven repeated step blocks are the pre-existing layout and out of scope.

🤖 Generated with Claude Code