Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I was reading an article by Dino Esposito on how to test AsyncConrollers in ASP.NET MVC and in there he uses the “Humble Object” pattern, without going into much detail.
I haven’t had much luck Googling around either.
So, what is the Humble Object pattern? When would it be useful?
There is a thorough description at xunitpatterns.com.
Basically, you pull all the logic into a separate object which you can easily test – and your “Humble Object” becomes a wrapper around your testable object; it’s just that the humble object also has dependencies on things that are difficult to test, like async services or GUI classes. The idea being to leave so little actual logic in the humble object that you don’t need to test it, and so don’t need to deal with testing the difficult to test dependency.