You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
overriding method withFixture in trait MockitoFixture of type (test: IdentificationServiceSpec.this.NoArgTest)org.scalatest.Outcome;
method withFixture in trait ResetMocksAfterEachTest of type (test: IdentificationServiceSpec.this.NoArgTest)org.scalatest.Outcome has weaker access privileges; it should be public
sorry that I only report issues instead of fixing them immediately in a PR, Im low on time ;/
The text was updated successfully, but these errors were encountered:
I haven't put much effort in this one (maybe I just should document it doesn't work) as both modes are somehow incompatible
This trait is aim for people that must declare their mocks outside the test scope, and as we discussed in #31 the session basically requires the mock to created as part of each test and not as part of the test class
I'm going to think if there is a fancy way to combine both, but tbh, I don't think the use cases overlap, if you were forced to have mocks as class instances then there isn't that much you can do about it
What do you think? is there any use-case in where it make sense to have both class and test level mocks?
sorry that I only report issues instead of fixing them immediately in a PR, Im low on time ;/
The text was updated successfully, but these errors were encountered: