In prior articles I have described how to create custom Windows installer packages from a template. I explained the value of having a template for creating Windows Installer files and how using iTest for creating automated, repeatable checks can make automated, reusable diagnostic tests easier and faster to write and run. In this article I will describe the benefits of using iTest for Windows and how to use it to automate Windows diagnostic testing.
Using iTest in Windows server mode offers several advantages over the more common method of testing software in Windows test environment. When used in server mode, iTest displays figure results as a graphical display, or as a list of items in an array. Figure results can be viewed in different styles, including legend style, grid, pie, and other layouts. When running the software, in server mode, you can select the appropriate figure to display and then move the mouse over each item in the array to get details of the particular test that was run on that item. You can even drill down into individual items to view the individual test results.
Another important advantage of using more it is that it supports parallel testing. With parallel testing, multiple devices can be simultaneously tested using iTest - one device at a time. It is also easy to determine which specific device was used for a particular test. Using iTest for Windows server mode allows testers to easily determine if a specific server method was used for a specific test.