When reporting issues with the ScalaTest integration, we currently name a mock with the method name and parameters only. ScalaMock adds the trait/class under test and a unique identifier (based on the declaration order I believe). We want the trait/class name for sure, and a unique identifier possibly. That identifier needs to be useful for the developer debugging their test (eg. no uuid).
Issue to track ErrorReportingTest.scala#L62 and ErrorReportingTest.scala#L88.
When reporting issues with the ScalaTest integration, we currently name a mock with the method name and parameters only. ScalaMock adds the trait/class under test and a unique identifier (based on the declaration order I believe). We want the trait/class name for sure, and a unique identifier possibly. That identifier needs to be useful for the developer debugging their test (eg. no uuid).