Solution Test Overview
This document illustrates activities that make up the test strategy, which checks the interaction and operational validity of each Microsoft scheme (obtained by MSM).
With a comprehensive quality assurance (QA) method, its main researchers, processes, and technical components are operated as solutions and involve a broader business range and operational process, as well as pure technical issues. QA should start in the initial stage of the project and provide support for technical design and development groups by determining the goals for solutions and solution components.
Important test criteria for the need to verify in the solution include:
• aims. Whether the solution has reached the goal determined by the business / scope document? • Results. Whether all feature components and system components are located in the function specified in the functional manual? • The correctness. Depending on the test, whether the function is expected? • Do not have a complex component that acts in action, and whether they will bring trouble to end users or technical support in the future?
There are several test methods and programs in this document:
• Test cases. The test case is a system including an input, performing a pre-processing and an estimated output, which is for special objects, such as exercise special procedures paths or whether the test is met. This test can be further divided into two subcategories that are associated with "providing" and "installation" in the user environment. • Product Features. This test has verified the function and performance of "not packaged" products that have been filed. • Product configuration. These test cases evaluate product customization, configuration, or programming to perform special tasks. • Process and policy schemes This test usually evaluates the guidance steps, guidelines, or policies.
Test Range
In most items, the time assigned to the previous deployment task (for example, test) is limited by the demand for construction, resources, funds, and organizations. These restrictions also limit the breadth and depth of the tests performed. Because the number and scope of these tests depends on organizational needs and business goals, it is recommended that only minimal testing is impossible, because the test will provide sufficient high guarantees for subsequent deployments.
Therefore, concentrated energy tests must be an important aspect (functional) of organizations (functional). Although there may be problems in other aspects of the program, it is secondary and conducive to the reduction of the level of test.
The MSM test team is mainly committed to the management of terminals to terminals in the Windows Server 2003 environment. The plans they are involved include deploying servers and desktops in this environment; operation, fixing, and monitoring this environment; users and site management of this environment. All plans have been tested in the management architecture. It has introduced in the Management Architecture Guide. This test key is to ensure that the MSM components can be seamlessly integrated to meet the needs and emphasis of different customers within the project. Business solution.
Test type
The test type you want to perform is introduced below.
unit test
Unit test (also component test or module test) is usually composed of a set of tests, which explicitly in a single operation, functionality or process.
Figure 1: Unit test View the actual size of the actual size.
The unit test is performed by the MSM development team in its unit test environment, and the test results have been recorded before the scheme is tested in an integrated test environment. Please refer to the relevant section, which is the test environment in which the test environment is used in the MSM test in more detail. All program plans described in this document MSM Solution Component Test Sections must perform unit testing.
Document review
The primary job to test the team to be implemented is to review the MSM documentation. This work is to be performed before any formal tests executed in the laboratory. In the laboratory construction process, the chapter specified in the guide is accurately tested. All program plans described in the "MSM Solution Component Test" section must perform this test. For custom documents created by your own organization, your test team can also do this to show its policies and steps.
Build a verification test (BTV)
After the laboratory is built in accordance with this document test laboratory environment chapter, the MSM test team immediately implemented BVT test so that the core functions of different services and basic functions of the management infrastructure can play. This test ensures that the service is deployed as indicated in the document, ensuring unity of each set of documents. Technologies to be tested include Microsoft Operations Manager (MOM), Microsoft Software Upgrade Service (SUS), Terminal Services (TS), Microsoft System Management Server (SMS), Advanced Deployment Server (ADS), and Various Windows Server 2003 Resource Toolkit program. After the laboratory, this test is only executed once. Safety test
A network of management has reduced its security accordingly. To ensure that the security will not be reduced, the evaluation test is required. These tests should be performed immediately after the BTV test. And all scenarios have implemented these tests in all the scenarios of the MSM Solution Component Test section.
System test
This method tests the compatibility of components, and how components are integrated. For process testing, this method evaluates communication within the process.
Figure 2: System Test View full image.
Integration Testing
This series of tests can display their effects along with other third-party products and processes other than other Microsoft technology and infrastructure products, processes, and other third-party products and processes that may be integrated into the enterprise.
Figure 3: Integrated test View full image.
Program test
This series of advanced tests check the effectiveness of terminals to terminal processes in different business plans and operational environments.
Figure 4: Program test
pressure test
The company performs this test to evaluate the accuracy and effectiveness of MSM guidance when running at rated load, full load or close to full load. All program plans described in the next section must perform this test.
MSM scheme component test
The following MSM solution components perform tests by the MSM test team.
Management architecture
During the system architecture deployment management architecture, the management architecture will be tested to find a typical problem that companies may encounter. The system architecture is designed based on Microsoft Systems Architecture (MSA) best practices guidelines. The system architecture is more in-depth analysis in the back of the test laboratory environment in this document. To simulate the real-world program, the MSM test team designed a model company, and its security zone divided several mainland and the branch office and the Group's data center were associated with a different WAN.
In the MSA architecture, Wide Area NetWork (WAN) is passed through the Virtual Private Network (VPN) pipe, or through the T1 line connected to the Internet to Internet Service Provider (ISP). To study the impacts caused by limiting bandwidth and network conditions, the test team introduces a server with a special-purpose dual address to simulate the network bandwidth congestion and increase the delay time of the packet transmission. Like MOM warning, MOM cross-firewall monitoring, SUS across wide area network synchronization and SMS cross-firewall function are part of this program test.
Patch management solution
Patch management solutions provide advice and guidance for deploying software patches, service upgrade packets, and fast repair projects (QFE) using SMS or SUS.
Patch management guidance includes:
• Efficient repair management technology and proceedings. • Repairing the details of the operational process included and how SMS or SUS supports these processes. • Daily, weekly, monthly tasks and tasks that must be implemented
Figure 5 shows the advanced flowchart of the repair management. SMS and SUS Patch Management Flowcharts are determined within this framework. This flowchart has a detailed description in the patch management scheme.
Figure 5: Repair management flow chart
The MSM test team uses the SMS and SUS servers to perform patch management in accordance with the instructions in the patch management program. These tests should be performed separately, but they will be synchronized with each other.
System Management Server (SMS)
The basic goal of the repair management test is to ensure that the organization that uses the Microsoft System Management Server Deployment Patch Management can be confidently enabled, so that the solution can work normally in its product environment. The MSM test team tests the patch management scheme with the model companies described in previous chapters. To be more comprehensive to test the test flow and build your own test environment, see Following the documentation in accordance with the Microsoft System Management Server Test Scheme Overview Document by MSM V2.0 Patch Management. Details of the installation and patching and execution steps are introduced in the test case details, which can be downloaded in the following URLs. Http://go.microsoft.com/fwlink/?LinkID=20211. The MSM test plan for the MSM test team focuses on installing the patch for Microsoft Exchange 2000 Server and Microsoft SQL Server 2000. Advanced testing of the above two is explained in the following sections.
Microsoft Exchange 2000 Server
• Build 2 nodes for Exchange clusters. • Install SP1 on a node and install the released patches on another node.
plan 1
• Use SMS to determine the difference between the patches and boost two nodes to the same configuration level. This is called flat. • Use SMS to ensure available patch available
Scenario 2
• Update two Exchange 2000 Server nodes to SP3.
Solution 3
• Install subsequent Exchange 2000 Server SP3 patch for two nodes
Follow the patch management flow shown in Table 1 to install the patch, make sure that the corresponding patch is installed in both nodes of the end of the process Exchange 2000 Server.
Microsoft SQL Server 2000
• Install the SQL Server 2000 cluster. • Install SQL Server 2000 SP3 on 2 computers • Use SMS to ensure that the latest patch is available. • Follow the patch management flows shown in Table 1 below, and ensure that the corresponding patch is installed in the two nodes of the end SQL Server in the process.
The advanced steps of the System Management Server Patch Management Test Process are shown in Table 1. For the results of the detailed test step and the result of the MSM test team, see the SMS Patch Management Form in the Test Example Details in the Electronic Form. Test case Details spreadsheets can be downloaded at the following URLs Http://go.microsoft.com/fwlink/?LinkId=20211.
Table 1 System Management Server Patch Management Test Process
View the full image.
Software Update Service (SUS)
SUS Patch Management Test can be used for servers, workstations, and laptop. At the same time, you can perform tests in the same model enterprise in the previous chapter. Site Level, Domain Level, and OU Level Group Policy (GPOS) can be used for SUS patch management testing. The test team determines the GPOS for different target computers at the Active Directory site level and the organizational unit (OU) level. Use the Group Policy Management Console (GPMC) tool to configure group policies. SUS Patch Management Test is primarily for Microsoft Windows XP and Windows 2000 Advanced Server technology. To test the test process more fully and build your own test environment, see the MSM V2.0 Patch Management Follow the Microsoft Software Update Service Test Plan Overview to Practition Management Documents. Details of the installation and patching and execution steps are introduced in the SUS patch management table for the test case details. Advanced tests for each situation will be described in the following sections.
SUS repair management
• Does the Active Directory site level policy must point to the appropriate SUS server. • Different OU level policies in the server, workstation, and portable computer are used to fix management configuration. Scenario 1: Server
• Install Windows 2000 SP3 on a computer configured as a server. • Follow SUS Patch Management Guide to install selected sample patches on a Windows 2000 computer
Solution 2: Workstation
• WIDOWS XP is installed on all client computers. • Install SP1 on several client computers. • Use MBSA to evaluate and determine the flat. • Upgrade all client computers to SP1. • Follow SUS Patch Management Guidance to install instant patches, QFE, and patch samples.
Solution 3: User roaming
• Join the portable computer into the domain. • Connect to the domain through a portable computer. • Install Windows XP SP1 on your laptop. • Follow SUS Patch Management Guidance to install some sample fixes listed above. • The step of the software update service patch management test process is shown in Table 2.
Table 2 Software Update Service Repair Management Test Process
See the actual size picture.
Service monitoring and control
The purpose of service monitoring and control is to observe whether the endpoint to endpoints in the information technology service is normal to find and prevent service exceptions, and simult information for other service management functions (SMFS) to optimize IT services.
Service Monitoring and Control (SMC) Test is in central status in different MOM configuration, which is introduced in the management architectural guidance. Develop specific management schemes, for example, component failure, stress and alarms are used to test the effectiveness and accuracy of SMC guidance.
User and location management
MSM provides detailed person, process, and automation guidelines for adding, deleting, and changing users and addresses. Test these programs in accordance with MSM guidance to perform specific work. Testing will be carried out under various conditions specified in the MSM model enterprise and its verification.
User Management
Advanced Change Management and Publish Management Flow Charts are shown in Figure 6. It can be used to add users, change users, and delete user workflows. This flowchart has a detailed description in the User Management Build Guide, additional information, see the MOF change quadrant material.
Figure 6: Change management and release management flow chart
The MSM Test Panel determines the workflow to add, change, and delete users. The purpose is to span the test scheme to different processes to enable the test team to simulate a real customer plan in the test environment.
The test team used the system infrastructure specified in the test laboratory environment. In a scheme designed to test the user management process, an employee of New Delhi's branch office was convened and requested to join Contoso, Ltd. (MSM deployment plan), the virtual company used in the plan, then returned SEATTLE CORPORATE Center. This scenario includes 3 contents of the user management scheme: add, change, and delete users. The various items included in the scheme will be described below.
Add user. When the employee joins the New Delhi branch office, you need to run the addition of the user workflow to enable employees to start working outside the local office. The MSM test team runs the add user workflow and ensures that users can log in to Asian fields to start accessing his or her resources.
Change the user. Retreating employees from Asian fields to North American fields is a typical change user program. This includes running to add users and delete user workflows in the corresponding domain. The MSM test team runs workflow and ensures that employees can now log in to North American fields and begin to visit his or her resources.
delete users. Re-deploying employees to North American domains to run delete user workflows in Asian domain. The MSM test team runs the deletion of a user workflow on the Asian domain and ensures that users have no access to the Asian domain, for example, unable to accept emails.
The following table lists the instructions for testing schemes and test cases, while the different phases used to change the status of the quadrant / change / delete the different stages in the user process are reflected here.
Table 3 is used to change the test scheme and description of the quadrant.
View the full image.
What is the implementation of these test schemes, what is in the implementation process, please refer to the User Management Table (Test Example Details Electronic Form), which can be downloaded at http://go.microsoft.com/ FWLINK /? LINKID = 20211. It also includes the test results that the MSM test team is drawn in its test laboratory. Location management
Advanced Change Management and Publish Management Flowcharts are shown in Figure 7. It is a workflow for adding location, changing location, and deleting locations. For details of this process, see Location Management Build Guide Supplementary Information See "MOF Change Quadrant" material.
Figure 7: Change management and release management flow chart
The MSM Test Team is determined to develop a test plan for each process in the process of adding, changing, and deleting location workflows. The team uses the system infrastructure specified in the test laboratory environment to perform location management testing. And create a new Active Directory domain, which is part of the location workflow test. The domain is moved to a separate Active Directory site. You can then add users to this site and operate the site to test the effectiveness of the operation. The MSM Test Panel decides to use the same site to test the change position workflow. A new DHCP server is created to meet the needs of user growth, which is a scheme for testing change location sites. The team once again uses a full set of MOF, determines the technology contained in this process and performs testing to verify that the flowchart is valid. Finally, this site is deleted to test the deletion of the location workflow. In order to simulate the situation in the real world, some users are migrated to the North American field while deleting some users.
The solution used to test the location management flow chart is as follows:
Add location. The MSM Test Panel decided to add a new site (Brazil) and the new domain (South America) to test the location workflow. This site is connected to the group's data center via T1. The site has only one domain controller, the DNS server in the domain controller, and some client computers.
Change location. The MSM team decided to add a DHCP server in this new site, which is part of the change position test. A new DHCP server has been added according to the workflow specified in the Location Management Build Guide.
Delete the location. The MSM test team deletes South American and Brazil sites to test the deletion of the location workflow.
The following table records the test schemes and test cases, which are reflected in the different stages of the addition / change / delete position workflow.
Table 4 is used to change the test scheme and description of the quadrant.
View the full image.
For more information on these test programs and various test results, see Location Management Tables (Test Example Details Electronic Form), which can be downloaded at Http://go.microsoft.com/fwlink/?LinkID = 20211.
Core OS Service Operation Guide
Product Operation Guide (POGS) Details Different work needs to be performed per week / weekly month to ensure the normal infrastructure environment. Pogs mainly introduces the core operating system components, such as the Microsoft Active Directory Services, Domain Name System (DNS), Dynamic Host Configuration Protocol (DHCP), Windows Internet Name Service (WINS), and files and print services. This test ensures that the execution steps of different configuration tasks in Pogs are accurate, and these tasks help instantiate the management environment. Special management schemes designed, for example, component failures, stress conditions, and alarms are used to test POG effectiveness and accuracy. (When writing this article, DNS POG cannot be used to test.)
Executing these tests is to prove that MOF-based processes and automation management of Windows Server 2003 environments help companies manage corporate environments in the most efficient way.
