这两天对即将发布的产品做了个Velocity Test,其定位应该属于兼容性测试。测试的过程倒是比较简单,装上相应微软提供的工具,做好一些前期的准备工作,直接运行就行了,中间几乎无需人为介入,只是考机非常耗费时间,整个测试过程大概需要花费3至4个小时左右。测试结束,对Velocity Testing做个简单的总结。
一. 什么是 Velocity Testing?
引用一下微软在Velocity Test Suit介绍文档中提及的概念:
It provides guidelines for original equipment manufacturers (OEMs) to precisely measure (as well as baseline) OS performance, and quality of manufacturing images, based on the following criteria:
1. Device Compatibility
2. Application Compatibility
3. Performance (Responsiveness, boot time, sleep/hibernate/resume time etc)
4. Power Management
上述概述中precisely一词很好的定位了此测试的精度性,从而可以肯定的是Velocity测试的进行还是极具有参考意义的。
二. Velocity Testing到底测试些什么?
该测试主要关注三个方面:Performance、Reliability、Security,细分如下:
1. Performance
| Criteria | Test | Note |
| Performance | Boot Complete | Important determinant of user experience |
| Shutdown | How fast machine goes off - Important determinant of user experience | |
| Suspend | How fast machine goes into sleep - Important determinant of user experience | |
| Resume | How fast machine resumes from sleep - Important determinant of user experience | |
| IE Launch Time | How fast until I can surf the web – Time to warm launch of IE to a blank page | |
| Disk Flush Check | Test for a common hard disk performance issues |
2. Reliability
| Criteria | Test | Notes | |
| Reliability | Driver Verifier Check | Verify correct driver implementation and behavior. Common source of reliability problems | |
| Driver Signature Check | Unsigned drivers can adversely impact boot time. Signatures are a logo requirement | ||
| Driver Update Check | Tests for latest drivers on system except where latest version has significant quality issues or was released too close to image lock to allow good-faith effort to include update | ||
| Pre-Installs Check | Tests for latest software on system except where latest version has significant quality issues, or was released too close to image lock to allow good-faith effort to include update | ||
| Compatibility Check | Checks for Windows Vista compatibility of all pre-installs | ||
| Check for BIOS String or other marker | Necessary to check systems accurately via OCA |
3. Security
| Criteria | Test | Notes | |
| Security | Service Pack and Security Update Check | Latest service pack installed on | |
| Firewall Enabled | Checks for Windows firewall (or other replacement) enabled after OOBE and enabled after OOBE | ||
| UAC Enabled | Checks for User Account Control feature enabled after OOBE | ||
| Defender Enabled | Windows Defender (or replacement) enabled after OOBE | ||
| Security Integrity Check | Checklist of 6 manual tests to help assure safe usage experience |
三. Velocity Testing的使用场合
1. PC的OEM厂商,如DELL、HP、Lenovo在发布产品前对整个系统(包含硬件和软件)做的Velocity测试,以调优。
2. 软件公司可进行两次Velocity测试,一次是未安装发行软件,一次是安装了发行软件,对比两次测试结果,从而来考核发布软件对目标机器是否存在性能上的显著影响。这一点更趋向于兼容性测试范畴。
3. 个人用户如果购置了新机后也可进行该测试,可以有效检验机器性能是否能达到了微软的要求,以此验证PC厂商有没有忽悠目标用户。
四. 微软的其他同类测试
除了Velocity Testing,微软还提供了另外两种类似的测试种类Logo Testing、OEM Ready Testing,具体的区别参看下图:

五. 其它
在Velocity测试开展前,要进行一些相应的准备工作,在测试过程中可能还要处理蓝屏异常,等等相关操作可参考微软提供的文档“Velocity_Test_Suite_Standalone_Edition_v4.xps”。
另外微软官网上有一份主题是“The Vista Velocity Program“的PPT,很详细的描述了该测试的技术细节,以及其他相关类似测试的对比,可点击这个链接进行下载!
本文详细介绍了Velocity测试的内容,包括它的定义、测试的主要方面(性能、可靠性和安全性),以及它适用于哪些场合。Velocity测试由微软提供,旨在帮助PC制造商、软件公司和个人用户评估系统的性能和兼容性。
1234





