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

It is believed that many inexperienced people don't know what to do about the implementation steps of the VS2010 suite. Therefore, this article summarizes the causes and solutions of the problem. Through this article, I hope you can solve this problem.

The VS2010 suite describes the detailed execution steps and methods of the test, as well as the expected results of each method execution, and talks about the Test Case here in more detail. Configuration defines the various execution environment configurations of Test Plan. These are all very practical.

The answer I can think of is that the functions of testing and laboratory management are relatively independent, and it is easier to use them as a separate tool. If it is only used to manage the lab or execute test cases, you can only install this tool, and you can choose to install only the MTLM tool in the installation interface, right? -- to be confirmed at the next installation.

I installed MTLM on my machine, and after running this tool for the first time, I found that MTLM is only a client for testing and laboratory management functions, that is, a "supporting role". The real "main role" turns out to be a Team Foundation Server (TFS) server, or rather, TFS 2010 Beta 2. MTLM is completely dependent on TFS, and the interface it runs is for you to connect to a specified TFS server, otherwise it will stop there and it will be impossible to move a step further.

We know that TFS is the core server of Microsoft's software development life cycle management (ALM) suite, and closely binding MTLM with it further highlights Microsoft's software lifecycle management software strategy, which has been gradually started since VS 2005 and 2008, and the VS2010 suite further strengthens this strategy. VS is no longer just for developers or testers, but to provide a platform to effectively coordinate and support the various roles in the development process, and enable them to collaborate closely with each other. Just as Excel and Project and TFS connections are already supported in VS 2008, it is also a trend to imagine that all tools related to the software development process will be bound to TFS in the future.

These concepts are easy to understand, and Test Plan is the top-level object managed in MTLM. After starting the MTLM, you need to connect to the TFS project, which must be a project used by the team, which saves the user requirements work items, source code, etc., created by the development team, and the Test Plan object must be created on this project. Test Suites is actually used to organize Test Case, similar to the role of folders in a file system. Test Case here refers to manual test cases.

The VS2010 suite describes the detailed execution steps of the test, as well as the expected results of each step, and more precisely, Test Case refers to manual test cases (Manual Test Case). Configuration defines the various execution environment configurations of Test Plan. Where Requirement maps to TFS's work items of type User Storey, while Test Case and Shared Step correspond to Test Case and Shared Step work items.

It should be pointed out here that Automated Test Case can only be defined and implemented in code in the VS test project, and can be run in VS, and its code is saved in the code controller of the TFS project. Automated Test Case can also be executed in MTLM after it is associated with a Test Case defined in MTLM.

After reading the above, have you mastered the steps of the VS2010 suite? If you want to learn more skills or want to know more about it, you are welcome to follow the industry information channel, thank you for reading!

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.