blocks|key|3377523|text|“自动化测试”并不像听起来那么好。据我所知，它是测试执行的自动化，这只是过程的一部分。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3377524|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

'Automated testing' isn't as good as it sounds. As far as I can tell, it's the automation of test execution which is only part of the process.

blocks|key|3377555|text|哪种类型的自动化测试？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3377556|我已经编写了一些脚本，它们是构建后过程的一部分，用于通过API比较一些结果，但这并不是您特别想要的。|3377557|在自动化windows用户界面应用程序方面，我对rational+but略有了解，但不能特别推荐它。|3377558|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

which kind of automated testing ?

I've written a few scripts that are part of a post-build process to compare some results through the API, but this is not specially what you want.

In terms of automated windows user interface applications, I've had a glimpse on rational robot, but cannot specially recommend it.

blocks|key|4224194|text|我们在我工作的地方不使用QuickTest专业版，但我们正在研究自动化系统测试的选项。就推荐而言，如果不知道接受或拒绝软件工具的标准是什么，那就有点困难了。我正在根据这些标准来评判自动化的系统工具：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4224195|4224196|是否允许程序员以外的其他人员创建自动系统测试？|unordered-list-item|4224197|程序员是否可以为其编写脚本以进行自定义？|4224198|是否支持数据驱动测试(使用来自外部文件和/或environment?|4224199|的测试数据多次运行单个测试)？|4224200|它在多大程度上支持在持续集成and中包含测试|4224201|4224202|这些只是一些功能。成本当然是一个因素。该工具是否需要学习用于脚本编写的专有语言是另一个因素。|4224203|自动化测试绝对是个好主意。自动化测试是continuous+integration的关键推动因素之一。|offset|length|4224204|entityMap|0|LINK|mutability|MUTABLE|url|http://martinfowler.com/articles/continuousIntegration.html^0|0|0|0|0|0|0|0|0|0|J|M|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|13|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|14|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|15|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|16|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|17|8|@]|9|@]|A|$]]|$1|L|3|M|5|E|7|18|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|19|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1A|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1B|8|@]|9|@$S|1C|T|1D|1|1E]]|A|$]]|$1|U|3|-4|5|6|7|1F|8|@]|9|@]|A|$]]]|V|$W|$5|X|Y|Z|A|$10|11]]]]

We don't use QuickTest Pro where I work, but we are in the process of researching options for automated system testing. As far as recommendations go, that's a bit difficult without knowing what your criteria are for accepting or rejecting a software tool. I'm judging automated system tools according to these criteria:

<ul>
<li>Does it enable someone other than a programmer to create automated system tests?</li>
<li>Can programmers script it for customization purposes?</li>
<li>Does it support data-driven testing (run a single test multiple times with test data from external files and/or databases).</li>
<li>Can you configure the order tests run in?</li>
<li>How well does it support inclusion in a continuous integration environment?</li>
</ul>

These are just capabilities. Cost is certainly a factor. Whether or not the tool requires learning a proprietary language for scripting is another factor.

Automated testing is definitely a good idea. Automated testing is one of the key enablers of <a href="http://martinfowler.com/articles/continuousIntegration.html" rel="nofollow noreferrer">continuous integration</a>.

blocks|key|3377697|text|我发现对非UI的自动化测试绝对是值得的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3377698|UI的自动化测试也是值得的，但不是很多。对于我的项目，UI不到代码的10%25。UI的自动化测试还有一堆其他问题，比如定时和线程访问，这使得它比预期的更加困难。我使用nunitforms进行UI测试。|3377699|我建议如果可能的话，先测试UI背后的逻辑，然后再测试UI。通过非UI测试，您可以获得更好的回报。|3377700|我评估了Automated+QA的测试程序，它看起来很好，但我选择了nunitforms，因为它更类似于我为非UI测试所做的事情。|3377701|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

I've found automated testing of non-UI to be definitely worth it.

Automated testing of the UI is also worthwhile, but not as much. For my project, UI is less than 10% of the code. Automated testing of the UI has a bunch of other issues like timing and thread access that makes it more difficult than expected. I use nunitforms for UI testing.

I'd suggest that if it is possible, test the logic behind the UI first, then test the UI last. You get much better bang for buck with non-UI testing.

I evaluated Automated QA's testing program and it looked good but I went with nunitforms since it was more similar to what I was doing for non-UI testing.

blocks|key|161120|text|有几个关于测试自动化的线索：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|161121|161122|Which+is+better+for+web+testing?+Record-Play+automation+or+coding?|unordered-list-item|offset|length|161123|User+Interface+Testing|161124|Automated+testing+of+GUI|161125|161126|我从未使用过Quick+Test+Pro，但我参与了几个使用了不同自动化测试工具的项目:+Silk+Test，Rational+Robot，WinRunner。这些工作中最成功的是使用Rational+Robot和RRAFS框架来将应用程序更改从测试脚本中隔离出来。我们还使用STAF框架来自动化和管理我们的测试基础设施。|161127|自动化测试是测试应用程序各个方面的一种很好的技术，但它不能取代人工测试人员。像所有的工具一样，你可以使用它，也可以滥用它。只要你正在测试的东西是稳定的，重复的，有可预测的或可计算的结果，并且你足够频繁地测试它，那么自动化的成本最终会得到回报。|161128|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/142398/which-is-better-for-web-testing-record-play-automation-or-coding#311259|1|https://stackoverflow.com/questions/41601/user-interface-testing|2|https://stackoverflow.com/questions/226342/automated-testing-of-gui#226765|3|http://staf.sourceforge.net/^0|0|0|0|1U|0|0|0|M|1|0|0|O|2|0|0|3U|4|3|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|15|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|16|8|@]|9|@$F|17|G|18|1|19]]|A|$]]|$1|H|3|I|5|E|7|1A|8|@]|9|@$F|1B|G|1C|1|1D]]|A|$]]|$1|J|3|K|5|E|7|1E|8|@]|9|@$F|1F|G|1G|1|1H]]|A|$]]|$1|L|3|-4|5|6|7|1I|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|1J|8|@]|9|@$F|1K|G|1L|1|1M]]|A|$]]|$1|O|3|P|5|6|7|1N|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|1O|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X]]|Y|$5|T|U|V|A|$W|Z]]|10|$5|T|U|V|A|$W|11]]|12|$5|T|U|V|A|$W|13]]]]

There are several threads on SO concerning test automation:

<ul>
<li><a href="https://stackoverflow.com/questions/142398/which-is-better-for-web-testing-record-play-automation-or-coding#311259">Which is better for web testing? Record-Play automation or coding?</a></li>
<li><a href="https://stackoverflow.com/questions/41601/user-interface-testing">User Interface Testing</a></li>
<li><a href="https://stackoverflow.com/questions/226342/automated-testing-of-gui#226765">Automated testing of GUI</a></li>
</ul>

I've never used Quick Test Pro, but I've been on several projects that have used different automated test tools; Silk Test, Rational Robot, WinRunner. The most successful of these efforts was the one that used Rational Robot with the RRAFS framework to isolate application changes from the test scripts. We also use the <a href="http://staf.sourceforge.net/" rel="nofollow noreferrer">STAF</a> framework for automating and managing our test infrastructure.

Automated testing is a good technique for testing facets of an application, but it doesn't replace human testers. Like all tools, you can use it or you can abuse it. As long as what you're testing is stable, repetitive, has predictable or computable results, and you test it often enough, then the cost of automating will eventually pay for itself.

blocks|key|4224354|text|我是一个使用QTP的自动化团队的负责人，我讨厌它。录制/回放功能很糟糕，它经常会被弄糊涂，导致奇怪的测试结果。记录只能用来建立对象数据库，即使这样，为了让它在某种程度上可靠地工作，还必须进行各种黑客攻击。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4224355|QTP/QC是基于ActiveX/COM的，只能用VBScript编写脚本，这是另一种火热的狗便便。为了获得任何类型的可扩展性，我们必须使用所有这些技巧和技巧。我们正在做的事情包括运行一个测试，该测试动态地将QTP测试添加到测试套件中，编辑输入参数，更改对象存储库以使其与环境相匹配，保存测试，生成调度程序实例以运行测试。测试完成后，将所有结果复制到父测试，然后从测试集中删除QTP测试。最后，我们最终发布了定制的COM组件，VBScript调用了这些组件，并使用QTP/Quality+Center作为一个半途而废的报告引擎，它并没有真正提供足够的灵活性来获得我们真正需要的报告类型。|4224356|水星/惠普的另一个问题是，他们将所有的技术支持外包给了印度，而没有对他们进行培训。在你可以与任何有API技术知识的人交谈之前，在底层支持炼狱中花费两周的时间是很常见的，结果却被告知，是的，这是一个bug，但不，我们不会修复它。|4224357|我很抱歉我的粗鲁的语言，但我发现整个事件的精神创伤，再也不会在一个项目或使用QTP/QC的团队工作。|4224358|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

I was head of an automation team that used QTP and I hated it. The record/playback functionality was horrible, it would routinely get confused resulting in weird test results. Record could only be used in order to build up the object database and even then had to result to all sorts of hacks in order to get it to work somewhat reliably. 

QTP/QC is based on ActiveX/COM and can only be scripted with VBScript which is another bag of flaming dog poo. There are all these hacks and tricks we had to do in order to get any sort of extensibility. We were doing things like run a test that dynamicly adds the QTP test to the test suite, edit the input parameters, change the object repository so that it matches the enviroment, save the test, spawn a scheduler instance in order to run the test. Once the test is done copy all the results to the parent test and then remove the QTP test from the test set. In the end we ended up publishing custom COM components which the VBScript called into and used QTP/Quality Center as a half-assed reporting engine that didn't really offer enough flexibility to get the type of reports we really needed.

Another problem with Mercury/HP is that they outsourced all of their tech support to India and didn't train them. It was common to spend 2 weeks in lower level support purgatory before you could speak to anyone with any technical knowledge about the APIs only to be told that yes it's a bug but no we won't fix it.

I sorry about the strong language but I found the whole episode traumatizing and will never work on a project or for a team that uses QTP/QC ever again.

blocks|key|942581|text|如果在tasks.For中有重复，那么应该有任何任务的自动化，例如在模块中如果你必须为每个构建运行回归测试用例，其中在产品中进行了一些小的改进，那么回归测试用例运行可以自动化。在这个例子中，重复性测试用例的自动化将提高生产力，并使测试人员能够更专注于手动测试。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|942582|除了qtp之外，你还可以探索qt相关项目的squish，以及windows+C%2B%2B和VB项目的测试伙伴。|942583|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Automation of any tasks should be there if there are repetition in the tasks.For e.g. in a module if you have to run regression test cases for each build in which some minor improvements are made in the product, then the regression test case run can be automated. In this example, automation of the repitive test cases will increase productivity &amp; will enable tester to concentrate more on manual testing.

Apart from qtp, you may also explore squish for qt related projects &amp; test partner for windows C++ &amp; VB projects.

blocks|key|947629|text|丹，我用QTP+11来实现自动化。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|947630|让我知道你的要求，比如你想测试哪种应用程序等。许多开源和共享软件工具几乎适用于所有类型的应用程序。|947631|自动化测试是一个好主意，前提是你要自动化的东西不会经常改变。如果不是这样，您最终将更频繁地修改测试脚本，而不是在需要时在您的应用程序上运行它。|947632|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Dan, I use QTP 11 for automation. 

Let me know your requirements like what kind of application you wanna test etc. Lot of open source and shareware tools are available for almost all kind of applications. 

Automated testing is a good idea, provided what you are going to automate is not gonna change very frequently. If not, you will end up modifying the test scripts accordingly more often than running it on your application when needed.

I have three easy questions.

Does anybody use QuickTest Pro for automated testing? 

Any other automated testing applications that you recommend?

Is automated testing a good idea?

Thanks

QuickTest Pro automated testing

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我有三个简单的问题。有人使用QuickTest专业版进行自动化测试吗？您还推荐其他自动测试应用程序吗？自动化测试是个好主意吗？谢谢

问QuickTest专业版自动化测试
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问QuickTest专业版自动化测试EN