This can be implemented based on
1. the requirements of Application Under Test.
2. experience of the automation developer
3. Time and budget
so on..
In my opinion - first thing we should take in concideration is the AUT and the designing the test cases, depeding on these we can devide the test in suitable different Actions i.e. Reusable , Prepare and associate the repository to the actions and proceed with designing the reusables covering all possible test scenarios for particular action. finally all the actions can be assembled in a test to cover the whole scenario.
I think this is the best way to proceed with QTP scripting, although we can do this by any convenient method, we have some nice articles on this see at https://www.learnqtp.com/
1. the requirements of Application Under Test.
2. experience of the automation developer
3. Time and budget
so on..
In my opinion - first thing we should take in concideration is the AUT and the designing the test cases, depeding on these we can devide the test in suitable different Actions i.e. Reusable , Prepare and associate the repository to the actions and proceed with designing the reusables covering all possible test scenarios for particular action. finally all the actions can be assembled in a test to cover the whole scenario.
I think this is the best way to proceed with QTP scripting, although we can do this by any convenient method, we have some nice articles on this see at https://www.learnqtp.com/