Jump to content

  • Log In with Google      Sign In   
  • Create Account

#ActualVReality

Posted 06 September 2013 - 07:11 PM

I imagine a good answer might involve breaking the buffering out into its own class (one responsibility for one class, etc.). 

 

Also, I've occasionally made a unit test a "friend" of the class it tests so it can screw with internals without exposing them in general.


#2VReality

Posted 06 September 2013 - 07:11 PM

I imagine a good answer might involve breaking the buffering out into its own class (one responsibility for one class, etc.). 

 

Also, I've occasionally made a unit test a "friend" of the class it tests so it can screw with internals without exposing them in general.


#1VReality

Posted 06 September 2013 - 07:04 PM

I imagine a good answer might involve breaking the buffering out into its own class (one responsibility for one class, etc.).  I don't have that answer off the top of my head.

 

But I can say that I've occasionally made a unit test a "friend" of the class it tests so it can screw with internals without exposing them in general.


PARTNERS