I'd argue that if you feel like you have to use snapshot testing to meet a deadline, you probably don't even need the test in the first place. It's one thing i

I'd argue that if you feel like you have to use snapshot testing to meet a deadline, you probably don't even need the test in the first place. It's one thing if you're using snapshot testing like your average test, to make sure things don't break when you make changes. But if you're in a bind, is a snapshot test really better than your own eyes? Maybe it's better to release the thing in that case and add better tests asynchronously to the deadline. I suppose the snapshot test in a pinch is not so bad if it's just changes being made to legacy code. But I'm not sure I'd do such a thing when building new features.