Skip to content

Conversation

@AlmightyMikkel
Copy link
Contributor

No description provided.

Copy link
Contributor

@kirre-bylund kirre-bylund left a 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).

Copy link
Contributor

@kirre-bylund kirre-bylund left a 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.

@kirre-bylund
Copy link
Contributor

Also, your tests are failing. They seem to be locking up somewhere and eventually timing out. Please fix

Copy link
Contributor

@kirre-bylund kirre-bylund left a 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.

}, true);
}

public static void CreateAsset(int contextID, Action<LootLockerTestAssetResponse /*asset*/> onComplete)
Copy link
Contributor

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?

Copy link
Contributor

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

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
Copy link
Contributor

@kirre-bylund kirre-bylund left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All comments answered

@kirre-bylund kirre-bylund merged commit 1fbdc91 into dev Sep 19, 2024
108 checks passed
@kirre-bylund kirre-bylund deleted the ci/revamp branch October 17, 2024 05:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants