I know i had put similar post before but this is slightly different and very specific.
After spending sufficient time in automation still when it comes to start new project there always remains doubt in mind should I do this with Record & Play back or should i use full descriptive programming.
and If you are specifically asked by your director "Can we automate this application by just record and playback?" Provided 1. Applications are pretty stable now and no chance for GUI change. 2. They want script to be maintainable over the years Than,
What will be your approach??
Do you feel that DP is only the answer? If yes why? Should we even think of Record and playback? if yes why and when???
Request everyone who read this thread to give their opinion about how they evaluate both approaches?
Note : I recently read book on automation testing and it says that "Capture and playback is not the automated testing"
Re: How to evaluate approach? While starting project
thanks for the response. Let me change my question little bit. I did take look at many such articles and also reading very popular book on automation,
Software Test Automation (Effective use of test execution tools) , by Mark Fewster & Dorothy Graham
however I want to see whats happening in the real world. I understand record and playback is not the answer to any automation solution but in real practice how many % of record and playback is used by people? Are people using fully descriptive with 0% record and play-back?
requesting everyone to give reply in one or two line about what approach they are following and may be why?
I am not very much experienced in the automation area so everytime I start with new project the question comes in my mind is , should i record some part of application to speed up the work??? will greatly appreciate your logical short answers on this.