What problem does it solve?
Writing integration tests for .NET Static Web Assets requires knowing which test asset to reuse, which base class to inherit, which manifest to assert on, and how to modify projects at runtime without corrupting shared test assets. This Skill codifies that workflow so tests cover the full asset pipeline correctly.
Core Features & Use Cases
- Test Asset Selection: A catalog of existing test projects (RazorComponentApp, RazorAppWithP2PReference, AssetGroupsSample, BlazorHosted, and more) mapped to features like scoped CSS, fingerprinting, compression, and asset groups.
- Base Class Guidance: Chooses between AspNetSdkTest, AspNetSdkBaselineTest, and IsolatedNuGetPackageFolderAspNetSdkBaselineTest based on whether the test builds, publishes, packs, or compares baselines.
- Manifest Assertion Patterns: Explains when to assert on staticwebassets.build.json versus the endpoints or publish manifests, including compressed asset variants and content-negotiated endpoints.
- Use Case: When adding a feature that excludes certain static assets, the Skill directs you to verify the build manifest still contains the assets while the endpoints manifest shows zero matching endpoints.
Quick Start
Write a new Static Web Assets integration test that publishes a Razor class library through a P2P reference and asserts the compressed endpoints appear in the endpoints manifest.