Vincent RICARD

After some thoughts I can understand why you would display `item.toString()` in case you have someone populating a list with custom items without backing it up with custom cells. So,...

I have exactly the same issue and I also believe MockK could be behind it. I have posted the issue on SO: https://stackoverflow.com/questions/63059986/android-ui-tests-with-espresso-mockk-crash-with-sigsegv Looking at OP crash log, I found...

I agree with @NitroG42 . I have migrated the few UI tests I had written to on a new mobile app project **Mockito** believing it would be way more stable...

Great, since the issue android/android-test#352 is closed... Also, if it can helps, my logs are now showing C++ traces upon crash with the SIGSEGV. Maybe it could help ? ```...

Interesting, thanks for the project, I'll see what I can do. I was tempted to revert back to Mockito, but since you did it, it's fine. I would then suggest...

In my case, I decided to go for Mockito (instead of MockK) on which I had no prior experience. And so far, so good.

@NitroG42 bad news, the crashs are back. So I now believe that MockK is not culprit. More info here: https://github.com/android/android-test/issues/352#issuecomment-669049551

Hi all and thanks for your inputs so far :) I will try and sum up: 1. Both mockk and mockito faces the issue, though with some differences in the...

Hi everyone and much thanks for all of your feedback for the past year. I would like so summarize / conclude. First of all, it now seems evident that this...