I have another question wink Why is that ``` coEvery view sh

Question

I have another question wink Why is that ``` coEvery view showDeleteSectionDialog returns true ``` produces ``` Bad recording sequence State AnsweringState ``` but ``` with view coEvery showDeleteSectionDialog returns true ``` does not

svenjacobs · Answer

Seems to be related to the coroutine versions of the `verify` functions only

oleksiyp · Answer

Should be just syntactic sugar

svenjacobs · Answer

Is this intentional or a bug

oleksiyp · Answer

Bug

svenjacobs · Answer

Okay +1

oleksiyp · Answer

But I am not able to understand how it may happen

oleksiyp · Answer

Aw with should have same bytecode

oleksiyp · Answer

As

svenjacobs · Answer

Should I create an issue on GitHub

oleksiyp · Answer

the answer is yes slightly smiling face

svenjacobs · Answer

It seems that this was un intentionally fixed in MockK 1 9 1 sunglasses

oleksiyp · Answer

Good

svenjacobs · Answer

Or wait a minute I have tests where it works and others where not Have to investigate further

svenjacobs · Answer

This might not be a MockK problem at all I m using Spek 2 0 and I have something like this in my test class ``` val mock by memoized mockk lt Cache lt Entry gt gt coEvery tryGet uuid returns entry1 ``` Now when I try to specify additional behaviour in a test with `coEvery mock ` I get this error whereas `with mock coEvery ` works When I remove `memoized` both variants works It seems to be related to the `memoized` delegate

svenjacobs · Answer

< oleksiyp> Do you have an idea what the problem could be or should I direct my issue to the developers of the Spek framework

oleksiyp · Answer

I think you shouldnt specify `mock` variable in the scope it is being initialized Just add more behaviours without it

svenjacobs · Answer

I don t understand Usually I set up my tests like this Declare mocks and common behaviour before tests and add special behaviour or overriding default behaviour in each test ``` class Test Spek val mock by memoized mockk lt MyClass gt coEvery doSomething returns SOMETHING it should do something coEvery mock doSomethingElse returns SOMETHING ELSE further test it should do something else coEvery mock doSomethingElse returns null further test ```

oleksiyp · Answer

Ok now it is clear what you have where I think yes it may be a case that you need to initialize mock before putting it to `every` Nothing you can do about it

svenjacobs · Answer

I still don t understand why `with memoizedMock coEvery ` is different than `coEvery memoizedMock ` Shouldn t the property be initialized when the property is accessed

oleksiyp · Answer

It initialize mock

svenjacobs · Answer

So `coEvery mock something ` assumes that `mock` has been initialized before the call of `coEvery`

oleksiyp · Answer

Yes inside coEvery magic happens