I generally favor clear verbosity over muddled compactness. So, +1 from me. Let's try it and see how it works out.
Cheers, Nick --- Vincent Massol <[EMAIL PROTECTED]> wrote: > Hi, > > I'd like to propose a way to name our test methods. Instead of naming > them with "test<method named><extension>" such as in: > > testSetUniqueIdOk() > testSetUniqueIdCannotBeRest() > > I propose to name them with a sentence. This means that if you remove > the "test" prefix it should make a sentence. For example: > > testUniqueIdIsAddedToListOfQueryStringParameters() > testUniqueIdCannotBeReset() > > Why? > > For 2 reasons: > - it documents better what the test is doing > - javadoc documentation could then be generated automatically using > TestDox (http://agiledox.sourceforge.net) > > If you're ok then we can use this strategy in the future and slowly > refactor existing test names. We should also add it to the development > rules web page. > > What do you think? > > Thanks > -Vincent > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
