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 really like to use static methods (especially for helpers classes). But as static methods are not stubbable, eventually they are a bad practice, aren’t they? So I have to choose between static methods usage convenience and testability. Is there any compromise?
It depends on what the static methods do.
Is it something that really has to be stubable? Like data access, long running operations etc. or is do you mean helper methods like .ToSlug()?
If it’s the former case, I’d make them instance methods to increase testability / speed of tests.
If it’s the latter, I’d leave them static and just verify their correctness.