JavaNaming: Difference between revisions
No edit summary |
mNo edit summary |
||
(2 intermediate revisions by 2 users not shown) | |||
Line 2: | Line 2: | ||
<pre> | <pre> | ||
public void testWhenTheCustomersBankAccountReachesZeroGetStatusReturns_NoAvailableFunds_unlessOfCourseTheAccountIsClosed_ifTheAccountIsClosedThenItShouldReturn_AccountClosed_() { | |||
assertEquals("No Available Funds", fixture.getAccountWithZeroBalance().getStatus()); | assertEquals("No Available Funds", fixture.getAccountWithZeroBalance().getStatus()); | ||
assertEquals("Account closed", fixture.getAccountWhichIsClosed().getStatus()); | assertEquals("Account closed", fixture.getAccountWhichIsClosed().getStatus()); | ||
} | } | ||
</pre> | </pre> | ||
[[Category:Java|Naming]] |
Latest revision as of 07:53, 1 October 2007
theInventionOfCamelCaseNamingHasBeenAGreatHelpToJavaProgrammers_IHaveFoundItUsefulInAllMyJavaProgramsAndWouldLikeToProposeASlightExtensionToTheStandard_youSee_SometimesYouHaveAMethodOrVariableNameWhichRequiresMoreThanOneSentenceToDescribe_inSuchCases_IProposeReplacingThePeriodAtTheEndOfTheSentenceWithAnUnderscore_additionally_theUnderscoreCharacterCanBeUsedToReplaceOtherPunctuation_suchAsCommas_furthermoreIProposeUsingTwoUnderscoresToCreateANewParagraph__theseNewChangesWillBeMostUsefulForJavaProgrammersWhoLikeToGiveMethodNamesVeryDescriptiveNames_forExample_
public void testWhenTheCustomersBankAccountReachesZeroGetStatusReturns_NoAvailableFunds_unlessOfCourseTheAccountIsClosed_ifTheAccountIsClosedThenItShouldReturn_AccountClosed_() { assertEquals("No Available Funds", fixture.getAccountWithZeroBalance().getStatus()); assertEquals("Account closed", fixture.getAccountWhichIsClosed().getStatus()); }