I have a user class like such:
class User {
transient springSecurityService
String displayName
String password
protected void encode
I personally don't like adding logic to production code to help satisfy a test. Sometimes you have to make a decision on what's best to do. Couple of options...
If this code (or code that runs into the same problem) is sprinkled throughout your application then you'd probably want to figure out a way to mock out these calls in your unit tests for all test cases so you're not duplicating your setup efforts everywhere. An easy way to mock this out is with metaClassing.
@Test
public void something() {
def user = ...
def springSecurityService = new Object()
springSecurityService.metaClass.encodePassword = {String password -> "ENCODED_PASSWORD"}
user.springSecurityService = springSecurityService
...
}
Now when the springSecurityService.encodePassword
gets invoked it should return "ENCODED_PASSWORD". I also create an Object
instead of instantiating a new SpringSecurityService
because if you instantiate an actual service then you may end up calling actual methods on that service unexpectedly and unknowingly and having your tests pass for the wrong reasons. I'd rather get a no such method error than a passing test that shouldn't be passing.