- Agile development is getting bigger and bigger. What does this have to do with Quicktest Pro?
- QTP can't handle continuous deployment, the tests takes to much time to run and can't be easily integrated with Hudson, CruiseControl or other CI tools. Just have your build process launch a vbscript to kick off your automated suite on remote machines. Continually poll those machines until the suite finishes. Provide more machines so your test run in parallel to make it faster. - QTP can't handle BDD (it's possible with BPT but it's really expensive and doesn't work very well). Whats BDD? Selenium is a web based testing tool only. What if you have a java application? What about web services? You are going to have to start using different tools for this testing. How are you going to report the results? You are going to have to create custom build reporting. QTP does all of the above nicely. - VBScript is and old language and doesn't support a lot of features supported by newer languages like Python and Ruby. What features does python and ruby provide that is essential for test automated that VBScript doesn't provide? - VBScript is not used for development, so DEVs and QAs can't code on the same language and improve knowledge sharing. How much code sharing does QA really share with DEV? VBScript is probably the easiest language to code in and its pretty lightweight. What do you think about that? I really interested in your views. *** I will think about new points and add here later *** Regards, 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] For more options, visit this group at http://groups.google.com/group/MercuryQTP?hl=en
