The best forum is probably the scalatest mailing list: http://groups.google.com/group/scalatest-users

There’s an open ticket about the problem with vals here:
https://github.com/paulbutcher/ScalaMock/issues/3

As you can see from that bug, it turns out to be a more fundamental problem than it first appeared to be. I believe that I have worked out the structure of a solution, but I don’t have an implementation of it yet.

Just a little extra information regarding the post above. I noticed the original comment about the immutable method error was associated with lazy vals. I seem to be getting this when using a trait that has vals (not necessarily declared as lazy either). The mock object tries to override the val as a def.

Also, if you’d prefer me to post questions / issues in another forum, please let me know.

Thanks,
Ryan

Any chance the “method needs to be a stable, immutable value” is resolved? I’m still getting the error. I’ve used the following in my SBT however:

libraryDependencies += “org.scalamock” %% “scalamock-scalatest-support” % “latest.integration”,

Thanks in advance,
Ryan

Yes, please do create a bug and I’ll get to it as soon as I can.

Like Paul I just started looking at ScalaMock and it looks nifty! I have however discovered an issue I think.

When mocking an object like:
object Foo {
def foo(s:String)(t:String):List[String] = List(s,t)
}

The generated mock does not compile:
object Foo extends Mock$$Foo {

def foo(s: String): (t: String)List[String] = if (forwardTo$Mocks != null) forwarder$0(s) else mock$0(s)
// other generated methods here
}

As you can see the generated mock does not implement the correct method signature. After the first parameter list it inserts “:” expecting a return type.

Should I create an issue on GitHub for this?

The issue with question-marks should be easy for me to fix.

Embarrassingly, I haven’t tested lazy vals – I’ll investigate and see if I can work out what’s up.

Can you do me a favour and create issues in GitHub for both of these? Thanks!

The generated mock methods for methods ending in ? and + don’t compile. The generated method name needs a space before the :

For example the following is generated (and does not compile)

def post_?: Boolean = …

but this would work

def post_? : Boolean = …

The other problem is where the class extends a trait with a lazy val, which gives “method X needs to be a stable, immutable value”.

Not sure what you can do about that one. Keep up the good work!

Maven support is on my list of things to do, but I know next-to-nothing about Maven, unfortunately, so it’s unlikely to happen soon I’m afraid. If you or anyone else fancies having a go, I’d be delighted to accept a contribution

Regarding cglib, I’m well aware of it. I deliberately chose not to use it because part of my motivation for ScalaMock was to support Android, and Android’s Dalvik VM doesn’t support cglib, unfortunately.

I’m not opposed to a cglib backend for ScalaMock, and may look at it myself at some point, but it’s not something I’m likely to have time to investigate any time soon, I’m afraid. Again, I’d be very happy to accept contributions if anyone felt like giving it a go