Naming Convensions for Unit Tests
What are the common/popular naming conventions for Unit Tests? For example:


----------

[MethodName_StateUnderTest_ExpectedBehavior]

Example:

    Public void Sum_NegativeNumberAs1stParam_ExceptionThrown() 

    Public void Sum_NegativeNumberAs2ndParam_ExceptionThrown () 

    Public void Sum_simpleValues_Calculated ()

source: http://weblogs.asp.net/rosherove/archive/2005/04/03/TestNamingStandards.aspx


----------

I also prefer the above but with underscores between each word such as:

    Public void Sum_Negative_Number_As_1st_Param_Exception_Thrown() 

    Public void Sum_Negative_Number_As_2nd_Param_Exception_Thrown () 

    Public void Sum_Simple_Values_Calculated ()


----------

What other conventions are there and what are the pros and cons for each?



Naming Convensions for Unit Tests
===

What are the common/popular naming conventions for Unit Tests? For example:


----------

[MethodName_StateUnderTest_ExpectedBehavior]

Example:

    Public void Sum_NegativeNumberAs1stParam_ExceptionThrown() 

    Public void Sum_NegativeNumberAs2ndParam_ExceptionThrown () 

    Public void Sum_simpleValues_Calculated ()

source: http://weblogs.asp.net/rosherove/archive/2005/04/03/TestNamingStandards.aspx


----------

I also prefer the above but with underscores between each word such as:

    Public void Sum_Negative_Number_As_1st_Param_Exception_Thrown() 

    Public void Sum_Negative_Number_As_2nd_Param_Exception_Thrown () 

    Public void Sum_Simple_Values_Calculated ()


----------

What other conventions are there and what are the pros and cons for each?


