title: Is it ok to unit-test an abstract class by instantiating it as a mock object?
body: <p>It has come to my attention that you can unit-test an abstract class by instantiating it as a mock object. Thereby you mock the abstract properties and methods, while being able to test the implemented ones. </p>
  
  <p>However, I am accustomed to distinguish between the class <strong>to test</strong> and the injected dependencies <strong>to mock/stub</strong>. So, in this early stage of my new enlightenment I wonder if there are any pitfalls to this way of testing?? Any thoughts on this? </p>
  
  <p>Regards, 
  Morten</p>