-
Notifications
You must be signed in to change notification settings - Fork 7
Unity integration test revamp - Target stage #261
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In general very pleased. Left some comments of things that we should adress but I'm gonna approve still so we can merge and have these on dev.
That said, we need to update the README.md file with instructions on how to test (add the testables: [ com.lootlocker.lootlockersdk ] thing and all that).
Tests/LootLockerTestUtils/LootLockerTestConfigurationException.cs
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I went through the commits one by one because the PR was so large so sorry if some comments are outdated already (for example i in one commit comment to remove debug logs that you then remove in the next commit).
You're getting there, a lot of this is great work 💪
For next time though, you should have merged the PR (it was complete and approved when I left) and then split up your changes in different PRs. This was a pain to review.
|
Also, your tests are failing. They seem to be locking up somewhere and eventually timing out. Please fix |
e3f103f to
1f52082
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added some more comments, generally on setup and configuration files. Didn't review the actual tests much further since I realized there are still like 30 unresolved (or resolved in GH but actually unresolved) comments in the PR. Will review later when it's more complete.
Tests/LootLockerTestUtils/LootLockerTestConfigurationException.cs
Outdated
Show resolved
Hide resolved
| }, true); | ||
| } | ||
|
|
||
| public static void CreateAsset(int contextID, Action<LootLockerTestAssetResponse /*asset*/> onComplete) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is the create asset method on the leaderboard class?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still questionable to me, but can't be bothered at the moment
Tests/LootLockerTestUtils/LootLockerTestConfigurationLeaderboard.cs
Outdated
Show resolved
Hide resolved
Tests/LootLockerTestUtils/LootLockerTestConfigurationLeaderboard.cs
Outdated
Show resolved
Hide resolved
c3d6ec8 to
97374f6
Compare
0fac3b4 to
349f5d2
Compare
This is a squashed commit of a long living branch. This commit consists of: 1. Initial workflow that targets stage 2. Added CI specific utils to store created users and games 3. Testing on Guest login 4. Testing on White Label Login 5. Testing on Leaderboard details and rewards 6. Testing on submitting scores to Leaderboards 7. Testing on Leaderboard listing, types, and metadata 8. Testing on Player Info 9. Testing on Pinging LootLocker's server 10. Testing on Player Storage, private, public and update 11. Removed ratelimiting while targeting stage 12. Added retry functionality for CI hitting ratelimiter
349f5d2 to
bd50f0f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All comments answered
No description provided.