News for hackers. Stuff that matters.

A comment on Ask HN: Do you write tests before the implementation?. Parent comment

Re:Ask HN: Do you write tests before the implementation? by Trisell on Friday November 15, 2019 @10:15AM (#21545451)
I’ve had really good luck with react UI testing using Jest and React Testing Library and throwing in UI screenshot testing.

At my previous job we eliminated selenium from our testing suite. We found that good UI unit and integration testing caught 99% of the bugs and the bugs that did make it through most likely wouldn’t have been caught by selenium so the added time wasn’t worth it.

[ Parent | on HN ]
Re:Ask HN: Do you write tests before the implementation? by SkyPuncher on Friday November 15, 2019 @03:07PM (#21548241)
IMO, snapshots, like Jest/React, are one of my favorite ways to test UIs. They require minimal effort and address the major points of testing a UI.

Actual pixel "perfect" UI testing should still be done from time to time in a real browser. It's nearly impossible to properly capture some of the layout differences/bug that can come simply from a new browser version.

[ Parent | on HN ]
Re:Ask HN: Do you write tests before the implementation? by Trisell on Sunday November 17, 2019 @12:12PM (#21558803)
We ran screenshots and looked for a percentage same. Because 100% is almost impossible. Where it saved us over snapshots was we were using MUI and they introduced a breaking UI change that our snapshots didn’t catch the change. And the screenshot did because the menu was no longer hidden. But the code hadn’t changed.
[ Parent | on HN ]