[ASM Test] Add IIS CI coverage for WebApi null-action ASM test#8597
Conversation
Snapshots difference summaryThe following differences have been observed in committed snapshots. It is meant to help the reviewer. 16 occurrences of : + component: aspnet,
|
BenchmarksBenchmark execution time: 2026-05-11 11:18:41 Comparing candidate commit 76bdfa9 in PR branch Some scenarios are present only in baseline or only in candidate runs. If you didn't create or remove some scenarios in your branch, this maybe a sign of crashed benchmarks 💥💥💥 Scenarios present only in baseline:
Found 3 performance improvements and 5 performance regressions! Performance is the same for 50 metrics, 14 unstable metrics, 87 known flaky benchmarks, 39 flaky benchmarks without significant changes.
|
| } | ||
|
|
||
| [SkippableFact] | ||
| [Trait("RunOnWindows", "True")] |
There was a problem hiding this comment.
Other tests in this file have [Trait("Category", "EndToEnd")], probably it's worth adding it for consistency even though I am not sure if it's used
## Summary of changes - Mark the WebApi null-action ASM IIS test with the EndToEnd category trait. ## Reason for change - Keeps the test metadata consistent with the neighboring WebApi IIS tests added by #8597. ## Implementation details - Adds only the missing `[Trait("Category", "EndToEnd")]` attribute to `TestNullAction`. ## Test coverage - metadata-only test attribute change. Co-authored-by: Cursor <[email protected]>
Summary of changes
RunOnWindows=TrueandLoadFromGAC=Truetraits toAspNetWebApi.TestNullAction.component: aspnettag output.Reason for change
AspNetWebApi.TestNullActionwas not exercised by the IIS AppSec CI jobs, so snapshot changes could be missed by PR CI.Implementation details
AspNetWebApi.cs.Test coverage
AspNetWebApi.TestNullAction