I have to automate an application having several complex functionalities with a set of resources that are relatively beginners in automation. We will be using Test complete for the same. I have to lead the team and will have to handle multiple responsibilities like guiding the testers with Test complete and other basic automation concepts.
I am trying to follow the approach please tell if there can be anything better
Approach: I am planning to sit with each module owner(who will eventually automate his module) and develop a DFD for him which will suggest him to create what functions to create and when to call what. Apart from that I have created some generic reusbalbe functions like for Checkpoints, Object search , Synchronization..
Please tell me is this the right approach or somehting else is required
Many thanks for your reply. They are quite raw. But that training thing I had planned already. Now after training also they will learn tool but not automation as such. so my primay concern is at this point itself. Thats why I asked that whether the approach to create a DFD for them and guiding them with problems they face is the right approach or something else also must be included
My understanding is you and your team of developers are write test fixtures for testers and test engineers to reuse in their tests. That approach is doable, but I would highly suggest building that proficiency for testers to be able to write fixture code as well. I think you'll find that test fixture code maintainence will become an annoyance if development effort gets interrupted frequently for small changes.
For a while, my team (team responsible for maintaining the test automation framework) was a sole people writing test fixtures. But after a while, automation effort grew exponentially and we eventually became a bottle neck as the number of tests grew much faster than we could write and maintain the fixtures supporting those tests.
How about writing one module automation yourself. Then do a code review of your code with the team. Walk them through what you did and why you did it. Make sure they ask questions that will help them understand the fundamentals of test automation.
Unless you are very sharp in automation, a good teacher and have lots of time to review and critique their code, I think this effort may be futile. People that have no experience in test automation need lots of guidance to do things correctly. Relying on "green" individuals to write complete test cases with no experience and no lead is pretty risky.
Also, is your test automation going to be quality driven or time based? Is your team under the gun to produce something right away or are you going to be given the time needed to grow these people into test automators?
If this or any response has helped you, please reply to the thread stating that it worked so other people with a similar issue will know how you fixed your issue!
First thing is to have a framework in place(Could be a smaller one but we should know how this thing is going to role out). And decide on reusable functions/code within the modules and across the modules. Develop the framework code and reusable functions.
Once the framework and reusable functions are in place, it will be easy for a team to achieve automation.