Is summary necessary in unit test method

Question

Since the naming of a unit test method makes its purpose more meaningful, is it necessary to add a summary to a unit test method?

Example:

/// 

        

Answer 1

For the example above, I would say that it's not necessary, unless you use a tool that extracts documentation from source (like javadoc or something).

A common rule of thumb is that the code says what you're doing and the comment says why, but since the name is so very verbose (which I think is ok, since no one ever has to type it) I don't think that the comment contributes anything.