QTP / 动态大平原自动化
我最近完成了一项关于使用 QTP、TestComplete 和其他 GUI 识别/交互工具进行 GP 功能测试自动化可能性的详细调查。 简而言之，这些工具都没有发挥良好的作用。 上面提到的效果最好，但在录制的示例脚本中仍然存在大量硬编码。 不过，QTP 的表现明显更好。
一些 GUI 在 .NET（QTP 中的 swf...）下被识别并且处理得很好。 其他一些仅被识别为 swfObject，但访问本机方法和属性允许执行所需的交互。
最后，内部名为“Microsoft.Dexterity.Shell.DexDialogHost”的对象呈现的对象似乎没有 Windows 句柄，因此无法被 QTP 识别。 我还没有找到有关这些对象系列的任何详细文档（例如用于查找方法名称的类引用）。
所以我想知道是否有人可以分享自动化 GP 的经验以及使用了哪些工具/方法。
谢谢。
I have recently completed a detailed investigation regarding GP functional test automation possibilities with QTP, TestComplete, and other GUI recognition/interaction tools.
In short, none of the tools acted well. Mentioned above did best but still featured a lot of hard-coding in recorded sample scripts. QTP did significantly better though.
Some of the GUI were recognized under .NET (swf... in QTP) and handled well. Some other were recognized as swfObject only but accessing native methods and properties allowed performing required interaction.
Finally, object internally named "Microsoft.Dexterity.Shell.DexDialogHost" renders objects that seem don't have Windows Handle and thus unrecognizable by QTP. I haven't found any detailed documentation on those objects family (like class reference to find out names of methods).
So I was wondering if someone could share experience automating GP and what tools / approach were used.
Thanks.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
如果 QTP 无法识别某些控件，您可以使用
.NET扩展性来扩展它支持的控件集。 这允许您添加与这些控件相关但 QTP 不支持的新功能。 请注意，需要一些.NET编程。.NET 扩展性的文档可在开始> 处找到。 节目> 快速测试专业版> 扩展性> 文档 > .NET 插件 Windows 窗体扩展性帮助
今日事实： QTP 中
.NET对象名称中的 SWF 代表对于系统系统WindowsF形式。If QTP doesn't recognise some controls you can extend the set of controls it supports by using
.NETExtensibility. This allows you to add new functionality which is relevant for these controls but is not supported out of the box by QTP. Note that some.NETprogramming is required.The documentation for .NET Extensibility is available at Start > Programs > QuickTest Professional > Extensibility > Documentation > .NET Add-in Windows Forms Extensibility Help
Fact of the day: The SWF in
.NETobjects' names in QTP stands for System Windows Forms.对于部分成功的对象，您注意到的那些被识别为 SwfObject - 如果这些对象在逻辑上映射到标准类，您可以配置 QTP 将其视为标准类。 例如，如果您有一个行为类似于按钮的 SwfObject，则可以将 QTP 配置为记录和重播，就好像它是标准按钮一样。
[删除了建议的击键+clipbaord解决方法，因为它不适合这种情况，因为有多个敏捷对话框，每个对话框都有许多对象的进一步信息]
With regards to the objects that were partially successful, the ones you noted were recognized as SwfObject - if these logically map to a standard class, you can configure QTP to treat it as a standard class. For example, if you have an SwfObject that behaves like a button, you can configure QTP to record and replay as if it is a standard button.
[removed suggested keystroke+clipbaord work-around as it is inappropriate for this situation given further information that there are multiple Dexterity dialogs, each with many objects]
我花了一段时间进行研究，然后实际证明了这个概念。
我开始了一系列关于 Great Plains 自动化成功故事的帖子，其中我将调查的所有细节和步骤以及示例代码放在一起。
http://automation-beyond.com/2009/08/24 /great-plains-automation/
http: //automation-beyond.com/2009/08/26/dynamics-great-plains-gui/
http://automation-beyond.com/2009/09/01/gp-automation-utilizing-com/
（待续）
这是摘要。
Microsoft Dynamics Great Plains 拥有自己完全独立的 GUI/事件系统 (Dexterity)，这使其成为跨平台产品。 同样的事情使得它几乎完全是“黑匣子”，无法从外部访问。
特定于平台的引擎支持COM自动化和Windows平台的各种集成模型。 所有这些都集中在 Continuum Integration Library 名称下。
对于测试自动化需求特别有用的是，Continuum 提供了高级方法来模拟 GUI 的用户输入，从而与测试自动化工具的行为方式相同。
只要 Continuum 不能满足测试自动化需求，就可以实时执行 sanScript（Dexterity 的内部脚本语言）的直接调用。
只要
通过上述所有内容，我为 Quick Test Professional 创建了自定义“Dexterity GUI”组件，以实现 Microsoft Dynamics Great Plains 应用程序的功能测试自动化。 当然，无需使用任何键盘/鼠标硬编码解决方法。
谢谢。
It took a while for me to conduct a research, and then practically prove the concept.
I started series of posts about Great Plains automation success story where I put all the details and steps of my investigation along with sample code.
http://automation-beyond.com/2009/08/24/great-plains-automation/
http://automation-beyond.com/2009/08/26/dynamics-great-plains-gui/
http://automation-beyond.com/2009/09/01/gp-automation-utilizing-com/
(to be continued)
Here's the summary.
Microsoft Dynamics Great Plains has its own completely independent GUI/Event system (Dexterity) that makes it cross-platform product. The same thing makes it almost completely "black box" not accessible from outside.
Platform-specific engine supports COM Automation and various integration models for Windows platform. All these are gathered under Continuum Integration Library name.
What is especially useful for Test Automation needs, Continuum provides high-level methods to simulate user inputs for the GUI thus acting the same way as Test Automation Tool does.
Wherever Continuum doesn't cover Test Automation needs, direct calls of sanScript (Dexterity's internal scripting language) could be executed in real-time.
With all the above, I created custom "Dexterity GUI" component for Quick Test Professional enabling functional test automation of Microsoft Dynamics Great Plains application. Of course, without any use of keyboard/mouse hard-coded workarounds.
Thank you.
您可以从 hp 下载 .NET 插件。
链接文本
You can download the .NET Add-In from hp.
link text