Can any tell me how can we create a plan for test automation. yes, There can be N number of ways. but just wanted to know what approach do you think is the best. I mean it should be clearer, Easier to understand and should be explicit in what it wants to say. Please share your thoughts
You can check out Elfriede's book that's noted in this forum, it has material on that subject. Basically though you will want to consider this as a software project, because that is what it is - even if it is an internal tool you will be developing code. So treat it as an internal project with designs, milestones and code reviews.
Nothing learns better than experience.
"So as I struggle with this issue I am confronted with the reality that noting is perfect."