* .vsmdi的目的是什么?我需要进行源代码控制吗? [英] what's the purpose of *.vsmdi? Do I need to source control it?

问题描述

.vsmdi文件的用途是什么?我需要检查源代码控制系统吗?

What's the purose of .vsmdi file? Do I need to check into the source control system?

推荐答案

首次创建测试项目时，Visual Studio将创建VSMDI文件.它包含Visual Studio可以在解决方案程序集中找到的所有测试的列表，并允许您将测试分为所谓的测试列表.这些测试列表可用于对测试进行分类，并让您选择要执行的测试子集.

The VSMDI file is created by Visual Studio when you create a test project for the first time. It contains a list of all tests that Visual Studio can find in your solution assemblies and allows you to divide your tests into so-called test lists. These test lists can be used to categorize your tests and let you select a subset of tests for execution.

您可以使用此机制来运行子选择.但是，您也可以(自由地)为一个测试分配多个测试类别，这使您能够以更灵活的方式实现相同的目标.有了VSMDI文件的已知问题，例如这些文件的不受控制的重复以及用警告图标列出的过时测试，这似乎是执行此类操作的更好方法.

You can use this mechanism for running sub-selections. However, you can also (freely) assign multiple test categories to a test, which enables you to achieve the same, in a more flexible way. And with the known issues with VSMDI files, like uncontrolled duplication of these files and obsolete tests being listed with a warning icon, it might seem the better way to do things like this.

我的总体建议是:检入默认生成的.vsmdi文件.当添加新的测试项目时，这将阻止Visual Studio在您自己和团队成员系统上(重新)生成此类文件.根据您的使用经验来决定使用测试列表或直接为测试分配类别.测试列表很容易入手，但是不太适合您想要灵活地进行大量测试.

My overall suggestion is: check-in your default generated .vsmdi file. This will prevent Visual Studio from (re-)generating such files on your own and your team members systems when new test projects are added. Decide on usage of test lists or assigning categories to tests directly based on your usage experience. Test lists are easy to start with, but less suitable is you want to have flexibility for a large set of tests.

这篇关于* .vsmdi的目的是什么?我需要进行源代码控制吗?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！