I had a question about making something public only to test it for years. I read tons of blog posts about testing yet never encountered an answer. I even asked the author directly once but got useless response. Thank you for finally answering it!
I haven't gotten to that part of the video yet, and I'm still new to TDD, but it sounds like it's only good to test your code's interface (what is publicly exposed). At least that's what I've been told, and what I've read online. It makes sense too because all of your private methods are merely implementation details that must only be called upon within a specific context that's facilitated by the public interface. Wordiness aside, private methods should be private if they can't be called at any point in time. Those private methods are always going to be called by either a property or method that is publicly callable one way or another. If a method or branch in one of your private methods doesn't get called, then it's dead code and should probably be eliminated. It's not uncommon to write multiple tests for a single public method to test all of these use-cases either. Anyway, that's my 2 cents. I'm still new at this myself, so I'm still developing the mindset for testing too :D
I had a question about making something public only to test it for years. I read tons of blog posts about testing yet never encountered an answer. I even asked the author directly once but got useless response. Thank you for finally answering it!
What is his answer?
I haven't gotten to that part of the video yet, and I'm still new to TDD, but it sounds like it's only good to test your code's interface (what is publicly exposed). At least that's what I've been told, and what I've read online. It makes sense too because all of your private methods are merely implementation details that must only be called upon within a specific context that's facilitated by the public interface. Wordiness aside, private methods should be private if they can't be called at any point in time. Those private methods are always going to be called by either a property or method that is publicly callable one way or another. If a method or branch in one of your private methods doesn't get called, then it's dead code and should probably be eliminated. It's not uncommon to write multiple tests for a single public method to test all of these use-cases either.
Anyway, that's my 2 cents. I'm still new at this myself, so I'm still developing the mindset for testing too :D
48:05
One of the best video about TDD in Unity! Many thnx!
Nice video, this is gold. Despite the couple things I didn't get muc completely in the examples...
Thanks!
What UI automation plugin do you suggest to use?
Please are more videos about TDD and unit testing i general :)
nice theme, nice links to catlike coding blog, but I wouldn't say this video is greate for starting with TTD, I feel lack of accents
It is a pitty that the tools are not available anymore and the videos have not been removed.
The test runner is at window>General>Test Runner