As a general rules of thumb, we use automation for Regression Testing. When say regression testing, once the Build 1 is complete, then automation start working on Build 1 etc... So as a good practice use Automation only for stable application behavior.
But as per your needs if you want to start automating during Application development itself, there are couple of challenges. 1. Rework will be more. There might chances that the whole automation become a TRASH. 2. You are not confident that whether it is bug or application behavior? etc.... It is not advisable to start Automation during Application Development. Thanks, Uday QTP Videos <http://www.youtube.com/user/AnemUday/videos> On Wednesday, 25 September 2013 01:04:29 UTC+5:30, surabhi wrote: > > Can anyone suggest the disadvantages of developing the automated scripts > in parallel to the development when no environment is given. > > Thanks > -- -- You received this message because you are subscribed to the Google "QTP - HP Quick Test Professional - Automated Software Testing" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/MercuryQTP?hl=en --- You received this message because you are subscribed to the Google Groups "QTP - HP Quick Test Professional - Automated Software Testing" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
