QTP vs Selenium - 比较 [英] QTP vs Selenium - Compare
问题描述
我有一个使用.net技术创建的应用程序/产品。此产品具有一个GUI，它使用Web API（应用程序服务器上的SOAP）连接到数据库。大多数测试对于DB中的值执行，而其他测试可以落入可用性，性能等。因此，要执行的测试的60-70％是要验证DB中的值是否被正确地显示，而其他测试GUI是否如需要在需求规格中工作。
I have an application/product which is created using .net technologies. This product has a GUI, which connects to a DB using a Web API (SOAP on an application server). Majority of the tests are executed for the values in the DB, while the others may fall into Usability, Performance, etc. As such, 60-70% of the tests to be executed are to verify if the values in the DB are correctly shown on the GUI, while the others test if the GUI is working as desired in the requirement specifications.
测试的另一个方面也是测试与DB和GUI的后端应用程序服务器接口。因为这将使我们能够确定应用服务器是否向GUI发送错误的值，或者是否是具有错误值的数据库。
The other aspect to the testing will also be testing the backend Application server interface with both the DB and the GUI. As this will enable us to determine, if the App Server is sending bad values to the GUI or is it the DB which has bad values!
产品UI不会更改除了以附加的下拉菜单项和这些菜单项的附加页面的形式添加新功能。
The product UI does not change much, except to add new features in the form of additional dropdown menu items and additional pages for these menu items.
考虑到上述情况，哪个框架会更合适？ QTP或Selenium或其他商业/开源工具？
Considering the above, which framework would be more suitable? QTP or Selenium or some other Commercial/Open Source tool?
（成本不是一个主要问题，浏览器兼容性或操作系统。 ，并且DB是兼容的。）
(Cost is not a major concern, and neither is browser compatibility or OS. The system installs on a Windows Server, and DB is compatible.)
推荐答案
我们有一个围绕Selenium构建的验收测试框架来测试我们的应用程序， flex UI与Java + db后端交互。
We have an acceptance testing 'framework' built around Selenium to test our app which has a flex UI that talks to a java + db back-end.
我们可以轻松地将Selenium集成到我们现有的测试和持续集成基础设施中，因为我们可以在java中编写我们的脚本，并使用junit来驱动测试。这些测试也由开发人员编写和维护。我们还在每次测试之前使用dbunit设置数据库。
We could easily integrate Selenium into our existing testing and continuous integration infrastructure because we can write our scripts in java and use junit to drive the testing. These tests are also written and maintained by developers. We also use dbunit to set up the database before each test.
我们的测试部门决定使用QTP。他们看到我们的基础设施建立在Selenium周围，但他们发现很难理解。我知道他们有一个全职的专人写的测试和维护他们。
Our test department however decided to go with QTP. They were shown our infrastructure built around Selenium but they found it hard to understand. I know they have a full-time dedicated person to write the tests and maintain them.
由于我不知道您的具体情况，我只能建议您考虑以下情况：
Since I do not know your exact situation I can only suggest you to consider the following:
- 谁在编写和维护测试？
- 套件是否是大型基础设施的一部分？
- Who is writing and maintaining the tests?
- Are the suites going to be part of a larger infrastructure?
Selenium是一个不错的选择...
- 您有开发人员负责撰写和维护测试
- 您需要将这些测试作为更大基础架构的一部分
- 您认为您可能想要测试Windows以外的其他浏览器和其他平台
- 您想要一些自由
- you have developers responsible for writing and maintaining the tests
- you need to have these tests as part of a larger infrastructure
- you are pretty sure you do not need to do much testing outside of the browser
- you think you might want to test other browsers and other platforms besides Windows
- you want something free
QTP可能是一个不错的选择...
- 你有较少的代码级人员编写和维护测试（虽然我不知道Selenium IDE是否很难学习非
此 http://functionaltestautomation.blogspot.com/2008/10/sno-features-qtp-selenium-explanation_22.html\">范例也可能会助您一臂之力。
This article might also help you.
我认为很明显哪一个我喜欢，但你需要决定什么最适合你的情况。
I think it is obvious which one I prefer, but you need to decide what works best for your situation.
这篇关于QTP vs Selenium - 比较的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
