blocks|key|1001573|text|如果虚拟机运行的是普通操作系统，则其浏览器应该不会出现任何问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1001574|渲染和性能差异可能会很明显，但无论如何都应该对此进行测试。|1001575|请记住，您的最终用户也可能在VM中浏览您的站点。|1001576|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

If the VM is running a normal OS, there should not be any issues with its browser.
It's possible that rendering and performance differences might be noticeable, but you should test for that anyway.
<h2>Remember that your end-users might also browse your site in a VM.</h2>

blocks|key|3128276|text|VM是最好的方法。其他选项如多IE差异要频繁得多。就个人而言，我们使用Virtual+Box|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3128277|entityMap|0|LINK|mutability|MUTABLE|url|http://www.virtualbox.org/^0|Z|B|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

VM is the best way. Other options like multiple IE differences are much more frequent.
Personally we use
<a href="http://www.virtualbox.org" rel="nofollow noreferrer">Virtual Box</a>

blocks|key|4595648|text|在虚拟机内部运行的操作系统与在实际金属上运行的操作系统没有区别！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4595649|显然，正如您所指出的，操作系统和应用程序配置可能会使并排比较变得困难。|4595650|此外，在虚拟化下可能存在性能差异。这应该不会对浏览器行为产生明显的影响。|4595651|我建议与您的同事一起提出一个操作系统配置黄金副本脚本，您可以在构建虚拟和主机操作系统时遵循该脚本，以解决可能的比较问题。例如：|4595652|4595653|ClearType?|unordered-list-item|4595654|Graphics驱动程序？Version?|4595655|Screen+resolution?|4595656|Fonts+installed?|4595657|Memory?|4595658|Browser+version?|4595659|Browser浏览历史记录？(有关css重置资源，请参阅http://www.west-wind.com/Weblog/posts/490727.aspx+)|offset|length|4595660|4595661|entityMap|0|LINK|mutability|MUTABLE|url|http://www.west-wind.com/Weblog/posts/490727.aspx^0|0|0|0|0|0|0|0|0|0|0|0|S|1D|0|0|0^^$0|@$1|2|3|4|5|6|7|18|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|19|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|1A|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|1B|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]|$1|I|3|J|5|K|7|1D|8|@]|9|@]|A|$]]|$1|L|3|M|5|K|7|1E|8|@]|9|@]|A|$]]|$1|N|3|O|5|K|7|1F|8|@]|9|@]|A|$]]|$1|P|3|Q|5|K|7|1G|8|@]|9|@]|A|$]]|$1|R|3|S|5|K|7|1H|8|@]|9|@]|A|$]]|$1|T|3|U|5|K|7|1I|8|@]|9|@]|A|$]]|$1|V|3|W|5|K|7|1J|8|@]|9|@$X|1K|Y|1L|1|1M]]|A|$]]|$1|Z|3|-4|5|6|7|1N|8|@]|9|@]|A|$]]|$1|10|3|-4|5|6|7|1O|8|@]|9|@]|A|$]]]|11|$12|$5|13|14|15|A|$16|17]]]]

There is no difference between an OS running inside a VM and an OS running on the actual metal!

Obviously, as you point out, OS and app configuration can make a side-by-side comparison difficult.

Also, there are possible performance discrepancies under virtualization. This should not have a measurable affect on browser behavior.

I suggest working with your folks to come up with an OS configuration gold copy script that you can follow when building up both virtual and host OSs that can address possible comparison issues. Eg:

<ul>
<li>ClearType?</li>
<li>Graphics driver? Version?</li>
<li>Screen resolution?</li>
<li>Fonts installed?</li>
<li>Memory?</li>
<li>Browser version?</li>
<li>Browser browsing history? (see <a href="http://www.west-wind.com/Weblog/posts/490727.aspx" rel="nofollow noreferrer">http://www.west-wind.com/Weblog/posts/490727.aspx</a> for css reset resources)</li>
</ul>

blocks|key|1007759|text|我从来没有见过VM中的代码和“真正的”PC上的代码之间的行为差异，我不能直接将其归因于修补底层操作系统之间的差异。同样，我有过在一栋建筑中工作的经验，在那里，只有一台神秘配置的笔记本电脑会表现出奇怪的行为，而且没有其他机器可以做同样的事情。(是的，web应用程序中奇怪的Javascript行为。现在回想起来，我不寒而栗。)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1007760|现在，如果您的代码涉及到测试可能受视频驱动程序工作影响的内容，那么您可能有理由担心。显然，基于VM的方法不会在视频硬件方面给您带来太多变化。然而，对于web应用程序来说，这似乎不太可能是一个问题。|1007761|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I've never seen a behavior difference between code in a VM and code on a "real" PC that I couldn't directly ascribe to patch discrepancies between the underlying operating systems. Similarly, I've had the experience of working in a building where exactly one mysteriously-configured laptop would exhibit weird behaviors, and no other machine could be found to do the same things. (Yes, weird Javascript behaviors in a web application. I shudder now from the memory of it.)

Now, if your code involves testing things that might be affected by the workings of the video driver, then you might have cause for concern. Clearly, a VM-based approach isn't going to give you much variety in terms of video hardware. However, for a web application, that seems unlikely to be an issue.

blocks|key|812307|text|没有什么不同。我们运行跨浏览器测试服务，并对所有基于Windows和Ubuntu的配置使用VMWare+ESXi。虚拟机映像下的浏览器渲染效果与在“真实”操作系统下的渲染效果相同。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|812308|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

There are no differences. We run a cross browser testing service and use VMWare ESXi for all the Windows and Ubuntu based configurations. The browsers under a VM image render just as they would under a 'real' OS.

blocks|key|812343|text|在VM中运行与在真实计算机上运行相比，您可能需要注意的唯一区别是实际的硬件差异。使用VM的一个优点是，所有操作系统组合都将在相同的虚拟硬件上运行-相同的普通VGA“适配器”、相同的普通网络“卡”等。但是，对于测试，这也是一个缺点，因为这意味着您不是在真实的硬件上测试。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|812344|在浏览器中运行的JavaScript通常不应该关心您的硬件，但在某些情况下可能会观察到工件。如果您的JavaScript使用插件、ActiveX控件等高级浏览器功能，或者Flash、Silverlight、OpenGL或Canvas等显示功能，或者视频或音频播放等内容，则您的代码可能会对机器之间的硬件差异敏感，而这些差异在仅在同构虚拟机中测试时并不明显。类似地，如果您的JavaScript正在执行相当低级的有线协议操作(通过XmlHttpRequest发送数据包)，则VM虚拟网络堆栈和实际网卡硬件和驱动程序之间的差异可能会导致数据包到达时间的更改、丢弃数据包，甚至可能导致数据包顺序混乱。|812345|最好的做法是在虚拟机中进行大部分测试，甚至所有的自动化测试，原因很简单，因为这样做更容易管理，也更经济，但也需要预算和计划在完全不同的硬件上进行一些测试-包括超级快速和非常糟糕的视频卡、内置mobo音频以及售后音频卡、uniproc和multiproc系统等。|812346|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

The only differences in running in a VM vs running on a real machine that you may need to watch out for are actual hardware differences. A strength of using a VM is that all OS combinations will be running against the same virtual hardware - the same vanilla VGA "adapter", the same vanilla network "card", etc. For testing, though, that is also a liability, since it means you're not testing against real world hardware.

JavaScript running in the browser normally shouldn't care about your hardware, but there can be situations where artifacts may be observable. If your JavaScript makes use of advanced browser features like plugins, ActiveX controls, or display features like Flash, Silverlight, OpenGL, or Canvas or whatever, or things like video or audio playback, your code may be sensitive to hardware differences between machines that would not be apparent when testing exclusively in homogeneous VMs. Similarly, if your JavaScript is doing fairly low-level wire protocol operations (sending packets of data through XmlHttpRequest), differences between the VM virtual network stack and actual network card hardware and drivers could cause changes in packet arrival timing, dropped packets, or perhaps even out of order packets.

The best course of action IMO is to do most of your testing, perhaps even all of your automated testing, in VMs simply because it's more manageable and more economical to do it that way, but also budget and schedule to do some testing on widely disparate hardware - both super fast and super awful video cards, built-in mobo audio as well as aftermarket audio cards, uniproc and multiproc systems, etc.

I am part of an organization in which there is contention amongst some very competent folks as to whether or not testing cross-browser behavior for JavaScript intensive web applications on virtual machines (for IE6/7/8, FF2/3, Chrome on XP/Vista/7) is reliable. This is using VMWare server on a Linux box host.

While the discrepancies seen are few, there are cases in which it has proven difficult to tell if it is a product of virtualization or just different machine configurations.

My question to the community is, what is people experience with this? Is there any credence to the claim that VM pose inconsistencies, or are they generally spot-on reliable? Can we trust them?

Cross Browser Testing on Virtual Machines - Issues?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我所在的组织中有一些非常能干的人在争论在虚拟机( IE6/7/8，FF2/3，XP/Vista/7上的Chrome )上测试JavaScript密集型web应用的跨浏览器行为是否可靠。这是在Linux机器主机上使用VMWare服务器。虽然看到的差异很少，但事实证明，在某些情况下，很难区分它是虚拟化的产品还是只是不同的机...

问虚拟机上的跨浏览器测试-问题？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问虚拟机上的跨浏览器测试-问题？EN