iPhone 测试自动化 - 基准测试工具？
你好 我们正在扩大我们在一家大型银行的项目之一，以包括通过移动设备进行访问。我们正在评估一些工具 - Inc.完美移动、专家测试和设备无处不在。 从我们最初的评估来看，perfecto 和 device Anywhere 涵盖了更多的手机（包括功能手机）。另一方面，Experitest 功能强大且易于使用智能手机（iPhone、Android 等）进行操作。 有人可以分享在大型项目中使用这些工具的经验吗？我们主要关注稳定性、与 QTP 配合使用的能力以及支持注意事项（对新设备的支持等）。
Hi
we are expanding one of our projects in a major bank to include access via mobile devices. We are evaluating a few tools - inc. perfecto mobile, experitest and deviceanywhere.
From our initial evaluation perfecto and device anywhere cover a larger set of handsets inc feature phones. Experitest on the other hand is strong and simple to operate with smartphones(iphone, android etc).
Can anyone share experience from using these tools for large scale projects? we are mainly concerened re stability, ability to work with QTP and support considerations (support for new devices etc).
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（6）
据我所知，Perfecto Mobile 对其产品进行了一些重大改进，目前提供了一些优于其他产品的主要优势，包括价格。在过去的几个月里，他们添加了 Lenovo nePaone 等流行设备。您可以在他们的网站上查看完整列表：www.perfectomobile.com。由于他们使用与 Device Anywhere 不同的控制技术，因此他们能够非常快速地支持新设备。在稳定性和 QTP 方面，他们也比其他公司有很多优势。例如，用于记录您自己的特定用户场景并跨设备重复测试它们的工具 - 对于大型项目来说，这是一个很棒的自动化工具。
To the best of my knowledge Perfecto Mobile has made some major improvments to its offering and currently offers some major benefits over the others, including price. In the last few months they've added popular devices like Lenovo nePaone. You can see the full list om their website:www.perfectomobile.com. Since they use differentontrol technology than Device Anywhere they are capabable of supporting new devices really quickly. Regarding stability and QTP they also have many advantages over the others. For instance, tools to record your own specific user scenarios and test them repeatedly across devices - this is a great automation tool for large scale projects.
如果您正在测试银行应用程序，您应该考虑安全问题。
如何保护您的应用程序和应用程序数据。一旦你释放了手机，其他人就可以控制它。
我的建议是使用我相信上述所有解决方案都具备的现场功能。
If you are testing bank application you should consider the security issue.
How do you protect your application and application data. Once you release a phone, someone else can get control over it.
My recommendation is to use the on-site capabilities I believe all the above solutions have.
我广泛使用过 DeviceAnywhere。 Perfecto，在经历了相当令人失望的试用期之后，并没有那么多。 DA 有 QTP 和 QC 的支持/插件。 Perfecto 不涵盖 QC。 Perfecto 并不比 DA 快，因为他们的大部分设备都在以色列，而不是美国。 DA 在美国和国外拥有多个数据中心，因此您有更好的机会获得更好的性能。 DA 拥有相当长的企业和运营商客户名单……而 Perfecto 似乎是一家非常小的公司。比较他们的网站质量 - 很明显哪个看起来更专业...您应该尝试它们并做出决定...
I have used DeviceAnywhere extensively. Perfecto, not that much, after a pretty dissapointing trial period. DA has support/add-ins for QTP and QC. Perfecto does not cover QC. Perfecto is not faster than DA, since most of their devices are in Israel, and not the US. DA has a few datacenters in the US and abroad, hence you have a better chance to get better performance. DA has an pretty long list of Enterprise and Carrier customers...while Perfecto seems like a very small company. Compare their website quality-it's pretty obvious which one looks more professional...You should try them both and make up your mind...
我已经多次使用这 3 个平台，
只有 Perfecto Mobile 和 DA 对于真正的测试人员来说足够强大（至少对于企业级）。
DA 有更多设备，但 Perfecto 100% 基于网络，速度更快，而且便宜得多。两者都提供自动化环境，各有利弊，但 Perfecto 提供 QTP 集成和增强的安全解决方案
结论 - 两个系统都很好，Perfecto 更便宜，Perfecto 对于从事移动测试的企业来说更好。
吉多
I have used all 3 platforms many times
Only Perfecto Mobile and DA are robust enough for real testers (at least for enterprise level).
DA have more devices but Perfecto are 100% web based, faster and MUCH cheaper. Both offer automation environments with pros and cons but Perfecto offers QTP integration and enhanced security solutions
Conclusion - both systems good, Perfecto cheaper, Perfecto much better for enterprises engaging in mobile testing.
Guido
考虑将标准软件远程控制产品与标准软件测试机器人（如 QTP）结合起来。
作为替代方案，并且基本上设备独立，但是依赖于位图的解决方案，您可以使用众多遥控器之一将移动设备的显示内容带到桌面。然后，您可以使用您最喜欢的测试机器人在远程控制窗口中“单击”。
听起来很愚蠢吗？好吧，它有它的优点和缺点：
如果为您设置了 QTP，您将陷入位图同步，看不到其他有用的 GUI 属性。但是，如果您掌握了一些 QTP 专业知识，则可以通过 QC、测试数据寻址等重用所有测试管理集成的专业知识，编写“艺术”脚本，例如等待正确的事情、将位图转换为文本等等。您甚至可以“实时”验证移动设备上显示的结果以填充到公司后端，或者在移动设备上进行一些交易后在某些中央数据库中研究预期结果 - 所有这些都会很容易，因为您的测试机器人运行为始终是 IT 基础设施的一部分，因此可以轻松访问这些资源。这些访问可以通过我们习惯的基于 PC 的测试机器人轻松完成，例如 QTP 的数据库检查点。
积极的方面是：使用这样的场景，您在很大程度上独立于移动设备的技术细节，并且可以通过仅使用不同的预期位图集来支持许多不同的设备。 （假设工作流程完全相同，当然情况并非总是如此。）
如果您不必购买额外的测试机器人，那么这个解决方案可能非常便宜。例如，大多数 Windows 移动设备都可以与 Microsoft 的免费远程控制一起使用，并且有许多商业供应商在一个软件包中为各种设备提供远程控制功能。
此外，您还可以使用模拟移动设备的模拟器来开发测试脚本，因为测试机器人无法知道从真实设备获取的显示或由模拟器显示的显示之间的区别。
我已经使用各种遥控器和 PDA/智能手机设备完成了所有这些工作，并使用 CitraTest 或 QTP 作为测试机器人。我很高兴不必再使用另一种专用工具，甚至不止一个工具，每个工具都有自己的语言或方法。
除了已经提到的障碍之外，最大的障碍是：
不过，这是可行的，而且这样的解决方案非常稳定和可靠，在测试维护工作方面具有足够的成本效率（当然，这取决于应用程序测试中的更改频率）。
Think of coupling a standard software remote control product with a standard software test robot (like QTP).
As an alternative, and being a mostly device-independent, but bitmap-dependent solution, you could use one of the many remote controls to bring the mobile's display contents to the desktop. Then, you'd "click around" in that remote control window using you favourite test robot.
Stupid that sounds? Well, it has its strong and its weak points:
If QTP is set for you, you'd be stuck on bitmap synchronization, no other useful GUI properties would be visible. However, if you have some QTP know-how on board, you could reuse all the know-how for test management integration via QC, test data addressing, and so on, scripting "art" like wait-for-the-right-thing, convert bitmaps to text, and so on. You could even "in real time" verify the results displayed on the mobile to stuff in the corporate backend, or research expected results in some central database after doing some transaction on the mobile -- all that would be easy since your test robot runs as part of the IT infrastructure all the time, so it has easy access to those resources. And those accesses could be done with all the comfort we got used to on PC-based test robots, like for example QTP's database checkpoint.
The positive aspect would be: Using such a scenario, you are largely independent of the mobile's technical details, and could support a lot of different devices by just using different sets of expected bitmaps. (Provided the workflows are exactly the same, which of course is not always the case.)
If you don't have to buy an extra test robot, this solution might be unbeatable cheap. Most Windows mobile devices for example can be used with Microsoft's free remote control, and there are lots of commercial vendors offering remote control functionality for a variety of devices in one package.
Also, you could develop test scripts using emulators emulating the mobile device, because the test robot would not know the difference between a display being fetched from the real thing, or being shown by the emulator.
I've done all that with various remote controls and PDA/smartphone devices, using CitraTest or QTP as the test robot. I was very happy not having to mess around with yet-another-specialized tool, or even more than one of them, each with their own language, or methodology.
Biggest hurdles besides the ones already mentioned were:
It's feasable, though, and such a solution can be very stable and realiable, with a sufficient grade of cost-efficiency in terms of test maintenance effort (depending on what changes how frequently in the app-to-test, of course).
jQuery 在功能手机和智能手机，也许你可以使用他们的测试系统。作为旁注，检查 jQuery mobile 是否适合您，它看起来非常酷。
jQuery runs a lot of tests automatically on both feature phones and smart phones, maybe you can use their test system. As a side note, check if jQuery mobile is for you, it seems very cool.