Shulou(Shulou.com)06/02 Report--

This article will explain in detail about Visual Studio 2010 Ultimate test architecture is what kind of, Xiaobian think quite practical, so share to everyone as a reference, I hope you can read this article after harvest.

VS2010 Test Overview

A software product or system, like anything else, also goes through stages such as gestation, birth, growth, maturity, and decline, which is generally called software life cycle, also known as SDLC(software development life cycle). It is the life cycle of software from birth to retirement. There are several stages in the cycle, such as problem definition, feasibility analysis, general description, system design, coding, debugging and testing, acceptance and operation, maintenance and upgrading, etc. This idea of time division is a kind of thinking principle in software engineering. SDLC can also be interpreted as a set of Steps, Phases, or Milestones. The general steps of SDLC include: problem identification, feasibility analysis and development planning, requirements gathering, analysis and design, code development, testing, installation, and maintenance.

In Microsoft Visual Studio 2010 Ultimate, application life cycle (ALM) is one of its key features and SDLC implementations. We divide a software lifecycle (SDLC) into several phases, and use various tools to assist in managing each key link, which is called Application Lifecycle Management (ALM). Microsoft Visual Studio 2010 will strive to create a functionally equal, shared, easy-to-use platform for application lifecycle management processes within organizations.

In VS2010 tools, the real protagonist is no longer VS IDE as a coding tool, but TFS, the core of ALM. The new MTM (Microsoft Test Manager) tool is an auxiliary client.

Tip: Microsoft Test Manager is a rich client software based on Windows Presentation Foundation (WPF)(internal development code "Camano"), installing Visual Studio 2010 Ultmate user client, which can integrate testing and management control functions for projects under development.

In the traditional Microsoft. NET software build workflow (run tests-> compile code-> deploy applications), each system has its own set of methods, for example, its own repositories, resources, commands, and tools. This will give developers who like to experiment with integration and custom components the feeling that the software build process is fragmented and not suitable for unified integration and code debugging and software testing when the project is large. This traditional build workflow is shown in Figure 1.

Figure 1 Traditional software process information silos

The mission of TFS is to solve the problem of "silos" of information in the development process, and to enable them to collaborate through a unified storage mechanism. TFS 2010 is already a multi-source control, simpler and "civilian" implementation and deployment, and a big step forward in overall collaboration technology. The Microsoft Test and Lab Manager build software workflow is shown in Figure 3.

Figure 2. Traditional software process information silos

The mission of TFS is to solve the problem of "silos" of information in the development process, and to enable them to collaborate through a unified storage mechanism. TFS 2010 is already a multi-source control, simpler and "civilian" implementation and deployment, and a big step forward in overall collaboration technology. The Microsoft Test and Lab Manager build software workflow is shown in Figure 3.

Figure 3 Lab Management Build Software Workflow

Microsoft has provided a wealth of tools for different roles to access TFS data, as well as the TFS Object Model (API), enabling third-party vendors to develop their own TFS based software, which expands the scope of workflows for. Net workers. This is shown in Figure 4.

Figure 4 VS 2010 Software Workflow

Visual Studio is no longer just a software coding tool for developers, it has become an ALM tool covering the entire software development lifecycle. In fact, as a software tool vendor, this is also an inevitable development direction, just like IBM also has Rational, ClearCase and other tools. As practitioners in every software industry, whether developers, project managers, or testers, we have to adapt to this trend, and I think it will only make our work easier and easier.

VS2010 Test Framework

For testers, VS2010 enhances testing capabilities and simplifies tools for integrating testing throughout the application lifecycle. New features include rapid test-related design and development, test case management, test planning integrated with Team Foundation Server, and ensuring that all updated program code is tested to improve coverage. These new features span the entire test cycle: test planning, test execution, and test execution progress tracking. New MTM tools are used to create test plans, manage test cases, run test cases, manage test results, and manage distributed virtual environments. The VSTS 2010 test framework is shown in Figure 5.

Figure 5 VSTS 2010 Test Framework

From the above test framework demonstration, we can see that VSTS2010 has strengthened support for test plans, test cases, related reports, etc. Microsoft has transformed VSTS2010 into a major tool throughout ALM. In addition to MTM, VSTS2010 also supports Web Tests, Ordered Test, Generic Test, and Unit Test automation. The new CodedUI Test is aimed at functional test engineers and provides them with new functionality to support automated testing and is also integrated with MTM tools.

Testing and Laboratory Management Framework

VSTS2010 includes comprehensive improvements to architecture design, project templates, test management, Test Lab management, project portals, etc.; and comprehensive integration with MS Project, SharePoint, Hyper-V virtualization platforms, and cloud computing platforms. Testing and lab management functions are relatively independent, so it is easier to use as a single tool.

On the server side, Lab Management Services is one of many services running in-house on Team Foundation Server (TFS), a solution that is unique to software testers and developers. We can now map lab resources, such as project collections for hosts, virtual machines, and storage teams to team projects, so we can adjust the lab hardware and business requirements to work.

On the client side, managing virtual resources is still done with MTM tools. Users can use it to define test plans, test suites, test cases and runs in physical or virtual environments. The laboratory management architecture is shown in Figure 6.

It is Microsoft's new generation server virtualization solution. Its architecture is completely different from Microsoft's previous virtualization products such as Virtual Server and Virtual PC. It can be said to be a breakthrough in Microsoft virtualization technology. Therefore, it is important to understand some of the basic concepts surrounding virtualization and how these labs can be managed to understand this paradigm shift in technology.

As you can see from the above diagram, Microsoft Labs Management Framework incorporates virtualization technology. Hyper-V

Figure 6 Laboratory management architecture

Hyper-V is a Mini programs with only a few hundred KB. It is between physical hardware and virtual machine. It has very little code and does not contain any third-party drivers. It is very compact. This architecture makes the connection between virtual machine and hardware only through a thin layer, unlike Virtual Server, which requires multi-layer conversion between virtual machine and hardware. Therefore, virtual machine execution efficiency is very high and hardware resources can be fully utilized. Make virtual machine system performance very close to real operating system performance. It emulates a complete hardware system, from processors to network cards, in a separate, siloed software environment, enabling incompatible operating systems to run simultaneously on a physical computer. Each operating system runs in its own isolated software partition. The Microsoft Hyper-V architecture diagram is shown in Figure 7.

Figure 7 Microsoft Hyper-V architecture diagram

The Lab Center in Microsoft Test and Lab Manager (MTM) is a facility for creating and managing virtual or physical environments on Microsoft Virtualization Technology; taking snapshots of environments or falling back to existing snapshots of virtual environments; communicating with virtual machines in environments through Environment Viewer; defining test settings for environments; and defining test scenarios, test suites, and test cases in the Test Center and executing them on lab environments.

The MTM tool has the following administrative features:

Virtual Machine Snapshot: A virtual machine snapshot is a file-based snapshot of the state, e.g., data on disk and configuration of the virtual machine at a particular point in time. Snapshots are the added flexibility of virtual machines when they are functionally similar to laptop hibernation, with one VM supporting multiple snapshots. You can roll back to any snapshot previously taken and can continue working there. Hyper-V VM snapshot tree, as shown in Figure 8.

Figure 8. Microsoft Hyper-V VM snapshot tree

Host: A physical computer hosting one or more virtual machines.

Host Groups: are hosts of virtual machines, and administrators can create custom groups in SCVMM to facilitate monitoring and management. Can be used to allocate and determine resources reserved for various team projects. For example, an administrator can create a hosting group named "Global Insurance Hosting Team" about the "Global Insurance Project" project and bind it to the corresponding team project in the Team Foundation admin console.

Library Share: One of the advantages to VMs is that you don't need to hoard hosts (if you're not using VMs for a while). You can copy it for a few minutes, store it on disk, and bring it to work in other computer environments. Environment: A typical multi-tiered application consists of multiple roles, such as database server, Web server, client, etc. Each role can run on one or more computers, or multiple roles can run on a single computer. It was a cumbersome and error-prone task to manage multiple layers of environments in the past, and it was even more difficult to replicate the same environment.

In TFS Lab Management Services, use of the Lab Management System Center Virtual Machine Manager (SCVMM) and virtual machine configuration management across multiple virtualization platforms, can be obtained from SCVMM Lab Management and Replication.

SCVMM (System Center Virtual Machine Manager) is a virtualization technology management tool and part of Microsoft's System Center Management solution. SCVMM 2008 R2 can manage VMware ESX, Microsoft Virtual Server 2005 R2, and Windows Server 2008 R2 Hyper-V.

SCVMM has six new features: fast storage migration, live migration queues, fast provisioning, host compatibility detection, support for third-party CFS file formats, and support for Veritas Volume Manager. It consolidates physical servers into a virtual architecture to provide end-to-end support; enables fast and reliable physical-to-virtual (P2V) and virtual-to-virtual (V2V) machine conversions; enables intelligent placement of virtual workloads on physical host servers; enables rapid deployment and migration of virtual machines; and enables centralized management of complete library files for all component blocks in virtual data centers.

VS 2010 emphasizes collaboration between testing and developers. Test Impact View and Code Changes View can avoid the waste of running all tests to verify a small code change and make testing more efficient. In addition, testers can use the MTM tool to track and control the Bug lifecycle (Plan->Test->Track->Organize). New BUG releases via Testing Center.

MTM introduces new concepts that are generally easy to understand literally, including the following four concepts: Test Plan, Test Suites, Test Case, and Configurations, and describes their relationships using UML class diagrams provided in VS 2010. as shown in figure 9.

Figure 9 Relationship diagram of MTM test objects

As can be seen from the above figure, Test Plan is the top-level object managed in MTM. When MTM is started, it needs to be connected to TFS project. This project must be the project used by the team. It saves the user requirements work items created by the development team, generation source code, etc. Test Plan objects must be created on this project. Test Suites are actually used to organize Test Cases, similar to folders in a file system. Test Case here refers to manual test case, which describes the detailed execution steps of the test and the expected results of each step. More accurately, Test Case here refers to manual Test case. Configuration is the configuration of various execution environments that define Test Plans. Here, Requirement maps to TFS User Store type work items, while Test Case and Shared Step correspond to Test Case and Shared Step work items. MTM provides an interface for managing and using these objects, as shown in Figure 10.

Figure 10 Management interface of MTM object

Note: It should be pointed out here that Automated Test Case can only be defined and code implemented in VS test project, and can be run in VS, and its code is stored in the code controller of TFS project. Automated Test Cases can also be executed in MTM after being associated with Test Cases defined in MTM.

About "Visual Studio 2010 Ultimate test architecture is how" this article is shared here, I hope the above content can be of some help to everyone, so that you can learn more knowledge, if you think the article is good, please share it to let more people see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.