Comment by fidotron
2 days ago
This is the core point. A canary deployment that was not preceded by deploying data that activates the region of the binary in question will prove nothing useful at all, while promoting a false sense of security.
2 days ago
This is the core point. A canary deployment that was not preceded by deploying data that activates the region of the binary in question will prove nothing useful at all, while promoting a false sense of security.
The root problem is that a dev team didn't appropriately communicate criteria for testing their new feature.
Which definitely seems like shortcut 'on to the next thing and ignore QA due diligence.'
Google does not separate dev and QA in general (I'm sure there are exceptions).
That sounds like a conflict of interest in practice.
Who's ass is responsible when a dev team starts missing coverage in their tests, like happened here?
1 reply →