我们如何测试我们的Java UI？ [英] How do we test our Java UI?

问题描述

我们正在寻找的记录和回放式的测试工具来自动化我们的一些UI功能测试。
我们已经看过大多数从西尔克到QTP通常的嫌疑人，其中没有工作。
他们都属于当需要右击选择的东西掀起了右键菜单，或者当你要选择在网格中下拉列表中值过。

We're looking at record and playback type test tools to automate some of our UI functional testing. We've looked at most of the usual suspects from Silke to QTP and none of them work. They all fall over when a right click is required to select something off a right click menu, or when you have to choose a value in a drop down list in a grid.

有谁知道能不能处理这种类型的用户界面的任何工具？

Does anyone know any tools that can handle this type of UI?

推荐答案

你说的是一个独立的Java应用程序，或者是基于网络的，与Java在服务器上，但HTML传递到客户端？

Are you talking about a stand-alone Java application, or is it web-based, with Java on the server, but HTML delivered to the client?

假设它是一个独立的Java应用程序，SilkTest中和QTP应该与Java发挥很好。 （您是否使用支持Java适当的Java附加/插件吗？QTP有一个单独的外接的Java支持。）另一种工具来考虑的将是IBM的Rational Functional Tester。它的建成使用Java和Java应用程序运行良好。我使用所有的3把刀具，虽然从来没有在SilkTest中Java应用程序。根据我的经验，QTP和RFT都与Java应用程序表现良好。

Assuming it's a stand-alone Java application, SilkTest and QTP ought to play nicely with Java. (Are you using the appropriate Java add-in/plugin for Java support? QTP has a separate add-in for Java support.) Another tool to consider would be IBM Rational Functional Tester. It's built in Java and works well with Java apps. I've used all 3 tools, though never SilkTest on a Java app. In my experience, both QTP and RFT performed well with Java apps.

话虽如此，在每个测试自动化项目中，有将是不开箱与所选的自动化工具，工作带来极大的UI控件。 （第三方控件通常是罪魁祸首）。在这些情况下，您将需要手动code一个变通。在预期不工作的权利，点击的例子，我经常需要放弃点击赞成使用按键选择所需项目的选择从右键菜单中的项目。这到底是什么指向的是你不得不放手记录/回放的概念是自动化的有效手段。

That having been said, on every test automation project, there are going to be UI controls that do not work great out of the box with the selected automation tool. (3rd party controls are usually the culprit). In these cases, you will need to manually code a work-around. In the example of right-clicks not working as expected, I have often needed to forego clicking to select an item from a right-click menu in favor of using keystrokes to select the desired item. What this really points to is that you have to let go of the notion of record/playback being an effective means of automation.

此外，它可能是有益的，为您张贴记录，并在该行失败，选择有问题的项目的实际code。实际的脚本code可以给我一些线索，什么是真正回事。

Additionally, it might be instructive for you to post the actual code that was recorded, and at which line it fails to select the item in question. The actual script code could give me some clues as to what is actually going on.

这篇关于我们如何测试我们的Java UI？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！