2 ms·
Testing code is exactly where I'm doing the print debugging from. I'm sure not doing it on production unless I have no choice! I don't take a dogmatic view of
by jerf 4y ago
Testing code is exactly where I'm doing the print debugging from. I'm sure not doing it on production unless I have no choice!
I don't take a dogmatic view of testing. There is no requirement that test code in X must be run in a test harness in X. There is no problem testing my database procedures with code being driven from my primary app language. What matters is that cases are covered, and that the desired outcomes are verified. My database code is perfectly well covered with testing. If yours isn't, that's a process problem on your end and is your problem, not mine.
- Capricorn2481 4y agoI wasn't accusing you of anything, I was genuinely asking. Do you mean that your testing logic is done in the code? I don't really know what that has to do with print debugging. Are you reading output from the database and running assertions on that?