Oh Sorry... you asked about problems with our approach
Well yes there are some...
- Automated testing means its very difficult for developers to 'ignore' problems that they don't feel like/can solve. This can be frustrating.
- People who can't code lose their jobs very quickly!
- It does mean more code is generated, and of course test themselves have bugs. However TCL/ACS is a fairly forgiving environment in this regard as that dreaded compilation step is missing.
- It can be difficult to create 'state machines' for certain applications. In the case of OACS its not so bad, as a database is always a really good way of preapring a test state.
- A-Testing tends to keep highlighting things that are wrong/spurious but also things that are just not well implemented. It becomes very easy to spend too much time solving problems that weren't that critical (although lets not discourage excellent code).
- It can be really difficult to get people to adopt it, because traditional western thinking works along the lines of Socraterial criticism.. i.e. the way to the right answer is constant critisicsm until what your left with is perfect.... a better (more eastern) way to look at things is to Accept, Apply and only then Adapt..
Hope that helps