Can any one please throw some guidelines what task and subtasks are included while developing a test suite script development project plan. Like for example say for a web app can the below be defined as tasks or subtasks
- Creating GUI MAP file
- Designing Script flow
- Developing/Coding Script
- Testing script execution
- Porting Script on some other desktop or
putting on N/w for usage by others
Also what should be the basis of coming up with estimated hours. I mean what factors should be included. My management has no idea about WINRUNNER terminologies.
[This message has been edited by LRWRnovice (edited 08-28-2002).]
Shall I assume no one has come across project planning stage for WINRUNNER scripting. OR I need to post it in some other forum. I need info as this might be useful for the rest of the forum audience. Thanks
<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by JCTreb: (Three hours isn't always enough for people to read your query and to generate a meaningful response.)
That having been said, you might want to post a more general query in the Automated Testing forum as you might get more responses (and not just from people that use WinRunner.)
Yes u r right 3 hours is not enough. AI got impatient my fault...but then I needed some ****** inputs thought giving a fast try...
All said that I need to develop project plan for automated testing efforts using WINRUNNER hence looking for some specific inputs with regard to WINRUNNER...