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

If only there was a way to programmatically reproduce the conditions under which the problem appears and then exercise the behaviour that triggers the bug. Then some code could verify whether the problem still appears. Once the problem is fixed this same “test” dark magic could help ensure the problem does not occur again.

Pipe dreams, my friends. Pipe dreams.



You can add a test after debugging, no one's stopping you. But yes, it's annoying to debug some UI issue and having to set up an entire integration test for an issue you already know is there and can navigate much more easily via a mouse than via linking through HTML tag ids.


“That’s just not, like, how my brain works, man. I have a different development ‘style’, ok?”


`git bisect` with an integration test suite of the backend running in a test environment can get you pretty close.


That seems completely unrelated to "have a unit test" which is what they're saying.


Yeah I was being sarcastic :)


Why tempt us with such far out propositions?




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

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

Search: