3 ms·
One gig I worked had web component tests where they committed a snapshot of the expected DOM and asserted that the component spat it out... so for every subsequ
by pshc 3y ago
One gig I worked had web component tests where they committed a snapshot of the expected DOM and asserted that the component spat it out... so for every subsequent change the dev would naturally hit the re-generate button and commit it all. Plentiful deltas, questionable signal.
- gen220 3y agoCounterpoint, those tests are really useful when you're working on a shared sub-component/library and want to understand the scope of a change, or want to be confident that what should be a no-op change from the caller's point of view is indeed a no-op. But yea 9/10 times that a snapshot test fails, it's noise rather than signal.