Add simple test and GitHub action to run them

[sweep-ai]

PR Feedback (click)

• 👍 Sweep Did Well
• 👎 Sweep Needs Improvement

Description

This PR adds a simple test and a GitHub action to run the test for the Summarize class in the aicord/discord/cogs/summarize.py file. The test ensures that the Summarize class correctly processes chat messages.

Summary of Changes

• Added aicord/discord/cogs/summarize_test.py to contain the test for the Summarize class.
• Created a test class TestSummarize that inherits from unittest.TestCase.
• Defined test methods for each public method in the Summarize class to verify their behavior.
• Created .github/workflows/test.yml to define a GitHub action that runs the test on push events.
• Configured the GitHub action to check out the repository, set up Python 3.10, install dependencies, and run the test using the unittest module.

Fixes #8.

---

🎉 Latest improvements to Sweep:

• Sweep can now passively improve your repository! Check out Rules to learn more.

---

💡 To get Sweep to edit this pull request, you can:

• Comment below, and Sweep can edit the entire PR
• Comment on a file, Sweep will only modify the commented file
• Edit the original issue to get Sweep to recreate the PR from scratch

[sweep-ai]

Rollback Files For Sweep

• Rollback changes to aicord/discord/cogs/summarize_test.py
• Rollback changes to .github/workflows/test.yml
• Rollback changes to .github/workflows/test.yml

[sweep-ai]

Apply Sweep Rules to your PR?

• Apply: There should not be large chunks of code that are just commented out. Docstrings and explanations in code are acceptable.
• Apply: We should use loguru for error logging. If the log is inside an exception, use loguru.exception to add tracebacks. Use f-strings for string formatting in logger calls.
• Apply: There should be no instances of import pdb; pdb.set_trace() in production code.
• Apply: There should be no debug log or print statements in production code.
• Apply: All functions should have parameters and output annotated with type hints. Use list, tuple and dict instead of typing.List, typing.Tuple and typing.dict.
• Apply: Leftover TODOs in the code should be handled.
• Apply: All new business logic should have corresponding unit tests in the same directory. For example, sweepai/api_test.py tests sweepai/api.py. Use unittest and unittest.mock as required.
• Apply: Any clearly inefficient or repeated code should be optimized or refactored.
• Apply: Remove any comments before code that are obvious. For example # this prints hello world; print('hello world').
• Apply: Avoid duplicating code. Refactor and update duplicate code to improve maintainability.
• Apply: Use consistent and descriptive commit messages that accurately reflect the changes made. Use gitmoji for commit messages.
• Apply: Handle exceptions gracefully and provide appropriate error handling and logging.