DTM测试环境配置步骤

合集下载

如何进行测试环境的部署与配置

如何进行测试环境的部署与配置

如何进行测试环境的部署与配置在软件开发过程中,测试环境的部署与配置起着至关重要的作用。

测试环境的正确配置可以确保软件在不同环境中的正常运行和高质量。

如何进行测试环境的部署与配置成为了开发团队中一个重要的课题。

测试环境的部署需要选择合适的硬件和软件基础设施。

选择合适的硬件可以保证测试环境的性能和稳定性。

在选择服务器的时候,要考虑到测试环境的规模和所需的资源。

如果需要进行大规模的性能测试,可能需要使用高性能的服务器。

对于小规模的测试环境,一台普通的服务器就可以满足需求。

还需要选择合适的操作系统、数据库和网络设备。

这些软件基础设施的选择应根据项目的需求和团队的技术水平来确定。

测试环境的配置需要进行一系列的操作。

需要在选择的硬件上安装操作系统。

操作系统的安装过程中,要根据实际需求选择合适的版本和配置选项。

安装完成后,还需要对操作系统进行一些基础的配置,如网络设置、用户权限等。

接下来,需要安装和配置数据库。

数据库的选择应根据项目的需求来确定,常见的包括MySQL、Oracle、SQL Server等。

在安装数据库之后,还需要创建数据库和表结构,并进行相关的权限设置。

除了硬件和软件基础设施的配置外,还需要进行环境变量的设置。

环境变量可以影响软件的运行环境和行为。

在测试环境中,可能需要设置一些特定的环境变量,如数据库连接信息、日志路径等。

通过设置环境变量,可以为软件提供正确的运行环境,并减少问题的产生。

测试环境中也需要安装和配置版本控制工具。

版本控制工具可以帮助团队管理代码的版本和变更。

常见的版本控制工具有Git、SVN等。

在安装和配置版本控制工具后,团队成员可以通过提交和更新代码来共享和管理代码的变更。

版本控制工具的使用不仅能够提高代码的可维护性和追踪性,还可以方便团队成员之间的协作和合作。

测试环境的部署与配置还需要考虑安全性和监控。

测试环境中的数据和代码可能包含敏感信息,需要采取一些安全措施来保护。

常见的安全措施包括对数据库和服务器进行访问权限管理、加密传输、防火墙设置等。

自动化部署过程中的测试环境和预生产环境搭建指南(一)

自动化部署过程中的测试环境和预生产环境搭建指南(一)

自动化部署是现代软件开发过程中的一个关键步骤,它可以大大简化软件交付过程和减少人为错误。

而在自动化部署过程中,测试环境和预生产环境的搭建是至关重要的,它们可以提供一个稳定和可靠的环境,用于测试和验证软件的功能和性能。

本文将为您提供一个关于测试环境和预生产环境搭建指南的综合指导。

一、测试环境的搭建测试环境是用于开发团队和测试人员测试软件的一个平台。

它需要能够模拟生产环境的各种因素,例如硬件、软件配置、网络环境等。

以下是测试环境搭建的一些关键步骤:1. 选择合适的硬件平台:测试环境需要有足够的计算资源和存储容量来支持软件的测试。

根据软件的需求,选择合适的硬件平台,并确保系统的性能和容量能够满足测试的需求。

2. 安装操作系统和软件:根据软件的兼容性要求,选择合适的操作系统版本,并在测试环境中安装所需的软件。

确保软件的版本和配置与生产环境保持一致,以便更好地模拟真实的用户环境。

3. 设置网络环境:测试环境需要与其他系统和网络进行交互,因此需要配置合适的网络环境。

可以使用虚拟网络技术来模拟复杂的网络拓扑和场景,以确保软件在各种网络条件下的性能和稳定性。

4. 准备测试数据:测试环境需要与真实的数据进行交互,因此需要准备合适的测试数据。

根据软件的功能和性能测试需求,生成适当的测试数据并导入到测试环境中,以保证测试的准确性和完整性。

二、预生产环境的搭建预生产环境是在软件交付之前进行最后的验证和测试的一个环境。

它需要与生产环境尽可能接近,以确保软件在交付给用户之前的质量和稳定性。

以下是预生产环境搭建的一些关键步骤:1. 复制生产环境:预生产环境应该与生产环境的硬件配置和软件版本尽可能一致。

通过复制生产环境的硬件和软件配置,可以更好地模拟真实的用户环境,并确保软件在预生产环境中的表现与生产环境一致。

2. 配置和优化环境:预生产环境需要进行一些额外的配置和优化,以确保软件的性能和可靠性。

例如,可以对系统进行调优,优化存储和网络性能,以及配置合适的安全设置,以提高系统的安全性和可用性。

测试环境搭建流程

测试环境搭建流程

测试环境搭建流程在进行软件开发过程中,测试环境搭建是非常关键的一步。

一个完善的测试环境可以有效地保障软件质量,提高开发效率。

下面,我们将介绍测试环境搭建的流程,希望能够对大家有所帮助。

1. 确定测试环境需求。

在开始测试环境搭建之前,首先需要明确测试环境的需求。

这包括硬件设备、操作系统、数据库、中间件、网络配置等方面。

根据项目的实际情况,确定测试环境所需的各项配置和规格。

2. 硬件设备采购。

根据测试环境需求,确定所需的硬件设备配置,并进行采购。

这包括服务器、存储设备、网络设备等。

在采购过程中,需要考虑设备的性能、稳定性和可扩展性,以满足测试环境的需求。

3. 操作系统安装和配置。

根据项目需求,选择合适的操作系统,并进行安装和配置。

在安装过程中,需要注意系统的版本和补丁更新,以保证系统的稳定性和安全性。

同时,还需要进行相关的网络配置、用户权限设置等工作。

4. 数据库和中间件安装和配置。

根据项目需求,选择合适的数据库和中间件,并进行安装和配置。

在安装和配置过程中,需要注意版本的兼容性和配置参数的调优,以保证数据库和中间件的稳定性和性能。

5. 测试工具安装和配置。

根据项目需求,选择合适的测试工具,并进行安装和配置。

这包括性能测试工具、自动化测试工具、监控工具等。

在安装和配置过程中,需要注意工具的版本和参数设置,以满足测试需求。

6. 网络配置和安全设置。

进行网络配置和安全设置是测试环境搭建的重要环节。

需要设置网络地址、子网划分、防火墙规则等,以保证测试环境的网络通信和安全性。

7. 系统集成和测试。

完成上述步骤后,进行系统集成和测试。

这包括系统组件的集成、功能测试、性能测试、安全测试等。

通过系统集成和测试,验证测试环境的稳定性和可靠性。

8. 环境文档编写和培训。

最后,对测试环境进行文档编写和培训。

编写测试环境的配置文档和操作手册,培训相关人员对测试环境的使用和维护,以保证测试环境的长期稳定运行。

通过以上流程,我们可以完成一个完善的测试环境搭建工作。

软件测试中的测试环境搭建与管理

软件测试中的测试环境搭建与管理

软件测试中的测试环境搭建与管理一、引言在软件测试过程中,测试环境的搭建与管理是非常重要的一项任务。

测试环境的搭建与管理是为了模拟真实的软件运行环境,以便进行各种测试活动,包括功能测试、性能测试、安全测试等。

本文将介绍软件测试中的测试环境搭建与管理的相关内容。

二、测试环境搭建1. 硬件设备准备在进行测试环境搭建之前,首先需要准备相应的硬件设备。

这包括计算机、服务器、网络设备等。

根据测试需求,确定所需硬件设备的类型、数量和配置要求。

2. 软件安装与配置在确定硬件设备后,需要进行软件的安装与配置。

根据测试需求,选择合适的操作系统、数据库、应用程序等软件,并按照规定的步骤进行安装与配置。

3. 网络搭建测试环境中的设备通常需要进行网络连接,以实现各个设备之间的通信。

根据测试需求,进行网络的搭建与配置,确保各个设备间的通信畅通。

4. 数据准备在进行软件测试时,通常需要使用一些测试数据。

根据测试需求,确定所需的测试数据,并进行相应的准备工作,包括数据的采集、整理和导入等。

三、测试环境管理1. 环境配置管理测试环境的配置管理是指对测试环境的各种配置信息进行管理,包括硬件配置、软件配置、网络配置等。

通过配置管理工具,可以对测试环境进行版本控制、变更管理等,确保测试环境的稳定性和一致性。

2. 环境访问控制为了保护测试环境的安全性,需要对测试环境进行访问控制。

只有经过授权的人员才能够对测试环境进行访问和操作。

可以通过账号、密码、权限等方式实现环境的访问控制。

3. 环境监控与维护测试环境的稳定性和可用性对测试工作的顺利进行至关重要。

因此,需要对测试环境进行监控和维护。

监控测试环境的硬件设备、软件运行情况,及时发现并解决问题,确保测试环境的正常运行。

4. 环境复制与恢复在进行某些测试活动时,可能需要对测试环境进行复制和恢复操作。

比如测试某个特定场景时的环境快照,或者在测试出现问题时的环境恢复等。

通过环境的复制与恢复,可以提高测试的效率和质量。

dtm 串级控制使用流程

dtm 串级控制使用流程

dtm 串级控制使用流程下载温馨提示:该文档是我店铺精心编制而成,希望大家下载以后,能够帮助大家解决实际的问题。

文档下载后可定制随意修改,请根据实际需要进行相应的调整和使用,谢谢!并且,本店铺为大家提供各种各样类型的实用资料,如教育随笔、日记赏析、句子摘抄、古诗大全、经典美文、话题作文、工作总结、词语解析、文案摘录、其他资料等等,如想了解不同资料格式和写法,敬请关注!Download tips: This document is carefully compiled by theeditor. I hope that after you download them,they can help yousolve practical problems. The document can be customized andmodified after downloading,please adjust and use it according toactual needs, thank you!In addition, our shop provides you with various types ofpractical materials,such as educational essays, diaryappreciation,sentence excerpts,ancient poems,classic articles,topic composition,work summary,word parsing,copy excerpts,other materials and so on,want to know different data formats andwriting methods,please pay attention!1. 系统配置确定被控对象和控制目标。

选择合适的传感器和执行器,并将其连接到控制系统中。

实验十六 DTM模型讲解

实验十六 DTM模型讲解

7.5 GRD模型
③、单击标注为“3”处的“线参数”按钮,系统将弹出修改线参数对 话框,以供我们修改结果文件的线型, 如图;
7.5 GRD模型
④、将标注为“4”处的“等 值线光滑处理”打“√” ,并将光滑度选择为“高 程度” ; ⑤ 、将标注“5”处的“制 图幅面”改为“原始数据 范围”; ⑥、双击标注“6”处的颜色 ,系统弹出颜色表,如右 图,以供我们修改相应等 高线的颜色,不过一般情 况下默认就可以了
实验十六
DTM模型
数字地形模型(DTM)

Digital Terrain Model,是数字形式表示的地 表面,即区域地形的数字表示,它是由一系列地 面点的X,Y位置及其相联系的高程Z所组成。这 种数字形式的地形模型是为适应计算机处理而产 生的,又为各种地形特征及专题属性的定量分析 和不同类型专题图的自动绘制提供了基本数据。 在专题地图上,第三维Z不一定代表高程,而可代 表专题地图的量测值,如地震烈度、气压值等。
7.5 GRD模型
下面依次来说明上图中7 个标注的作用: ①、将标注为“1”处的“等 值线套区”打“√”; ② 、单击标注为“2”处的“ 等值层值”按钮,系统会 弹出一对话框 ,如右图 ;

这里我们可以修改高程值之间的间隔,比如将右图中的 “步长增”改为20,然后单击“更新当前分段”按钮即可 修改成功,否则修改无效,然后单击“确认”按钮;
7.6 TIN模型

模型应用;
四、思考题


1.如何借助等高线数据生成TIN模型?借助 TIN模型可以绘制哪些图件? 2.如何进行可视分析? 3.平面数据展布标注制图与高程点标注制图有 何区别?各有何用途?


三角剖分数据——Tin数据;

测试人员的测试环境搭建与配置经验

测试人员的测试环境搭建与配置经验

测试人员的测试环境搭建与配置经验在软件开发流程中,测试环节起着至关重要的作用。

测试人员需要通过搭建和配置合适的测试环境来确保软件的功能和性能符合要求。

本文将就测试人员的测试环境搭建与配置经验进行论述,以帮助测试人员更好地完成测试任务。

一、测试环境的搭建1. 硬件环境选择在搭建测试环境之前,我们首先需要确定合适的硬件环境。

根据测试的实际需求,选择一台性能适中的计算机作为测试机器。

同时,还需确保测试机器的相关硬件设备与被测试软件的要求相匹配,例如网络连接、数据库等。

2. 操作系统的选择与安装根据被测试软件的兼容要求,我们需要选择合适的操作系统作为测试机器的基础环境。

安装操作系统时,需要注意选择稳定且适合测试用途的版本,并进行正确的驱动程序安装以确保硬件正常工作。

3. 开发工具和测试工具的准备根据被测试软件的开发语言和测试需求,测试人员需要提前准备好相应的开发工具和测试工具。

例如,如果被测试软件使用Java语言进行开发,那么我们需要安装适当的Java开发工具和测试框架。

4. 搭建网络环境在某些情况下,我们需要模拟实际网络环境来进行网络连接测试。

可以通过搭建虚拟机、配置网络设备或使用网络模拟器等方式来实现。

确保测试环境中的网络设备和配置与实际应用场景尽可能一致,以获得准确的测试结果。

二、测试环境的配置1. 软件安装和配置在搭建好测试环境后,我们需要进行软件安装和配置工作。

根据被测试软件的需求,依次安装并配置所需的应用程序、数据库、中间件等。

确保各个组件之间的相互依赖关系正确建立,以保证测试环境的稳定运行。

2. 数据准备在测试过程中,我们需要预先准备好一定量的测试数据。

这些数据应具有典型性,涵盖不同场景和使用情况,以全面覆盖被测试软件的功能和性能。

测试数据可以通过手动创建、导入或使用生成工具来获取。

3. 系统配置和参数调整为了满足不同的测试需求,我们可能需要对系统的配置和参数进行调整。

这包括修改配置文件、调整系统性能参数,或对数据库进行优化等工作。

软件测试中的数据准备与环境配置

软件测试中的数据准备与环境配置

软件测试中的数据准备与环境配置在软件测试过程中,数据准备和环境配置是非常重要的环节。

良好的数据准备和合适的环境配置可以保证测试的准确性和可靠性。

本文将介绍软件测试中的数据准备与环境配置的相关知识和技巧。

一、数据准备1. 数据的种类在软件测试中,数据包括测试数据和测试用例数据。

测试数据是指根据测试用例而准备的输入数据,用于验证软件的功能和性能;而测试用例数据是为了满足特定条件或测试目标而准备的数据。

测试数据可以是真实数据、模拟数据或随机数据。

2. 数据的准备方法数据的准备方法可以根据具体情况选择,常用的方法包括手动生成数据、使用现有数据和数据生成工具。

手动生成数据适用于简单的场景,可以根据需求手动输入数据。

使用现有数据适用于有大量数据可用的情况,可以利用已有的数据进行测试。

数据生成工具适用于需要生成大量数据的情况,可以根据需求自动生成数据。

3. 数据的验证与清理在使用数据进行测试之前,需要对数据进行验证和清理。

数据的验证是为了确保数据的正确性和完整性,可以通过比对数据和预期结果来验证数据的准确性;数据的清理是为了保证数据的一致性和可用性,可以删除重复或无效的数据。

二、环境配置1. 测试环境的选择在进行软件测试之前,需要选择适合的测试环境。

测试环境可以分为开发环境、测试环境和生产环境。

开发环境是指开发人员用于编写和调试代码的环境,一般包括开发工具、数据库和服务器等;测试环境是指测试人员用于进行测试的环境,一般包括测试工具、测试数据和测试设备等;生产环境是指软件正式发布后供用户使用的环境,一般包括生产服务器、数据库和网络等。

2. 环境的搭建与配置在进行软件测试之前,需要对测试环境进行搭建和配置。

搭建环境包括安装和配置测试工具、数据库和服务器等;配置环境包括设置测试参数、创建测试账号和配置网络等。

环境的搭建和配置需要根据具体的测试需求和环境要求进行操作,并保证环境的可用性和稳定性。

3. 环境的监控和管理在软件测试过程中,需要对测试环境进行监控和管理。

  1. 1、下载文档前请自行甄别文档内容的完整性,平台不提供额外的编辑、内容补充、找答案等附加服务。
  2. 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
  3. 3、如文档侵犯您的权益,请联系客服反馈,我们会尽快为您处理(人工客服工作时间:9:00-18:30)。

How to Use DTM for Windows Vista System Logo Testing:A Step-by-Step GuideAugust 28, 2007AbstractThis paper provides information about how to use Device Test Manager (DTM) to perform system logo testing for Windows Vista®. It contains guidelines for new users to set up, configure, test, submit, and diagnose tests by using DTM. It applies to DTM version 1.0.b and earlier.This information applies for the following operating systems:Windows VistaWindows Server® 2003Note This document will not be maintained in the future. For complete and ongoing coverage, refer to the installation instructions (Install.htm) in the root of the Windows Logo Kit (WLK) DVD and the help documentation available within DTM Studio.ContentsInstalling DTM Controller (3)Installing the DTM Tests (6)Installing DTM Studio (9)Installing DTM Client (11)Testing Systems (14)Understanding the Test Logs (25)Submitting Error Logs (28)DisclaimerThis is a preliminary document and may be changed substantially prior to final commercial release of the software described herein.The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.This White Paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT.Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, email address, logo, person, place or event is intended or should be inferred.© 2007 Microsoft Corporation. All rights reserved.Microsoft, BitLocker, Windows, Windows Server, and Windows Vista are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.The names of actual companies and products mentioned herein may be the trademarks of their respective owners.Installing DTM ControllerYou can install Device Test Manager (DTM) Controller only on a computer that is running Windows Server® 2003 with Service Pack 1 (SP1) or Service Pack 2 (SP2). Note The screenshots in this document may appear different between different releases of the Windows Logo Kit (WLK) and DTM.To install DTM Controller1. To start Autorun, insert the WLK DVD into your DVD drive. If Autorun isdisabled, you must manually start Installer.exe. You can click the button toinstall DTM Controller only if you are running Windows Server 2003 with SP1 or SP2.The Microsoft Windows Logo Kit Installer dialog box appears.If you do not Framework 2.0 and the SQL Desktop Engine currently installed, install them from the Windows Logo Kit Prerequisite SetupPackages section before you proceed to install DTM Controller.2. In the Windows Logo Kit Setup Package section, click the Install button nextto Driver Test Manager (DTM) Controller.Note If you plan to do system testing, make sure that you install only .NET Framework 2.0, SQL Desktop Engine, DTM Controller, and DTM Tests on the computer.The Microsoft DTM Setup wizard appears.3. Click Next.The End-User License Agreement page appears.4. Read the EULA, click I accept the terms in the License Agreement, and thenclick Next.The Custom Setup page appears.5. Click Next.The Ready to Install page appears.6. To begin installing DTM Controller, click Install.Note This process can take a while. It may appear at times that the progress bar stops, but this is normal. During installation, you might see the following page for 20 or more minutes.7. When the installation has completed, the following page appears. To completethe installation, click Finish.Installing the DTM TestsAfter installing the DTM Controller, you must install the DTM Logo tests separately. To Install DTM Tests1. In the Microsoft Windows Logo Kit Installer dialog box (shown in step 1 ofthe preceding procedure), under Windows Logo Kit Setup Packages, click the Install button next to Microsoft DTM Tests.The Microsoft DTM Tests Setup wizard appears.2. Click Next.The End-User License Agreement (EULA) page appears.3. Read the EULA, click I accept the terms in the License Agreement, and thenclick Next.The Custom Setup page appears.4. Click Next.The Ready to Install page appears.5. To begin installing Microsoft DTM Tests, click Install.Note This process can take a while. It may appear at times that the progress bar stops, but this is normal. During installation, you might see the following page for 20 or more minutes.6. When the installation has completed, the following page appears. To completethe installation, click Finish.7. As appropriate, go to the WHDC Web site to download and install the latestQuick Fix Engineering (QFE) updates. Do not simply download the latest QFEs;install them only if they are needed.Installing DTM StudioYou can choose to install DTM Studio on the same computer on which you installed DTM Controller or to another computer that is in the same network as the controller. We recommend that you install DTM Studio on the same computer on which you installed DTM Controller. It is a good idea to make sure that the system under test is close to the server so that you can intervene with the manual tests whennecessary. Do not install DTM Studio on a computer on which you plan to install DTM Client.To install DTM Studio1. On the taskbar, click Start, and then click Run.2. In the Run dialog box, type \\servername\DTMInstall, and then click OK.Note When you installed DTM Controller, a share called DTMInstall wasautomatically created on the server computer.3. In the Studio window (not shown here), navigate to the Studio folder anddouble-click Setup.exe to start the Microsoft Windows Driver Kit – Studio Setup wizard.4. Click Next. The End-User License Agreement page appears (not shown here).5. Read the EULA, click I accept the terms in the License Agreement, and thenclick Next.The Custom Setup page appears.6. To accept the default settings, click Next. The Ready to Install page appears(not shown here).7. To install DTM Studio, click Install. When the installation has completed, theCompleted page appears (not shown here).8. To complete the installation, click Finish.Installing DTM ClientYou cannot install DTM Client on the same computer on which you installed DTM Controller. Do not install DTM Client on any computer on which you plan to install DTM Studio or on any computer that already has DTM Studio installed. Install DTM Client on a test machine that is on the same network as the DTM Controller. Additionally, make sure that the DTM Client is running an appropriate operating system for which you want a logo.To install DTM Client1. On the taskbar, click Start, and then click Run.2. Type \\servername\DTMInstall, and then click OK.3. In the Client window (not shown here), navigate to the Client folder and double-click Setup.exe.The following message appears.4. Click Run. The Microsoft Windows Driver Kit – Client Setup wizard appears (notshown here).5. On the Welcome page (not shown here), click Next.The End-User License Agreement page appears.6. Read the EULA, click I accept the terms in the License Agreement, and thenclick Next.The Internet Connection Firewall Agreement page appears.7. Click Yes I will allow a port to be opened, and then click Next.8. On the Custom Setup page, click Next to accept the default installation.The Drive Selection page appears.Note Do not select Default Drive if the client is a dual-boot computer or if you intend to use the same computer to test multiple versions of Windows. In that case, place the Jobs working folder on a separate partition and preserve that folder through the different Windows boots and installations.9. Make sure that Use Default Drive is selected, and click Next. The Ready toInstall page appears (not shown here).10. To install DTM Client, click Install.11. When the installation is complete, the Completed page appears. To completethe installation, click Finish.Testing Systems1. On the desktop of the computer on which you installed DTM Studio, double-click the shortcut to DTM Studio.The Windows DTM Studio start page appears.2. On the Explorer menu, click Job Monitor.The Job Monitor explorer3. In the Machine Pool tab on the left side, right-click the $ symbol, and then clickAdd Machine Pool .Note We recommend as a best practice that you use the model name of the system that you are testing as the name of the pool that you are adding as part of this step.Note After you have installed DTM Client software on your test clients, thecontroller automatically detects new test clients and adds them to the Default Pool . You cannot test from the Default Pool . Instead, you must manually create a test machine pool, as described in this step. After you have created the test machine pool, you can drag and drop the systems in the Default Pool to the new test pool that you created. At that point, you can schedule those machines to run tests.After DTM Client has been installed on a test machine, it can take 5 to 20minutes for DTM Controller to automatically detect its presence. You canmanually refresh the list of machines in the Job Monitor by clicking View and then Refresh , or by pressing F5.4. Type a name for the machine pool, select a Job Delivery Agent , and then clickOK . Your machine pool is now listed in the Machine Pool pane on the left,under the $ symbol.5. Right-click the machine pool that you just created, and then click Properties.6. On the MCU Policy tab, under Available dimensions, scroll down and clickWDK\ConfigureSystem, click Add, and then click OK.7. You will now return to the Job Monitor explorer. You must drag and drop themachine that you want to test from the Default Pool into the new test machine pool that you just created. The status of the machine will be set to Manual.8. Right-click the test machine, point to Change Status, and then click Reset. Thestatus of the machine under test changes to Ready. When the test machine is ready, the MCU policy that you applied from the Available dimensions dialog box (in step 6) begins to initialize the machine with the MCU.9. Wait for the initialization to complete before you proceed. If you are promptedby the test machine for credentials for the DTMLLUAdminUser account, type Testpassword,1.Now you can log on to the Winqual Web site and download the latest filterupdates. However, the best time to download filter updates is after all the tests have been completed and you are ready to check the results.Note You must be a registered user of the Winqual Web site to download filter updates.10. On the Explorer menu, click Device Console.The Device Console explorer11. In the upper-right corner of the screen, click the Submission arrow, and thenclick New Submission.Important Do not click any of the option buttons (for example, Device,Machine, or Driver) in the View By area. Although they are functional, they do not apply to the logo program.The following dialog box appears.12. Click the operating system that is installed on the client system for which youwant to obtain a logo, and then click Next. The Create New Submissionwizard appears.13. Click System Submission, and then click Nex t.14. Click the platform that you are testing, and then click Next.15. Click the Qualification Level that you are testing for, and then click Next.16. In Name for new submission, type a name, click the machine pool that yourmachine is in, and then click Next.Note If you are running multiple versions of the same test, you can name them accordingly to provide version control with the test.The following page appears.17. Click the machine under test, and then click Finish.18. In the Device Console explorer, select the check boxes of the jobs that youwant to run, and click the Add Selected button in the lower-left corner. Thelogo program requires all the listed tests.Important Although you can schedule jobs in other ways, you should schedule them only from Device Console. Doing otherwise invalidates the logosubmission.19. If errors appear in the bottom window, you should ignore them and click theSchedule Jobs button in the lower-right corner. In particular, it is normal for the Device column to display No Devices Selected and for the Machine column to display No Machines Specified.20. Schedule the jobs in the following order.To add a second machine as an AP host1. Install DTM Client on an additional computer as described in the InstallingDTM Client section earlier in this document. This computer must be runningWindows XP SP2.2. In the Job Monitor explorer, drag and drop the newly added computer from theDefault Pool into the new test machine pool that you created manually.3. Right-click the additional computer, point to Change Status, and then clickReset. You will then see the status of the machine under test change to Ready.When the test machine is ready, the MCU policy that you applied from theAvailable dimensions (in step 6 of the Testing Systems section) begins to initialize the machine with the MCU.4. In the Device Console explorer, select the Fidelity Test check box, and thenclick Add Selected. Notice that the Caution icon appears next to the test name.5. Click Schedule Jobs in the lower-right corner. When the Fidelity Test runs,the following dialog box appears within DTM Studio.6. In the Run Modes area, make sure that Run Test Locally is selected, and thenexpand the machine pool in the Run Test Locally area. 7. Click the second machine in the pool, and then click Save .8. In the Device Console , select the tests that you want to run, and clickSchedule Jobs .Note This is not an all-inclusive list of the tests that appear in Device Console;however, the main tests are described in the table.After the tests have completed, you can create a compressed package (CPK) to send to Microsoft with your submission.To create a CPK1. Download and apply the latest filters. This ensures that the CPK Log Viewershows the test results with the latest filters applied.2. In Device Console, click the Status button.3. In Device Console, right-click the name of your machine under test, and thenclick Create Submission Package.4. When you are prompted to save the package, type a name for it, and then clickSave. Depending on the volume of tests that were executed, it might take a few minutes to compile the CPK.To review a CPKDownload and install the DTM Log Viewer for WHQL.To submit your passing test sequence to MicrosoftGo to the Winqual Web site and then scroll to Windows Logo Programs, select hardware, and then create logo submission. You will need a CPK as mentioned in the previous section.Understanding the Test LogsDue to the sheer number of tests that are performed and the number of possibilities of the root causes of failures, it is almost impossible to create a knowledge base of resolutions that is easily accessible. This section can help you find the exact failure notification so that you can investigate it further.If a test fails, you will see a red X in the Job Monitor that indicates failure.Note It is important to understand that the top section in Job Monitor shows the machines under test, the middle section shows the jobs, and the bottom section shows the tasks. You do not need to be concerned if a job passes but shows that a task within it has failed. The DTM is concerned only with jobs.To view job errors1. Click the machine that you were testing in the Machine Pool , and then click ajob that shows a failure notification in the Job Pool . You will then see a list of the job's tasks in the Task Pool . 2. Right-click a failed task, and then click View Task Log if available. If the log isnot available, right-click Child Job Results, find the failing task, and then click View Task Log.The Test Log Report - Summarywindow appears.3. In the upper-left corner, on the View menu, click Failure . The entire log isfiltered to display only failed job results.Note To view the detail of the task, click the plus sign (+) next to Test Cases . All failures in this view will be listed in red text, as seen in the following storage stress test failure.Note You can use the logs to help you to identify areas that need someattention, or you can send the logs to your original design manufacturer (ODM) to help you to identify issues.Submitting Error LogsIf you submit error logs to either your systems engineer, ODM, or Microsoft Technical Account Manager (TAM) to interpret the log results, we recommend that you create a compressed package (CPK) of your logs before you submit them as described in the To create a CPK procedure earlier in this document.。

相关文档
最新文档