Proof of Concept: Containerized Integration Tests #40
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.
This is a POC on how an SDK can use an extended Nakama image loaded with rpc functions to run integration tests against.
See https://github.com/heroiclabs/nakama-clientsdk-test for how this image is built and the associated rpc functions. The image it builds is currently on Docker Hub: https://hub.docker.com/repository/docker/heroiclabs/nakama-clientsdk-test
For test social provider keys, I propose an optional bind mount from the host machine and corresponding optional tests that are triggered in each SDK if such keys exist.
Remaining Steps:
(1) Make client-sdk test image repository public (before merging!)
(2) Versioning for test image on Docker Hub and make it public also (before merging!)
(3) Integrate with Github Actions
(4) Finalize approach for test keys