3 ms·
A bit more insight might be helpful...I've found that effective testing differs some based on type of work and technology. For example, the way you test a game
by latch 15y ago
A bit more insight might be helpful...I've found that effective testing differs some based on type of work and technology. For example, the way you test a game is different than a website. And the way you test Rails is different than how you test Java.
- czzarr 15y agowe build web apps in a proprietary language (yeah I know this is the core of our problem but it's not something we can change right now)
- latch 15y agoYa, that's a problem. Still don't know enough to say, but if I had to guess, I'd say your core problem is cultural/people, and until that changes, there's nothing you can "learn" to improve. On a technical level, if your language doesn't support things like inversion of control (in one form or another) and reflection/proxying (or a dynamic runtime), it's going to be an uphill battle to write effective, non-brittle unit tests. Therefore, maybe end-to-end integration tests might be a better fit (for which, I'm no expert).