Web Services on Devices Testing Prerequisites
This section describes the tasks that you must complete before you test a Web Services on Devices (WSD)-compliant device by using the Windows Hardware Certification Kit (Windows HCK):
Review the hardware requirements.
Review the software requirements.
Configure the test computers.
Hardware requirements
The following hardware is required for testing WSD compliance. Additional hardware may be required if the test device provides bus-specific support. See the test description for each bus-specific test to determine whether there are additional hardware requirements.
Basic Windows HCK test setup (Controller and Studio). See Windows HCK Getting Started.
Two test computers. For testing networking capabilities, the computer that the WDS-compliant device test device is physically attached to is referred to as the System Under Test (SUT) computer and the other computer is referred to as the support computer.
Note
All computers must meet the Windows HCK requirements. For more information, see Windows HCK Prerequisites.
One WDS-compliant device to be tested.
One wireless network card that supports SoftAP (for example, a D-Link WDA-1320 Desktop Adapter) and a Wireless router if the test printer includes wireless networking capabilities.
One stand-alone network adapter (if the test computer does not include an integrated network adapter) and an Ethernet hub or switch if the test scanner includes network printing capabilities.
One USB cable and one USB 3.0 hub for testing a device that includes support for USB 3.0 or a USB 2.0 hub for testing a device that supports USB 2.0.
Note
Testing a device for Server Device certification requires that the system that is being used to test the device supports four processors and a minimum of 1 GB of RAM. These system capabilities are required for testing the device and driver for their Rebalance, D3 State and Multiple Processor Group functionality. You do not need a computer that has more than 64 processors to test your device.
If a pool of test computers is used to test devices, at least one computer in the pool must contain four processors and a minimum of 1 GB of RAM. Additionally, that computer must contain the device and driver that is being tested. As long as the driver is the same on all computers in the pool, the test will be created to run against all computers.
For those tests that do not include a driver to test, such as testing a hard disk drive, the Windows HCK scheduler will require the tests that validate the device’s and driver’s Rebalance, D3 State and Multiple Processor Groups functionality to run on the default computer. This computer should also be manually configured to have multiple processor groups. The default computer is the first computer listed. Test personnel, in this case, should ensure that this first computer meets these minimum hardware requirements.
Note
Except for para-virtualization drivers (as defined by Logo Program Requirement Policy-0020), physical devices and their associated drivers being tested for a server certification or signature may not be tested in virtual machines using any form of virtualization. This is because not all virtualization products support the underlying functionality that is required to pass the tests that relate to Multiple Processor Groups, Device Power Management, Device PCI functionality, and so on.
Software requirements
The following software is required to run the WSD tests:
The driver for the test device if the device does not include an inbox driver.
The latest Windows HCK filters or updates.
Test computer configuration
To configure the test computer for WSD testing, follow these steps:
Install the appropriate Windows operating system on the test computers.
Configure the computers for your test network (the network that contains the Windows HCK Studio and Windows HCK Controller.
Connect both the SUT and the support computer to an Ethernet switch or hub to test wired networking capabilities of your WSD-compliant test device. Connect a wireless router to the support computer to test wireless capabilities.
Attach the WSD-compliant test device to the SUT using a USB cable.
Install the manufacturer-supplied device driver, if you have to, on the test computer.
Check that the WSD-compliant test device is visible from Device Manager on the SUT.
Install the Windows HCK client application on the SUT.
Create a machine pool by using Windows HCK Studio and move both the SUT and the support computer to that pool.
Make sure that the test computer is in the ready state before you begin your testing. If a test requires parameters to be set before it is run, a dialog box will be displayed for that test. Review the appropriate test topic for more information.
Some Windows HCK tests require user intervention. When running tests for a submission, it is a best practice to run the automated tests separately from manual tests. This prevents a manual test from interrupting the completion of an automated test.
WSD testing on WSD print and scan devices
PnPX and Vertical Pairing features are required for WSD devices. If you are testing your device over Ethernet, you need to manually add the Device.Connectivity.PnPX feature. If you are testing your device over WiFi, you need to manually add the Device.Connectivity.VerticalPairing feature.
To manually add a feature, follow these steps:
In the HCK Client, choose the Selection tab.
Select Show Selected in the left-hand menu.
Right-click a selected devnode, and then select Show Features.
Select the Device.Connectivity.PnPX or Device.Connectivity.VerticalPairing feature.