build-and-test

name	build-and-test
description	Procedures for restoring packages, compiling Screenbox and Screenbox.Core, running automated unit tests, and verifying XAML formatting. Use when the user asks to build projects, run tests, or verify code changes.

Build and Test Runbook

Follow these structured procedures when restoring, compiling, testing, or validating formatting in the Screenbox solution.

---

1. Prerequisites & Package Restore

Ensure local dotnet tools and NuGet packages are restored before building:

Restore Dotnet Tools (XAML Styler & LottieGen)

dotnet tool restore

Restore NuGet Packages

For the full solution:

msbuild Screenbox.slnx -t:restore -p:Platform=x64 -p:Configuration=Debug

Or restore the main UWP app project individually:

msbuild Screenbox/Screenbox.csproj /p:Configuration=Debug /p:Platform=x64 /t:Restore /m

---

2. Compilation / Build

Target the system platform for local development. For example, to build the main UWP app in Debug mode on the x64 platform:

msbuild Screenbox/Screenbox.csproj /p:Configuration=Debug /p:Platform=x64 /t:Build /m

---

3. Running Automated Tests

Run Full Test Suite

dotnet test Screenbox.Core.Tests/Screenbox.Core.Tests.csproj -v minimal

Testing Rules & Constraints

• Pure Logic Tests: Use [TestMethod] in Screenbox.Core.Tests.
• XAML-Dependent Tests: NEVER use plain test runners for tests that instantiate XAML types. Use the UWP Unit Test App runner with [UITestMethod].
• No Boilerplate Comments: Do not emit // Arrange, // Act, // Assert comments.
• Naming Style: Mirror existing test method naming in nearby test classes.

---

4. XAML Formatting & Lint Verification

Verify all XAML files adhere to XAML Styler rules:

pwsh ./scripts/lint-xaml.ps1

To format specific modified XAML files manually:

dotnet tool run xstyler -f Screenbox/Pages/PlayerPage.xaml