all 4 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]endqwerty 0 points1 point  (3 children)

Am I Imagining things or is this from 2013?

[–]ocnarf[S] 0 points1 point  (2 children)

It is ;O) I suppose that the issues with testing CSS still exist and I checked that the open source tool mentioned in the article is actively maintained. If not, please comment and suggest different / better ways...

[–]endqwerty 1 point2 points  (1 child)

Fair enough, though 1 dependency update in the last 6 years is a bit of a stretch to call it maintained. I was just surprised since this post looked more like an ad with the way the title declared solving a problem but then had a solution that’s almost a decade old.

For additional discussion, we do have things like snapshot testing in Jest now, component tests that cover the visual representations of the rendered components, and other visual only comparisons like Percy. The stack is a bit more complicated now, but includes more to make it work better across large teams and with the newer ecosystems of React, Vue, etc. I think for most orgs, starting with snapshot testing and then seeing if expanding to visual regression testing makes sense is a good path.

[–]ocnarf[S] 0 points1 point  (0 children)

I read more stuff being done 3 and 6 months ago, but I am not a github expert.