I totally agree with Matt on this that Testware that comes in a box becomes Shelfware in distant future. This is because it does not meet the project constraints and software design and has to be tweaked to fit the project requirements at great deal of expense and on top there is no corporate policy to implement it. The projects that I have worked or overseen over the years had one thing in common; the Testware adopted on one was abandoned in the second, Testware used in the third rejected in the fourth and so on. The success of automation depends on companywide policy and commitment from senior management. The Testware specifically produced for each project also comes at a cost and is a throw away once no more changes are made to the system. Then it does not come with 5 digit tag but cumulative cost from a number of projects may come to that. In the end it would be worth it.
Not all testing should be done by the team; there should be a degree of flexibility within the development that allows outside-in testing by independent testers. How this is performed, manual or automated would depend on the scale and available resources.
Sometimes you have to work on more than one project; this is where in house Testware limit your ability to work effectively. In such situations, Testware in a box is more effective and helps switch resources more quickly between projects because there isn't time to train people in each of the in house built Testware. I guess there is no simple answer to automation; therefore, I would say whatever works for you. Testware in a box is not a silver bullet but it is a good start if you can afford five figure sums. At the end of the day one should not discount automation as a farce.
Mohinder
With kind regards,
Mohinder Khosla, PhD
__._,_.___
MARKETPLACE
.
__,_._,___
0 comments:
Post a Comment