> > One thing that is interesting about this thread is that > > many are irked by the def of UTs that I laid out. The > > thing is, I'm not trying to change the def in the > > industry. But locally, with some teams, it's a great > way > > to focus. > > I guess my issue with that is that it's just one way to > focus, and it may be the wrong way to focus. In > particular, I've worked with people who make comments like > this: > > Besides being slow, critical dependencies also have > another nasty property: We can't ensure the availability > of the resource being dependent on. > > Sure, one approach is not to do those tests. But another > is to figure out how you *can* ensure the availability of > that resource. Often it requires getting pretty creative.
That's the thing. Those are other tests. I wouldn't recommend not doing them. The thing is, though, I often run into teams that do the hard work you describe but they end up not having any of the more independent tests, it bogs down, etc.
Flat View: This topic has 50 replies
on 51 pages
[
«
|
181920212223242526
|
»
]
Previous Topic
