test: verifies that a user can use INetworkSerializable with RPCs #850
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This task is to verify the user can define their own custom network serialized type.
This task is based on the following user stories:
MTT-787
MTT-788
Acceptance Criteria
A user should be able to implement the INetworkSerializable interface within a class and use that class as an RPC Parameter to pass between both client and server RPCs. The test should include the reading and writing of custom values within the custom INetworkSerializable based class.
A user should be able to send arrays of the same class type that implements the INetworkSerializable interface and expect the array to maintain the exact same order from when it was sent to when it is received.
Acceptance Tests
From TestRunner:
TestProject->RuntimeTests->RpcINetworkSerializable->NetworkSerializableTest
TestProject->RuntimeTests->RpcINetworkSerializable->NetworkSerializableArrayTest