Hi All, i feel the reason is 1. since Selenium is easy for integrating with other open source tool like cruise control which is mostly used for making build in a dev env where the selenium scripts can be integrated and runned as soon as the build is done. 2. Selenium test cases can be written as a Junit test cases which are easier for the developer. 3. Cost effective and the test cases are max run 5-6 times till the module is entirely created. 4. most of the test cases are basically record and play and it doesnt make sense to buy a tool for record n play.
Thanks Biswajit On Mon, Aug 9, 2010 at 8:58 PM, arihan sinha <[email protected]> wrote: > The main reason is during agile development while developers finish the > story they run the test suite at their end as well and then checkin the code > to the build server where through cruise control build gets run. > > if you use QTP then say if u ve 5 developers they need to run at their end > same time then u need 5 concurrent QTP licenses which is very expensive. > secondly configuring through eclipse IDE is not that easy. ( not sure) > > so its always advisable to use open source like selenium or RUBY+watir etc. > > > On Mon, Aug 9, 2010 at 2:10 PM, siva prasad <[email protected]>wrote: > >> Leo, >> >> In agile, we develop the build as per storyboards(requirements). After the >> release we need to integrate the code with the previous build and we call >> this process as *continuous integration. *We need to configure QTPserver >> with tools like Cruise Control or Nant. When the build is deployed, QTP >> execution starts automatically. >> >> Selenium is more user friendly then QTP for Agile Projects >> >> regards >> siva,k >> >> >> >> On Mon, Aug 9, 2010 at 12:02 AM, <[email protected]> wrote: >> >>> Leo, >>> >>> When you say "Migrate" from QTP to Selenium...does this mean convert all >>> of the QTP Scripts, and all of their resources into a Selenium test bed? If >>> so, tell us about the complexities after the experience... >>> >>> Thanks, >>> John >>> >>> In a message dated 8/6/10 11:49:18 A.M. Eastern Daylight Time, >>> [email protected] writes: >>> >>> I use both for my QA testing in an agile environment. I do not know a lot >>> about Selenium, but I use QTP mainly for data driven testing and for Client >>> server type application testing. Selenium cannot test Client server >>> applications which still do exist. >>> >>> On the other hand, I find Selenium to be a lot faster than QTP while >>> testing my web applications. >>> >>> That is all I have to add at this time. >>> >>> Regards, >>> Devon Watkis >>> >>> On Fri, Aug 6, 2010 at 11:11 AM, Leonardo Ribeiro Oliveira < >>> [email protected]> wrote: >>> >>>> If your answer is yes, please share your experiences. Pros and cons. >>>> Most agile teams have Selenium as their tool for test automation, I >>>> want to know why. >>>> >>>> I'm starting a new agile project on the next weeks and will migrate >>>> from QTP to Selenium. >>>> >>>> Thanks, >>>> Leonardo Ribeiro Oliveira >>>> >>>> -- >>>> 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]<mercuryqtp%[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 >>> "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]<mercuryqtp%[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 >>> "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]<mercuryqtp%[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 >> "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]<mercuryqtp%[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 > "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]<mercuryqtp%[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 "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
