The method should still do the same thing, regardless if it is private or public... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		Lawtonfogle on June 25, 2015 \| parent \| context \| favorite \| on: Warner Bros Suspends Sales of Batman: Arkham Knigh... The method should still do the same thing, regardless if it is private or public. If you purposefully create a new method and get rid of the old one, regardless if this is done by creating and deleting or by modifying, then the unit test should be changed as well. In short, you are testing the interface of that private method, not the implementation.

lmm on June 25, 2015 [–]

By that logic you could test a single line and say "I'm testing the interface of that line, not the implementation".

Retra on June 25, 2015 | [–]

You could if your line had a syntactical construct that presented an interface, like say, a name and a parameter list.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact