什么是真正之间的设备和模拟器/仿真器的区别? [英] What's the difference between real device and simulator/emulator?

查看:359
本文介绍了什么是真正之间的设备和模拟器/仿真器的区别?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

近日在QCon大会,杰拉德梅萨罗斯说,我们应该只在模拟器上运行的自动化测试,以提高效率。我们也正在考虑有关移动自动化测试。但我不知道是否会有一些问题,只能在真实设备发现的?还是喜欢拍照的一些组件,重力感应器不能在模拟器/仿真器测试?谢谢!

编辑:

您可以在这里找到Gerard的幻灯片:的http://www.slideshare.net/pinot_noir/ensuring-quality-in-cloud-and-mobile-applications.

我通过幻灯片阅读一次我发现我误会了他的观点。他真正的意思是,我们应该尽量避免在硬件(第41页)调试。他还提到,我们可以陷阱传出请求传感器和其他服务,再注入从他们的响应。也许我们可以挑选一些案件不能在模拟器进行全面的测试,然后与实际设备进行测试。

感谢您对您的所有意见! :)


解决方案

  

近日在QCon大会,杰拉德梅萨罗斯说,我们应该只在模拟器上运行的自动化测试,以提高效率。


这是奇怪的意见,如果这是真的什么梅萨罗斯先生说。在模拟器上运行测试是好的,但只是一种过度的建议。有一个在运行中的设备自动化测试没有坏处,你可以这样做学到很多东西。


  

但我不知道是否会有一些问题,只能在真实设备发现的?


当然。


  • 很多设备具有多核心CPU,而仿真器只有在这个时候模拟单核

  • 设备存储往往跑慢了很多比在模拟器上不存储

  • 设备制造商与Android在鼓捣不会运行Android的股票
  • 仿真器显示方式
  • 只有松散的模拟硬件相关的电力,互联网(例如,没有移动数据,没有WiFi),GPS,传感器,相机等。该模拟器

  • 模拟器不支持某些设备的能力,如地图,Play商店,在Android 4.2多个帐户,等新的版本V2

等。


  

还是喜欢拍照的一些组件,重力感应器不能在模拟器/仿真器测试?


那些的是难以以自动方式进行测试,期

Recently in QCon, Gerard Meszaros said that we should run automation tests only on simulators to improve efficiency. We are also considering about the mobile automation test. But I'm not sure if there will be some issues that can only found in a real device? Or some components like camera, gravity sensors could not be tested in a simulator/emulator? Thanks!

Edit:

You can find Gerard's slides here: http://www.slideshare.net/pinot_noir/ensuring-quality-in-cloud-and-mobile-applications.

I read through the slides again and I found that I misunderstood his point. What he really means is that we should try to avoid debugging on the hardware (page 41). And he also mentioned we could trap outgoing requests to the sensors and other services, then inject the response from them. Maybe we can pick some cases that couldn't be fully tested in simulator and then test it with real devices.

Thank you for all your comments! :)

解决方案

Recently in QCon, Gerard Meszaros said that we should run automation tests only on simulators to improve efficiency.

This was odd advice, if that is really what Mr. Meszaros said. Running tests on the emulator is fine, but "only" is an excessive recommendation. There is no harm in running automated tests on devices, and you can learn a lot from doing so.

But I'm not sure if there will be some issues that can only found in a real device?

Of course.

  • Many devices have multi-core CPUs, whereas the emulator only emulates a single core at this time
  • Device storage tends to run a lot slower than does storage on the emulator
  • Device manufacturers tinker with Android in ways that will not appear on an emulator running stock Android
  • The emulator only loosely emulates hardware related to power, Internet (e.g., no mobile data, no WiFi), GPS, sensors, camera, etc.
  • The emulator does not support some device capabilities, like the new V2 version of Maps, the Play Store, multiple accounts on Android 4.2, etc.

And so on.

Or some components like camera, gravity sensors could not be tested in a simulator/emulator?

Those ones are difficult to test in an automated fashion, period.

这篇关于什么是真正之间的设备和模拟器/仿真器的区别?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆