Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • Resetting an instance is a way to go when testing singletons, because they are always hard to test and there can't be any nice way around. Sometimes this kind of problems implies that there is something that could be refactored in Your design. Would You consider refactoring? Commented May 9, 2012 at 6:59
  • Yes, but, how could I refactor it? I mean, I spent some time looking for the best way to do it, and the singleton factory seemed a good pattern, it really does the job in a clear way. Only problem I have is with the tests, but I don't want to refactor the whole thing just to fit a jUnit test... Commented May 9, 2012 at 7:09
  • 1
    I see unit tests as the code quality meter. If I encounter something untestable I tend to refactor that piece of code. But, of course, this is Your code and if this testability problem doesn't bother You, resetting the instance is fine. Have You had a look at the Abstract Factory design pattern, for example? I think that should be more testable... Commented May 9, 2012 at 7:27