An alternate version of this test uses an in-memory database and populates a dummy user and all of the associated dummy information you might ever need in any test for any presenter. Now we significantly change the behavior of the presenter and it will just always pull from the in-memory database of otherwise real-looking data. It doesn't matter if one query becomes two or if the query changes or if the order of calls changes. When the implementation changes, our test does notchange because we're only testing the output of the presenter, not scripting how it talks to its inputs.
Database? Use an in-memory version. Shared preferences? Use an in-memory version or point to a dummy file that's cleared after each test. Network requests? Don't use wire-mock or MockWebServer, create an in-memory fake of your server. Permission manager? Create an in-memory fake. Biometric manager? Fake.