spitballing about jest mocks
ok. ok. ok. pure spitballing theory here.
All the client side source exists in esmodule form (hopefully importing from eachother?)
So then it stands to reason that a jest instance could instanciate an actual
All the client side source exists in esmodule form (hopefully importing from eachother?)
So then it stands to reason that a jest instance could instanciate an actual
Game instance as though it were actually an active game session. With something that mocks out a browser standing in for all the browser APIs, "All you'd need to mock" would be the socket connection server calls.