Skip to content
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

TestRscCogs Cog #198

Open
BenjaminHunt opened this issue May 13, 2022 · 0 comments
Open

TestRscCogs Cog #198

BenjaminHunt opened this issue May 13, 2022 · 0 comments

Comments

@BenjaminHunt
Copy link
Collaborator

This new cog shall test core functionality of the RSC Bot cogs. Test validations shall be executable individually or as a full ordered sequence:

  • validate that core cogs are downloaded by reloading them in the correct order:
    • prefixManager
    • teamManager
    • transactions
    • match
    • bulkRoleManager

There should be two scripts created for this cog:

  • creation/test
  • cleanup

A script should be generated to trigger a test sequence against the core behavior of the bot. This should begin by performing a cleanup in the guild. A confirmation should be prompted before beginning the script.

The cleanup should remove:

  • all saved JSON data in each cog
  • all channels associated with the RSC Bot
  • all roles associated with the RSC Bot cogs

Afterwards, a creation/test script should be executed which will perform the following:

Creation:

  • create required roles (League, Free Agent, PermFA, Draft Eligible, Captain, Subbed Out, etc.)
  • create tier(s)
  • create franchises (2 min)
  • create teams
  • create, register transactions channel
  • create matches

Test:

  • all transactions (verify saved data, and player roles. End with players rostered to teams)
    • sign
    • cut
    • sub
    • IR
  • roster command
  • captains commands
  • match command access appropriate data

If anything additional is missing, it should be added and tested in these scripts.

Ideas:

  • use random people in server as test users for across
  • to avoid pinging people unnecessarily, a role may be assigned called "test subject" and only members with this role will be used for testing.
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

No branches or pull requests

1 participant