Software Architect's Handbook

Unit test method names

The unit test methods should be given meaningful names that provide, at a glance, their purpose. Characteristics such as the method being tested, some indication as to the specific condition(s) and input(s) of the test, and the expected result of the test are all useful to provide.

For example, if we are testing the CalculateShipping method on the OrderService class, we might have test method names such as:

• CalculateShipping_NullOrder_ThrowsArgumentNullException
• CalculateShipping_ValidOrder_CalculatesCorrectAmount
• CalculateShipping_ExpeditedShipping_CalculatesCorrectAmount

The exact naming convention for unit test methods is up to you, but the important point is to come up with one and to use it consistently in order ...