Table of Contents

Build and test

Per-repository commands

Repository Build Test
website dotnet build SPE.Website.sln npm test (Playwright; see the repository's README)
api dotnet build SPE.API.sln dotnet test
profiler dotnet build Reignite.Profiler.sln dotnet test Reignite.Profiler.sln
profiler.java mvn package mvn test
profiler.node npm install npm test
profiler.python — pytest
collect-sync dotnet build collect-sync.sln dotnet test
code-fix dotnet build PerformanceRefactorer.sln dotnet test
diagnostic-bot dotnet build DiagnosticBot.slnx dotnet test tests/DiagnosticBot.Tests/DiagnosticBot.Tests.csproj
teams-bot dotnet build TeamsBot.sln -c Release dotnet test tests/TeamsBot.Tests/TeamsBot.Tests.csproj -c Release
media-bridge dotnet build dotnet test
docs dotnet build Reignite.Docs.sln dotnet test and ./scripts/build.ps1

Use the solution or project file named in the repository's own README when it differs; the repository is the authority for its test command.

Documentation build

The docs repository has an extra gate: the generated pages must match the model.

# regenerate
dotnet run --project tools/Reignite.Docs.Generator -- `
  --model architecture/model.yaml --docs docs

# verify without writing (exit 2 on drift)
dotnet run --project tools/Reignite.Docs.Generator -- `
  --model architecture/model.yaml --docs docs --check

./scripts/build.ps1 runs the generator, DocFX, and the host publish. It fails if the model is invalid or if DocFX cannot resolve a page.

What "green" means

A change is ready when:

  1. The repository builds with no errors.
  2. Its tests pass.
  3. If the architecture changed, architecture/model.yaml is updated and the generated docs are committed.
  4. The docs build succeeds.

Do not treat a skipped test as a pass. If a test cannot run in your environment, say so in the pull request and explain why.

Test ownership

Each repository declares its own test command and its own tests.yaml in the workspace. Prefer the command the repository already publishes over a command invented in this page. For the website, the Playwright suite is the end-to-end authority; run it with the harness in scripts/run-e2e.cjs so it allocates the origin the app should serve.