为什么 TestComplete 这么慢?

发布于 2024-07-18 00:24:58 字数 420 浏览 7 评论 0原文

我们正在使用 AQTime 的 TestComplete 通过我们的客户端/服务器应用程序在客户端测试 GUI。 它是用Delphi 2007编译的。客户端源代码约为140万条源代码。 硬件是 Intel 双核 2.13 Mhz、2 GB RAM,使用 Windows XP Pro。

我使用所有调试选项编译应用程序,并按照文档中所述链接到 TCOpenApp、tcOpenAppClasses、tcPublicInfo、tcDUnitSupport,使其成为开放应用程序。 生成的 exe 文件大约为 50 MB。

现在运行测试脚本时它可以工作,但是运行速度非常非常慢。 CPU 正在 100% 运行,由于速度缓慢而更改测试脚本有点令人沮丧。 我已经关闭了所有桌面效果,例如圆角窗角。 没有桌面背景。

还有其他人有相同的经历甚至解决方案吗?

We are using TestComplete from AQTime to test the GUI at client with our Client/Server application. It is compiled with Delphi 2007. The source of client is about 1.4 millions sourcelines. The hardware is a Intel dualcore 2.13 Mhz, 2 GB RAM using Windows XP Pro.

I compile the application with all debug options and also link in TCOpenApp, tcOpenAppClasses, tcPublicInfo, tcDUnitSupport as described in documentation to make it an Open Application. The resulting exe-file is about 50 MB.

Now when running the testscript and it works, but running very very slow. The CPU is running at 100 % and it is a bit frustrating to change the testscript because of the slowness. I have turned off all desktop effects like rounded window corners. No desktop background.

Anyone else with the same experience or even an solution ?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

故事还在继续 2024-07-25 00:24:58

您的问题可能在于您使用调试信息进行编译并使用 tcXXX 单元,导致创建大量对象。

来自 AutomatedQA 的文字记录留言板

你是在调试模式下编译的吗? 我们有一个应用程序,编译后
与 TC 一起使用时,调试模式速度很慢。 这是因为大量的
里面的物体。 如果我们编译时不进行调试,但使用 TC 启用程序,
一切都很好。

这个< /a> 可能有帮助

您可以在几个领域
提高速度。

如果您只是使用记录和
播放,然后考虑更换
.Keys("xxx") 调用 .wText = "xxx"。
Keys 函数将使用 ms
按键之间的延迟,而 wText
只是强制文本覆盖
内部。

第二个建议(您
可能已经看过)是
工具->默认项目
属性->项目->播放、设置
延迟为 100 ms、5 ms 和 5 ms
将停顿保持在最低限度。

至于对象属性,是的,TC
加载它们全部。 你可以强制这个
对您进行流程刷新
应用程序,以便数据
被迫在没有
调用时加载延迟。 这有可能
帮助减少出现
延迟。


编辑:

  • 我们也一直在评估TestComplete,也遇到了这个性能问题。 我很想知道您是否以及如何最终解决了这些问题。
  • 也就是说,我认为它是一个具有巨大潜力的产品,可以真正帮助您组织所有单元、集成和 GUI 测试。

Your problem probably lies in the fact you compiled with debug info and are using the tcXXX units, resulting in an enormous amount of objects being created.

A transcript from AutomatedQA message boards

Did you compile it in debug mode? We have an app that when compiled in
Debug mode is slow when used with TC. This is because of the enormous # of
objects in it. If we compile w/o debug but with the TC enabler(s),
everything is fine.

and this one might help to

A couple of areas where you can
increase speed.

If you are just using record and
playback, then look into replacing the
.Keys("xxx") calls to .wText = "xxx".
The Keys function will use the ms
delay between keystrokes, while wText
just forces the text overwrite
internally.

The second suggestion (which you
likely have already looked at) is
Tools->Default Project
Properties->Project->Playback, setting
the delays to 100 ms, 5 ms, and 5 ms
to keep the pauses to a minimum.

As for the object properties, yes, TC
loads them all. You can force this
with a process refresh on yor
application, so that the data is
forced into being available without a
load delay when called. This might
help with reducing the appearance of
delay.


Edit:

  • We also have been evaluating TestComplete and also encountered this performance problems. I would be very interested to know if and how you've finally solved them.
  • That said, I think it is a product with great potential and can really help you with organizing all of your unit, integration and GUI tests.
少女七分熟 2024-07-25 00:24:58

现在运行测试脚本时它可以工作,但运行速度非常非常慢。 CPU 正在 100% 运行,由于速度缓慢而更改测试脚本有点令人沮丧。 我已经关闭了所有桌面效果,例如圆角窗角。 没有桌面背景。

还有其他人有相同的经历甚至解决方案吗?

我建议您尝试更改 TestComplete 用于远程连接的 TCP 端口。 您可以在网络套件选项对话框中更改它们。 例如,您可以设置6100-6102端口。 这有帮助吗? TC 9.20 消耗中描述了类似的问题高 98% cpu SmartBear 论坛帖子。

Now when running the testscript and it works, but running very very slow. The CPU is running at 100 % and it is a bit frustrating to change the testscript because of the slowness. I have turned off all desktop effects like rounded window corners. No desktop background.

Anyone else with the same experience or even an solution ?

I recommend that you try changing the TCP ports that TestComplete use for remote connections. You can change them in the Network Suite Options Dialog. For example, you can set 6100-6102 ports. Does this help? A similar issue was described in the TC 9.20 consuming high 98% cpu SmartBear forum thread.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文