Running the tests

The engine (PnP.Scanning) has a unit test project, PnP.Scanning.Core.Tests (xUnit). The tests are pure unit tests that run offline with no external dependencies.

Unit tests

From src/PnP.Scanning:

dotnet test PnP.Scanning.Core.Tests/PnP.Scanning.Core.Tests.csproj

For the classic pages assessment, the unit tests cover the pure sub-logic (wiki/HTML parsing, web part mapping, layout detection, home-page detection, usage-row parsing, the storage and CSV-export cores, etc.).

End-to-end validation

The SharePoint CSOM code paths that cannot be unit-tested in isolation — reading a page's web parts via the LimitedWebPartManager, reading Web.CanModernizeHomepage, and the page-usage search query — are validated by running an actual assessment against a test tenant with the CLI:

microsoft365-assessment.exe start --mode Classic --classicinclude Pages `
  --authmode application --tenant contoso.sharepoint.com `
  --applicationid <app-id> --certfile <path-to-cert.pfx> `
  --siteslist "https://contoso.sharepoint.com/sites/team"

microsoft365-assessment.exe report --id <assessment-id> --mode CsvOnly --path "c:\reports"

Inspect the exported classicpages.csv, classicpagewebparts.csv, classicwebpartunique.csv and the web/site summaries to confirm the assessment produced the expected data. See Run a classic pages assessment for the full set of options.