3 ms·
For sure. Ever had to debug a bug deep inside of a webpage's code that relied on 5-10 preconditions to get it to appear? Without HMR, you're spending a lot of t
by phist_mcgee 3y ago
For sure. Ever had to debug a bug deep inside of a webpage's code that relied on 5-10 preconditions to get it to appear? Without HMR, you're spending a lot of time F5ing and navigating to reproduce/fix it.
- loloquwowndueo 3y agoIf 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.
- sodapopcan 3y ago“That’s just not, like, how my brain works, man. I have a different development ‘style’, ok?”
- peteradio 3y agoWhy tempt us with such far out propositions?
- phist_mcgee 3y ago`git bisect` with an integration test suite of the backend running in a test environment can get you pretty close.
- pc86 3y agoThat seems completely unrelated to "have a unit test" which is what they're saying.
- loloquwowndueo 3y agoYeah I was being sarcastic :)
- satvikpendem 3y agoYou 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.