Editor testing
For testing purposes, you can create custom mock implementations of interfaces to simulate various scenarios. This allows you to thoroughly test and validate the behavior of your game without relying on actual external dependencies and running in PlayPad.
To do this, find PlayPadCommunicator component on your scene and provide your own implementations for the communicators you want to test.
You can derive from:
CustomStandaloneAuthenticationCommunicatorBaseCustomStandaloneLeaderboardCommunicatorBaseCustomStandaloneTournamentCommunicatorBaseCustomStandaloneGameStatusCommunicatorBaseCustomStandaloneExternalUiCommunicatorBaseCustomStandaloneErc20SmartContractCommunicatorBase
tip
If you want to find out how default Editor implementation for some communicator works, search for Standalone counterpart of it.
For example for leaderboards the default is StandaloneLeaderboardCommunicator.
Another useful tool for testing in the Editor are Scriptable Objects called StandaloneConfigs:
StandaloneExternalAuthenticatorConfigStandaloneExternalTournamentConfigStandaloneExternalGameStatusConfig