Too Many Public Methods Forced by Test Driven Development

Posted by RoryG on Stack Overflow See other posts from Stack Overflow or by RoryG
Published on 2010-03-17T19:03:41Z Indexed on 2010/03/17 19:11 UTC
Read the original article Hit count: 366

Filed under:

A very specific question from a novice to TDD:

I seperate my tests and my app into different packages. Thus, most of my app methods have to be public for tests to access them. As I progress, it becomes obvious that some methods could become private, but if I make that change, the tests that access them won't work. Am I missing a step, or doing something wrong, or is this just one downfall of TDD?

© Stack Overflow or respective owner

Related posts about TDD