This is more of a sanity check question. How are people writing their scripts? Here is what my current work practice is(In Brief):
The test case is broken down into its most distinct steps. Each step is then written as an action. Originally I was working to each business process as a seperate action but this seems inflexible and less manageable. It makes more sense to me to record each step of the business action as a seperate action.
Maybe I am stating the obvious or maybe I am completely wrong.Can anyone see any flaws in this method I am using?
I am quite new to QTP but have been using winrunner for quite some time. The two tools require a radically different approach. It is this reason that I ask the above question.
Each distinct step as an action...i dont think a good way.
Divide the test case in to modules ( where module is nothing but set of related steps )
For each module one action,
If the module is big then divide the module into different actions.
Thanks for your opinion but why dont you think this is a good way? I am not questioning your judgement but a bit more expansion would be appreciated.
What you have described is how I had originally started, however, I found reusing the actions to be more tricky and found myslef rescripting the actions. Breaking them down to the component steps just seemed logical at the time, but now I am rethinking my strategy.
I decide on my split based on 2 factors (in most cases) - navigation and re-usability. I try to have steps that can be re-used in other scripts in a separate action. I also try and split up actions based on pages that are tested. The 2nd is not a stead-fast rule but I try to stick to it unless there isn't much to be tested on a page.
The only demerit of what you have stated above as I see would be the number of actions. You are going to have a lot of actions in your script with that approach. The merit of that approach is it's easier to manage coverage.
(I'm hiring Software Development Engineers in Test in Seattle, WA)
I think its best to work out a solution thats more suited to ur application than trying to fish out something thats out there readymade.
For some the module approach might workout and for some an entire BP approach at one go might workout.
let me give u an eg:
I have worked with diff types of app and one of them was a Windows based app which works through fat client. For this app I use a approach which actually paid me well when i built the framework on it later. In this app i always divided the app into three actions,
1) first one is invariably the navigation part(this is not the login one).
2)the second is the core which deals which the actual Business Process.
3) the third is to getting back to where i started in the first place.
Combining this with login and logout script later, worked wonders.
Now then came a web app which reqd me to check for some securities of some 30 diff users and then their respective previleges and then later their own BP's. Now i shifted to all in one approach. Since trying to modularize this doesn't really help.
So have one good god darn look on ur app, pray and go to sleep and next morning u would find the right way!!!!!!(just kidding). What i was actually trying to say was it is always independent and highly based on the requirements.