首页 \ 问答 \ TDD与单元测试[关闭](TDD vs. Unit testing [closed])

TDD与单元测试[关闭](TDD vs. Unit testing [closed])

 我公司是对我们的代码进行单元测试的新手。 我一直在阅读有关TDD和单元测试的一段时间，并且相信它们的价值。 我试图说服我们的团队，TDD值得努力学习和改变我们的思维方式，我们如何编程，但它是一场斗争。 这带给我我的问题。  
 TDD社区中有很多人很关心写测试，然后是代码（和我在一起），但是对于正在与TDD挣扎的团队来说，折中还带来额外的好处？  
 一旦编写代码（可能作为检查代码的要求），我可能会成功地让团队编写单元测试，而我的假设是在编写单元测试时仍然有价值。  
 将挣扎的团队带入TDD的最佳方式是什么？ 而不是这样，即使在代码写入之后它仍然值得编写单元测试？  
 编辑  
 我从中删除的是在编码过程中的某个地方开始单元测试是很重要的。 对于那些接手这个概念的团队来说，开始更多地采用TDD和测试。 感谢大家的意见。  
 跟进  
 我们最近开始了一个新的小项目，一小部分团队使用TDD，其余的在代码之后写了单元测试。 在我们封装了项目的编码部分之后，代码之后的这些写入单元测试惊讶地看到TDD编码器已经完成，并且使用了更为固定的代码。 这是赢得怀疑者的好办法。 我们仍然有很大的成长前进，但意志的战斗似乎已经结束。 感谢大家提供建议！ 

My company is fairly new to unit testing our code. I've been reading about TDD and unit testing for some time and am convinced of their value. I've attempted to convince our team that TDD is worth the effort of learning and changing our mindsets on how we program but it is a struggle. Which brings me to my question(s). 
There are many in the TDD community who are very religious about writing the test and then the code (and I'm with them), but for a team that is struggling with TDD does a compromise still bring added benefits?  
I can probably succeed in getting the team to write unit tests once the code is written (perhaps as a requirement for checking in code) and my assumption is that there is still value in writing those unit tests.  
What's the best way to bring a struggling team into TDD? And failing that is it still worth writing unit tests even if it is after the code is written? 
EDIT 
What I've taken away from this is that it is important for us to start unit testing, somewhere in the coding process. For those in the team who pickup the concept, start to move more towards TDD and testing first. Thanks for everyone's input. 
FOLLOW UP 
We recently started a new small project and a small portion of the team used TDD, the rest wrote unit tests after the code. After we wrapped up the coding portion of the project, those writing unit tests after the code were surprised to see the TDD coders already done and with more solid code. It was a good way to win over the skeptics. We still have a lot of growing pains ahead, but the battle of wills appears to be over. Thanks for everyone who offered advice!

原文：https://stackoverflow.com/questions/1742323

更新时间：2022-05-23 06:05

最满意答案

 根据MSDN MetadataToken在一个模块中是独一无二的 - 没有任何说明它保证任何订单。  
 即使它的行为方式是您想要的，那将是实现特定的，可以随时更改，恕不另行通知。  
 看到这个旧的MSDN博客条目 。  
 我强烈建议您远离任何依赖此类实施细节的信息 - 请参阅Marc Gravell的此回答 。  
 如果你在编译时需要一些东西，你可以看一下Roslyn （尽管它处于一个很早的阶段）。 

On .net 4.5 (and even .net 4.0 in vs2012) you can do much better with reflection using clever trick with [CallerLineNumber] attribute, letting compiler insert order into your properties for you: 
[AttributeUsage(AttributeTargets.Property, Inherited = false, AllowMultiple = false)]
public sealed class OrderAttribute : Attribute
{
    private readonly int order_;
    public OrderAttribute([CallerLineNumber]int order = 0)
    {
        order_ = order;
    }

    public int Order { get { return order_; } }
}


public class Test
{
    //This sets order_ field to current line number
    [Order]
    public int Property2 { get; set; }

    //This sets order_ field to current line number
    [Order]
    public int Property1 { get; set; }
}
 
And then use reflection: 
var properties = from property in typeof(Test).GetProperties()
                 where Attribute.IsDefined(property, typeof(OrderAttribute))
                 orderby ((OrderAttribute)property
                           .GetCustomAttributes(typeof(OrderAttribute), false)
                           .Single()).Order
                 select property;

foreach (var property in properties)
{
   //
}
 
If you have to deal with partial classes, you can additionaly sort the properties using [CallerFilePath].

TDD与单元测试[关闭](TDD vs. Unit testing [closed])

最满意答案

相关问答

如何使用反射获取属性值(How to get a property value using reflection)[2024-02-15]

通过反射的声明顺序获取属性(Get properties in order of declaration using reflection)[2023-09-13]

Stylelint嵌套声明顺序数组(Stylelint Nesting Declaration Order Arrays)[2022-05-09]

获取和使用类属性的反射(Reflection to get and use class properties)[2023-03-02]

如何通过java反射获取在kotlin扩展中声明的属性或函数(How to obtain Properties or Function declared in kotlin extensions by java reflection)[2023-01-23]

类属性声明，属性的属性顺序（final，private，static，type）(class attributes declaration, order of the attributes' properties (final, private, static, type))[2023-09-30]

使用反射按顺序获取类的属性(Get properties of class by order using reflection)[2022-08-02]

具有属性反射问题的对象(Object with properties Reflection Issue)[2022-09-30]

通过反射获取所有ICollection属性(Getting all ICollection properties through reflection)[2022-04-16]

Java反射不同意方法声明(Java reflection not agreeing with method declaration)[2022-10-26]

相关文章

最新问答