是否有必要在所有 Windows 操作系统及其所有版本上测试我的应用程序？
我将测试一个声称可以在 Windows XP、Windows Vista 和 Windows 7 上运行的应用程序。我知道我必须在 32 位和 64 位（如果存在）上测试每个应用程序，但我不确定是否有必要测试每个操作系统的每个版本。
例如，如果我已经测试了 Windows 7 Ultimate 或 Home，我是否真的需要测试 Windows 7 Starter？如果我已经测试过 Windows Vista Home Premium，是否还需要测试 Windows Vista Business？依此类推...
测试应该支持的三种风格的每个版本将非常耗时：
- Windows XP Home w/ SP2
Windows XP Professional w/ SP2
Windows Vista Starter
Windows Vista- Windows Vista Home Basic
- Windows Vista Home Premium
- Windows Vista Business
- Windows Vista Enterprise
Windows Vista Ultimate
Windows 7 入门版
- Windows 7 家庭普通版
- Windows 7 家庭高级版
- Windows 7 专业
- 版Windows 7 企业版
- Windows 7 旗舰版
让我知道您的想法。
I will be testing an application that claims to run on Windows XP, Windows Vista, and Windows 7. I know that I have to test the application for each of those on 32-bit and 64-bit (if it exists), but I'm not sure if it's necessary to test each edition of each operating system.
For example, do I really need to test for Windows 7 Starter if I already tested Windows 7 Ultimate or Home? Do I need to test Windows Vista Business if I already tested Windows Vista Home Premium? And so on ...
It would be very time-consuming to test each and every edition of each of the three flavors that are supposed to be supported:
- Windows XP Home w/ SP2
Windows XP Professional w/ SP2
Windows Vista Starter
- Windows Vista Home Basic
- Windows Vista Home Premium
- Windows Vista Business
- Windows Vista Enterprise
Windows Vista Ultimate
Windows 7 Starter
- Windows 7 Home Basic
- Windows 7 Home Premium
- Windows 7 Professional
- Windows 7 Enterprise
- Windows 7 Ultimate
Let me know what you think.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（6）
在我们的工作流程中，我们测试每个平台和架构，而不是每个版本。
例如，在 XP、Vista 和 7、32 位和 64 位体系结构上进行测试。没有必要在同一体系结构上测试 XP Home 和 Professional，除非您的软件的某些功能依赖于仅在 Professional 中存在的功能。
In our workflow we test each platform and architecture, not every edition.
For example, test on XP, Vista, and 7, and 32- and 64- bit architectures. There is no need to test both XP Home and Professional on the same architecture unless some feature of your software depends on a functionality only present in Professional.
这固然很好，但没有必要。谨慎的方法是在边缘情况下进行测试。
例如，如果它可以在 XP SP1 和 SP3 上运行，那么它也可能在 SP2 上运行。如果它适用于 Windows 7 Home Basic 和 Windows 7 Ultimate，那么它也可能适用于 Windows 7 Professional。
运用你的最佳判断力。发布一个“做所有事情！”的答案很容易，但实际上，这是不切实际的。
It would be good, but it is not necessary. A prudent approach would be to test it on the edge cases.
For example, if it works on XP SP1 and SP3, it probably works on SP2. If it works on Windows 7 Home Basic and Windows 7 Ultimate, then it probably works on Windows 7 Professional.
Use your best judgment. Its easy to post an answer that says, "Do Everything!", but in reality, that is not practical.
这需要你的分析。
如果您要使用仅在某些 Windows 版本中可用的 dll 或功能，或者依赖于 SP 中集成的修补程序而不是基础版本中的修补程序，则必须在每个不同版本上进行测试。
但是，我想说在大多数情况下测试您的建议就足够了。
我肯定会测试您列表中的以下版本：
Windows XP Professional w/ SP2 [否]
Windows Vista Starter [是]
Windows Vista Home Basic [否]
Windows Vista Ultimate [否]
Windows 7 Starter [是]
Windows 7 Home Basic [否]
我的理解是：如果它适用于最精简的基本版版本，它将适用于功能更多的版本。
It would require analysis from your part.
If you'd use dll's or features only available in some Windows editions, or rely on Hotfixes integrated in an SP but not in the base edition, you'd have to test on each of the different versions.
However, I'd say in most situations testing what you suggested should suffice.
I would definitely test the following versions from your list:
Windows XP Professional w/ SP2 [No]
Windows Vista Starter [Yes]
Windows Vista Home Basic [No]
Windows Vista Ultimate [No]
Windows 7 Starter [Yes]
Windows 7 Home Basic [No]
My understanding is: If it works on the most stripped basic version, it will work on the the ones that are more feature packed.
家庭/专业/终极/高潮之间的唯一区别是所包含的较大规模的功能。 API 应该是相同的。
The only difference between Home/Professional/Ultimate/Orgasmic would be the larger scale features that are included. The API should be identical.
一个可能的替代方案是跳过测试并简单地发布它。这为您提供了一小群具有各种环境的测试人员，其中一些人会向您报告（可能会发送愤怒的电子邮件或要求退款）。
多年来，我一直处于一个愉快的境地，我基本上拥有一个固定的客户群（这是公司内部的），我的代码要么为他们工作，要么他们报告失败，我会在同一天修复它。他们很高兴能够如此迅速地得到修复；其他部门测试了他们的代码，发布周期很长，但错误并没有减少；如果出现问题，需要很长时间才能修复。
这对你来说可能不是一个好建议，但是（正如我的轶事所示）这将取决于具体情况。如果您不担心惹恼一些用户或损害您的声誉，这可能会让您节省一两个时间。
编辑：
根据您的反馈，您处于（更常见）的情况，这种操作会让您挨打。在这种情况下，我同意其他一些答案的建议，鼓励您测试所有主要版本，而不是不同版本。
作为程序员，理论上您应该了解 Home/Premium/Whatever 版本的区别。据我所知，现在的问题往往是这样的：
在某些情况下，版本的差异归结为存储在 CD 上某个编号中的单个标志......相同的代码，只是切换功能的选项。除非功能子集对您的代码有影响，否则您可能可以安全地忽略它。一个明智的方法可能是使用产品的最低公分母（即“穷人版本”）进行测试，因为
但和往常一样，您的里程可能会有所不同。
A possible alternative is to skip testing and simply ship it. This provides you with a small army of testers with all kinds of environments, some of whom will report to you (with angry e-mails or demands for refunds, perhaps).
For some years, I was in a happy position where I had essentially a captive customer base (this was in-company) and my code either worked for them or they reported on failure and I'd fix it the same day. THEY WERE GRATEFUL to get fixes so quickly; other departments tested their code and had lengthy release cycles but not really fewer bugs; and if something went wrong it took ages to fix.
This may not be good advice for you, but (as my anecdote shows) it would depend on the circumstances. If you're not worried about annoying a few users or tarnishing your reputation, this might allow you to cut a corner or two.
EDIT:
Based on your feedback, you're in the (more common) situation where this kind of operation would earn you a spanking. In that case, I'd agree with the recommendations of some other answers that encourage you to test all major releases but not the different editions.
As the programmer, you should theoretically have a feel for what distinguishes the Home/Premium/Whatever versions. These days, as far as I've seen, that tends to be stuff like:
In some cases, the difference in versions came down to a single flag stored in some number on the CD... identical code, just an option for toggling capabilities. Unless the subset of capabilities has an impact on your code, you're probably safe to ignore it. A sensible approach might be to test with the lowest common denominator (i.e. the "poor peoples' editions") of the product, as that will
But as usual, Your Mileage May Vary.
我从 Microsoft 的 Windows 应用程序兼容性工具包开始，Win 7 版本是 在这里。您应该能够从那里通过 Vista 和 XP ACT 进行回溯。
I'd start with the Windows Application Compatibility Toolkit from Microsoft, the Win 7 version is here. You should be able to back track from there through the Vista and XP ACTs.