Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I agree it may be a design problem with the CSS, I agree.

But my point is exactly that: I can't just go in and _improve the code_ (extracting classes, rewriting it in less/sass or whatever) because to verify the changes do not mess up the UI requires clicking around many pages in half a dozen browsers in three OSes.

And thank you very much for the practical note, it's an interesting idea!



You're in the catch-22 of being unable to write tests without refactoring, and unable to refactor without test coverage. I get it.

I hope the automated screenshot idea helps. I personally found it more useful in theory than in practice, but I wasn't doing a lot of UI polish work.


One other practical note, you can create a single (test) page that showcases all of the visual styles currently in use, so there is one page to check manually.




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: