The previous test seeded tracker resources directly via the GraphQL `CreateTrackerResource` mutation, which doesn't go through the public `/report` handler. Switching the seeding to `ReportDetectedResources` covers the end-to-end path -- payload decoding, validation, and the new upsert -- so the listing assert is now grounded in the same write path that real clients use. Signed-off-by: Émile Ré <emile@getprobo.com>
13 KiB
13 KiB