_{settings ⋅ feedback ⋅ docs ⋅ learn more about trunk.io}

You'll probably also want to wire in changing places where JEST_JUNIT_SUITE_NAME is set, otherwise the variants will only show up under different tests still

I'm not sure I understand this? Why does that matter, and what do you mean by show up under different tests?

Big fan of variants and I want to get it set up here. Right now we set JEST_JUNIT_SUITE_NAME manually in order to mimic the concept of variants. This means that when we run a test on linux and mac, they show up as different tests

So if the desire of this change is for this to show up as one Testing linter osv-scanner main Snapshots instead of separate Testing linter osv-scanner <os> main Snapshots, you should modify the use of JEST_JUNIT_SUITE_NAME to omit the OS piece. This will create a new test to track this, but I think that's fine

I see, will do. You're correct that it'll create a new test, but adding a variant does that anyway, so that's already a thing.

So if the desire of this change is for this to show up as one Testing linter osv-scanner main Snapshots instead of separate Testing linter osv-scanner <os> main Snapshots, you should modify the use of JEST_JUNIT_SUITE_NAME to omit the OS piece. This will create a new test to track this, but I think that's fine

@TylerJang27 Ah, gotcha. Since we're only testing this on staging, and the uploader runs for the same tests on both staging and prod, I'd prefer to leave it as-is to not mess with prod for now, if that's alright?