Ticket/AI-013#26
Conversation
WalkthroughThis update introduces several new test modules, enhances the Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant APIFootballClient
participant API (api-football.com)
User->>APIFootballClient: get_fixtures(fixture_id, date, league, team, season)
APIFootballClient->>APIFootballClient: _build_fixture_payload(...)
alt API key missing or invalid payload
APIFootballClient-->>User: Return empty list (log warning)
else Valid payload
APIFootballClient->>API: GET /fixtures (with headers & params)
API-->>APIFootballClient: JSON response
APIFootballClient->>APIFootballClient: Parse response
APIFootballClient-->>User: Return fixtures list
end
Poem
✨ Finishing Touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
🔭 Outside diff range comments (1)
ai-backend/tests/test_quality_tools.py (1)
1-67: Relocate production code or add actual tests.This file is in the
tests/directory but contains production code rather than tests. TheFootballDataProcessorclass appears to be application logic that should either:
- Be moved to the main codebase (e.g.,
tools/orprocessors/)- Have actual pytest test functions added to test its functionality
If this is meant to be production code, move it:
-# ai-backend/tests/test_quality_tools.py +# ai-backend/tools/quality_tools.pyIf this should remain as tests, add actual test functions:
import pytest from tools.quality_tools import FootballDataProcessor @pytest.mark.unit def test_process_game_data(): """Test game data processing.""" processor = FootballDataProcessor("Premier League") result = processor.process_game_data("Arsenal", "Chelsea", "2-1") assert result["home_team"] == "Arsenal" assert result["away_team"] == "Chelsea" assert result["score"] == "2-1" assert result["league"] == "Premier League" @pytest.mark.asyncio @pytest.mark.unit async def test_fetch_recent_games(): """Test async game fetching.""" processor = FootballDataProcessor("Premier League") games = await processor.fetch_recent_games(limit=1) assert len(games) == 1 assert "home_team" in games[0] assert "away_team" in games[0]
🧹 Nitpick comments (4)
ai-backend/tests/test_openai.py (1)
15-34: Consider restructuring as a proper pytest test.This function acts more like a script than a unit test. Consider adding proper assertions and pytest markers for better integration with the test suite.
+@pytest.mark.integration def test_openai_connection() -> None: """Test basic OpenAI API connection.""" if not os.getenv("OPENAI_API_KEY") or os.getenv("OPENAI_API_KEY") == "your_openai_api_key_here": - print("⚠️ OpenAI API key not set. Skipping connection test.") - return + pytest.skip("OpenAI API key not set") - try: - # Test with a simple completion - response = client.chat.completions.create( - model="gpt-4.1-nano", - messages=[{"role": "user", "content": "Say 'Hello from Sport Scribe AI!'"}], - max_tokens=50, - ) - - print("✅ OpenAI API connection successful!") - print(f"Response: {response.choices[0].message.content}") - - except Exception as e: - print(f"❌ OpenAI API connection failed: {e}") + # Test with a simple completion + response = client.chat.completions.create( + model="gpt-4-turbo", # Use valid model name + messages=[{"role": "user", "content": "Say 'Hello from Sport Scribe AI!'"}], + max_tokens=50, + ) + + assert response.choices[0].message.content is not None + assert len(response.choices[0].message.content) > 0ai-backend/tests/test_fixtures.py (2)
8-32: Reduce code duplication by extracting common mock classes.The mock classes are duplicated across multiple tests. Consider extracting them to fixtures or a shared location.
+@pytest.fixture +def mock_response_data(): + """Fixture for mock response data.""" + return {"response": [{"fixture": 1, "league": 39, "season": 2025}]} + +@pytest.fixture +def mock_session(mock_response_data): + """Fixture for mock session.""" + class MockResponse: + status = 200 + + def __init__(self, data): + self._data = data + + async def json(self): + return self._data + + def raise_for_status(self): + pass + + async def __aenter__(self): + return self + + async def __aexit__(self, exc_type, exc, tb): + pass + + class MockSession: + def __init__(self, response_data): + self.response_data = response_data + + def get(self, *args, **kwargs): + return MockResponse(self.response_data) + + return MockSession(mock_response_data) @pytest.mark.asyncio +@pytest.mark.unit -async def test_get_fixtures_by_league(monkeypatch): +async def test_get_fixtures_by_league(mock_session): - class MockResponse: - # ... remove duplicate code - - class MockSession: - # ... remove duplicate code - client = APIFootballClient(api_key="test") - client.session = MockSession() + client.session = mock_session
7-7: Add appropriate pytest markers to all test functions.The test functions are missing the
@pytest.mark.unitmarker that was defined in the pytest configuration.@pytest.mark.asyncio +@pytest.mark.unit async def test_get_fixtures_by_league(monkeypatch): @pytest.mark.asyncio +@pytest.mark.unit async def test_get_fixtures_by_league_missing_season(monkeypatch): @pytest.mark.asyncio +@pytest.mark.unit async def test_get_fixtures_by_date(monkeypatch): @pytest.mark.asyncio +@pytest.mark.unit async def test_get_fixtures_by_team(monkeypatch): @pytest.mark.asyncio +@pytest.mark.unit async def test_get_fixtures_by_multiple(monkeypatch): @pytest.mark.asyncio +@pytest.mark.unit async def test_get_fixtures_no_params(monkeypatch):Also applies to: 35-35, 42-42, 70-70, 98-98, 140-140
ai-backend/tools/sports_apis.py (1)
58-92: Consider simplifying the API key validation.The method implementation is well-structured with good parameter flexibility and delegation to helper methods. However, the API key validation at lines 80-82 is redundant since headers are already configured conditionally in the constructor.
Consider removing the redundant check:
- if not self.headers or "X-RapidAPI-Key" not in self.headers: - logger.error("Missing RapidAPI key in headers.") - return [] - payload = self._build_fixture_payload(fixture_id, date, league, team, season)The API call will naturally fail with appropriate error handling if the API key is missing.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (11)
ai-backend/.pre-commit-config.yaml(1 hunks)ai-backend/agents/editor.py(1 hunks)ai-backend/agents/researcher.py(2 hunks)ai-backend/config/settings.py(5 hunks)ai-backend/main.py(3 hunks)ai-backend/pytest.ini(1 hunks)ai-backend/tests/test_environment.py(1 hunks)ai-backend/tests/test_fixtures.py(1 hunks)ai-backend/tests/test_openai.py(1 hunks)ai-backend/tests/test_quality_tools.py(1 hunks)ai-backend/tools/sports_apis.py(3 hunks)
🧰 Additional context used
🧬 Code Graph Analysis (2)
ai-backend/main.py (2)
ai-backend/agents/editor.py (2)
EditorAgent(13-62)review_article(21-35)ai-backend/utils/logging.py (1)
logger(207-209)
ai-backend/tests/test_fixtures.py (1)
ai-backend/tools/sports_apis.py (2)
APIFootballClient(23-209)get_fixtures(58-92)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: Codacy Static Code Analysis
🔇 Additional comments (18)
ai-backend/.pre-commit-config.yaml (1)
31-31: Minor style change - inconsistent with PR objectives.This change switches from double quotes to single quotes for the isort arguments, which is a minor formatting improvement. However, this doesn't align with the stated PR objective of implementing a "Football Fixtures Endpoint."
Likely an incorrect or invalid review comment.
ai-backend/agents/researcher.py (2)
24-24: Good formatting improvement.The method signature consolidation improves readability.
36-36: Logging format improved, but implementation still pending.The single-line logging format is cleaner. However, note that this method still contains a TODO comment and doesn't implement the football fixtures functionality mentioned in the PR objectives.
Likely an incorrect or invalid review comment.
ai-backend/agents/editor.py (1)
37-37: Method signature formatting improved.The single-line method signature is more readable and consistent with the formatting changes across other agent files.
ai-backend/main.py (4)
116-116: Exception handling format improved.The single-line HTTPException format is cleaner and more readable.
150-150: Method signature consolidation improves readability.The single-line method signature is consistent with similar formatting changes throughout the codebase.
154-154: Method call formatting improved.The single-line format is cleaner and maintains consistency with other formatting changes.
272-272: Logging statement format improved.The condensed logging format is more readable and consistent with the formatting style used throughout the PR.
ai-backend/tests/test_environment.py (1)
1-49: Inconsistent with PR objectives - missing Football Fixtures implementation.This environment test file doesn't relate to the stated PR objective of implementing a "Football Fixtures Endpoint." The PR description mentions changes to
tools/sports_apis.pyandtest_fixtures.py, but these files are not included in the review.Likely an incorrect or invalid review comment.
ai-backend/pytest.ini (2)
11-14: Good coverage configuration with appropriate threshold.The coverage settings are well-configured with term-missing for identifying uncovered lines, HTML reports for detailed analysis, and an 80% threshold which is a reasonable target for this project.
15-19: Well-defined test markers for better test organization.The markers provide clear categorization for different test types (slow, integration, unit, asyncio) which will help with selective test execution and CI/CD pipeline optimization.
ai-backend/tests/test_openai.py (1)
24-24: Confirming OpenAI model name:gpt-4.1-nanois valid.As of April 2025, OpenAI officially offers a “GPT-4.1 nano” variant alongside other GPT-4.1 models. The test’s use of
"gpt-4.1-nano"is correct, so no change is needed.Likely an incorrect or invalid review comment.
ai-backend/config/settings.py (3)
24-29: Good modernization to uppercase environment variables.The change to uppercase environment variable names follows conventional naming patterns and improves consistency with standard practices.
55-96: Excellent migration to modern Pydantic syntax.The update from
@validatorto@field_validatorwith explicit@classmethoddecorators follows current Pydantic best practices and improves code clarity.
114-114: Proper migration to SettingsConfigDict.The change from nested
Configclass tomodel_configattribute usingSettingsConfigDictaligns with current Pydantic patterns and maintains all previous functionality.ai-backend/tools/sports_apis.py (3)
31-42: LGTM! Good defensive programming for API key handling.The conditional header setup allows for flexible initialization and testing scenarios while maintaining clean separation of concerns.
94-116: LGTM! Solid validation and security practices.The method correctly implements the league/season dependency validation and applies input sanitization. The empty dict return on validation failure provides a clear signal to the caller.
118-143: Excellent error handling and response validation.The method demonstrates robust async HTTP handling with comprehensive error management and response validation. The fallback session creation is defensive programming that prevents runtime errors.
The implementation correctly:
- Handles aiohttp session lifecycle
- Validates HTTP response status
- Safely extracts and validates response data structure
- Provides meaningful error logging
- Returns consistent empty list on failures
| try: | ||
| print("✅ OpenAI package imported successfully") | ||
| except ImportError as e: | ||
| print(f"❌ OpenAI import failed: {e}") | ||
|
|
||
| try: | ||
| print("✅ OpenAI Agents package imported successfully") | ||
| except ImportError as e: | ||
| print(f"❌ OpenAI Agents import failed: {e}") | ||
|
|
||
| try: | ||
| print("✅ FastAPI package imported successfully") | ||
| except ImportError as e: | ||
| print(f"❌ FastAPI import failed: {e}") | ||
|
|
||
| try: | ||
| print("✅ Pydantic package imported successfully") | ||
| except ImportError as e: | ||
| print(f"❌ Pydantic import failed: {e}") | ||
|
|
||
| try: | ||
| print("✅ Supabase package imported successfully") | ||
| except ImportError as e: | ||
| print(f"❌ Supabase import failed: {e}") | ||
|
|
||
| try: | ||
| print("✅ Aiohttp package imported successfully") | ||
| except ImportError as e: | ||
| print(f"❌ Aiohttp import failed: {e}") | ||
|
|
||
| try: | ||
| print("✅ Python-dotenv package imported successfully") | ||
| except ImportError as e: | ||
| print(f"❌ Python-dotenv import failed: {e}") | ||
|
|
||
| try: | ||
| print("✅ Structlog package imported successfully") | ||
| except ImportError as e: | ||
| print(f"❌ Structlog import failed: {e}") | ||
|
|
There was a problem hiding this comment.
Critical bug: Missing import statements in dependency tests.
The test file is missing the actual import statements in each try block, making the environment verification completely ineffective. Each try block will always execute the success message regardless of whether the packages are installed.
Apply this diff to add the missing import statements:
try:
+ import openai
print("✅ OpenAI package imported successfully")
except ImportError as e:
print(f"❌ OpenAI import failed: {e}")
try:
+ import openai_agents
print("✅ OpenAI Agents package imported successfully")
except ImportError as e:
print(f"❌ OpenAI Agents import failed: {e}")
try:
+ import fastapi
print("✅ FastAPI package imported successfully")
except ImportError as e:
print(f"❌ FastAPI import failed: {e}")
try:
+ import pydantic
print("✅ Pydantic package imported successfully")
except ImportError as e:
print(f"❌ Pydantic import failed: {e}")
try:
+ import supabase
print("✅ Supabase package imported successfully")
except ImportError as e:
print(f"❌ Supabase import failed: {e}")
try:
+ import aiohttp
print("✅ Aiohttp package imported successfully")
except ImportError as e:
print(f"❌ Aiohttp import failed: {e}")
try:
+ import dotenv
print("✅ Python-dotenv package imported successfully")
except ImportError as e:
print(f"❌ Python-dotenv import failed: {e}")
try:
+ import structlog
print("✅ Structlog package imported successfully")
except ImportError as e:
print(f"❌ Structlog import failed: {e}")📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| try: | |
| print("✅ OpenAI package imported successfully") | |
| except ImportError as e: | |
| print(f"❌ OpenAI import failed: {e}") | |
| try: | |
| print("✅ OpenAI Agents package imported successfully") | |
| except ImportError as e: | |
| print(f"❌ OpenAI Agents import failed: {e}") | |
| try: | |
| print("✅ FastAPI package imported successfully") | |
| except ImportError as e: | |
| print(f"❌ FastAPI import failed: {e}") | |
| try: | |
| print("✅ Pydantic package imported successfully") | |
| except ImportError as e: | |
| print(f"❌ Pydantic import failed: {e}") | |
| try: | |
| print("✅ Supabase package imported successfully") | |
| except ImportError as e: | |
| print(f"❌ Supabase import failed: {e}") | |
| try: | |
| print("✅ Aiohttp package imported successfully") | |
| except ImportError as e: | |
| print(f"❌ Aiohttp import failed: {e}") | |
| try: | |
| print("✅ Python-dotenv package imported successfully") | |
| except ImportError as e: | |
| print(f"❌ Python-dotenv import failed: {e}") | |
| try: | |
| print("✅ Structlog package imported successfully") | |
| except ImportError as e: | |
| print(f"❌ Structlog import failed: {e}") | |
| try: | |
| import openai | |
| print("✅ OpenAI package imported successfully") | |
| except ImportError as e: | |
| print(f"❌ OpenAI import failed: {e}") | |
| try: | |
| import openai_agents | |
| print("✅ OpenAI Agents package imported successfully") | |
| except ImportError as e: | |
| print(f"❌ OpenAI Agents import failed: {e}") | |
| try: | |
| import fastapi | |
| print("✅ FastAPI package imported successfully") | |
| except ImportError as e: | |
| print(f"❌ FastAPI import failed: {e}") | |
| try: | |
| import pydantic | |
| print("✅ Pydantic package imported successfully") | |
| except ImportError as e: | |
| print(f"❌ Pydantic import failed: {e}") | |
| try: | |
| import supabase | |
| print("✅ Supabase package imported successfully") | |
| except ImportError as e: | |
| print(f"❌ Supabase import failed: {e}") | |
| try: | |
| import aiohttp | |
| print("✅ Aiohttp package imported successfully") | |
| except ImportError as e: | |
| print(f"❌ Aiohttp import failed: {e}") | |
| try: | |
| import dotenv | |
| print("✅ Python-dotenv package imported successfully") | |
| except ImportError as e: | |
| print(f"❌ Python-dotenv import failed: {e}") | |
| try: | |
| import structlog | |
| print("✅ Structlog package imported successfully") | |
| except ImportError as e: | |
| print(f"❌ Structlog import failed: {e}") |
🤖 Prompt for AI Agents
In ai-backend/tests/test_environment.py between lines 8 and 47, the try blocks
only print success messages without actually importing the packages, so they
always succeed regardless of package presence. To fix this, add the appropriate
import statements inside each try block before the print statement to properly
verify if the packages can be imported, ensuring the test accurately reflects
the environment status.
| async def test_get_fixtures_by_league(monkeypatch): | ||
| class MockResponse: | ||
| status = 200 | ||
|
|
||
| async def json(self): | ||
| return {"response": [{"fixture": 1, "league": 39, "season": 2025}]} | ||
|
|
||
| def raise_for_status(self): | ||
| pass | ||
|
|
||
| async def __aenter__(self): | ||
| return self | ||
|
|
||
| async def __aexit__(self, exc_type, exc, tb): | ||
| pass | ||
|
|
||
| class MockSession: | ||
| def get(self, *args, **kwargs): | ||
| return MockResponse() | ||
|
|
||
| client = APIFootballClient(api_key="test") | ||
| client.session = MockSession() | ||
| result = await client.get_fixtures(league=39, season=2025) | ||
| assert isinstance(result, list) | ||
| assert result[0]["league"] == 39 | ||
| assert result[0]["season"] == 2025 | ||
|
|
||
|
|
||
| @pytest.mark.asyncio | ||
| async def test_get_fixtures_by_league_missing_season(monkeypatch): | ||
| client = APIFootballClient(api_key="test") | ||
| result = await client.get_fixtures(league=39) | ||
| assert result == [] | ||
|
|
||
|
|
||
| @pytest.mark.asyncio | ||
| async def test_get_fixtures_by_date(monkeypatch): | ||
| class MockResponse: | ||
| status = 200 | ||
|
|
||
| async def json(self): | ||
| return {"response": [{"fixture": 2, "date": "2025-07-10"}]} | ||
|
|
||
| def raise_for_status(self): | ||
| pass | ||
|
|
||
| async def __aenter__(self): | ||
| return self | ||
|
|
||
| async def __aexit__(self, exc_type, exc, tb): | ||
| pass | ||
|
|
||
| class MockSession: | ||
| def get(self, *args, **kwargs): | ||
| return MockResponse() | ||
|
|
||
| client = APIFootballClient(api_key="test") | ||
| client.session = MockSession() | ||
| result = await client.get_fixtures(date="2025-07-10") | ||
| assert isinstance(result, list) | ||
| assert result[0]["date"] == "2025-07-10" | ||
|
|
||
|
|
||
| @pytest.mark.asyncio | ||
| async def test_get_fixtures_by_team(monkeypatch): | ||
| class MockResponse: | ||
| status = 200 | ||
|
|
||
| async def json(self): | ||
| return {"response": [{"fixture": 3, "team": 100}]} | ||
|
|
||
| def raise_for_status(self): | ||
| pass | ||
|
|
||
| async def __aenter__(self): | ||
| return self | ||
|
|
||
| async def __aexit__(self, exc_type, exc, tb): | ||
| pass | ||
|
|
||
| class MockSession: | ||
| def get(self, *args, **kwargs): | ||
| return MockResponse() | ||
|
|
||
| client = APIFootballClient(api_key="test") | ||
| client.session = MockSession() | ||
| result = await client.get_fixtures(team=100) | ||
| assert isinstance(result, list) | ||
| assert result[0]["team"] == 100 | ||
|
|
||
|
|
||
| @pytest.mark.asyncio | ||
| async def test_get_fixtures_by_multiple(monkeypatch): | ||
| class MockResponse: | ||
| status = 200 | ||
|
|
||
| async def json(self): | ||
| return { | ||
| "response": [ | ||
| { | ||
| "fixture": 4, | ||
| "league": 39, | ||
| "season": 2025, | ||
| "date": "2025-07-10", | ||
| "team": 100, | ||
| } | ||
| ] | ||
| } | ||
|
|
||
| def raise_for_status(self): | ||
| pass | ||
|
|
||
| async def __aenter__(self): | ||
| return self | ||
|
|
||
| async def __aexit__(self, exc_type, exc, tb): | ||
| pass | ||
|
|
||
| class MockSession: | ||
| def get(self, *args, **kwargs): | ||
| return MockResponse() | ||
|
|
||
| client = APIFootballClient(api_key="test") | ||
| client.session = MockSession() | ||
| result = await client.get_fixtures( | ||
| league=39, season=2025, date="2025-07-10", team=100 | ||
| ) | ||
| assert isinstance(result, list) | ||
| assert result[0]["league"] == 39 | ||
| assert result[0]["date"] == "2025-07-10" | ||
| assert result[0]["team"] == 100 | ||
|
|
||
|
|
||
| @pytest.mark.asyncio | ||
| async def test_get_fixtures_no_params(monkeypatch): | ||
| client = APIFootballClient(api_key="test") | ||
| result = await client.get_fixtures() | ||
| assert result == [] |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Consider adding error handling and edge case tests.
The current tests only cover happy path scenarios. Consider adding tests for:
- API errors (network failures, 4xx/5xx responses)
- Invalid parameter combinations
- Missing API key scenarios
- Malformed response data
Example additional test:
@pytest.mark.asyncio
@pytest.mark.unit
async def test_get_fixtures_api_error():
"""Test handling of API errors."""
class MockErrorResponse:
status = 500
async def json(self):
return {"error": "Internal server error"}
def raise_for_status(self):
raise aiohttp.ClientResponseError(None, None, status=500)
async def __aenter__(self):
return self
async def __aexit__(self, exc_type, exc, tb):
pass
class MockSession:
def get(self, *args, **kwargs):
return MockErrorResponse()
client = APIFootballClient(api_key="test")
client.session = MockSession()
result = await client.get_fixtures(league=39, season=2025)
assert result == [] # Should return empty list on error🤖 Prompt for AI Agents
In ai-backend/tests/test_fixtures.py around lines 7 to 144, the tests only cover
successful API responses and do not handle error or edge cases. Add new test
cases to simulate API errors such as network failures and 4xx/5xx responses by
mocking responses with error status and exceptions. Also add tests for invalid
parameter combinations, missing API key scenarios, and malformed response data
to ensure the client handles these gracefully, typically by returning empty
lists or appropriate error handling. Use async mocks for error responses and
verify the client returns expected fallback results.
| load_dotenv() | ||
|
|
||
| logging.basicConfig(level=logging.INFO) |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Consider removing global logging configuration.
Setting logging.basicConfig(level=logging.INFO) at the module level can interfere with application-level logging configuration and override existing settings. This is particularly problematic in larger applications where logging should be configured centrally.
Consider removing the global logging configuration:
load_dotenv()
-
-logging.basicConfig(level=logging.INFO)
logger = logging.getLogger(__name__)Let the application configure logging at the appropriate level instead.
🤖 Prompt for AI Agents
In ai-backend/tools/sports_apis.py around lines 17 to 19, remove the global
logging configuration call logging.basicConfig(level=logging.INFO) to avoid
overriding application-wide logging settings. This allows the main application
to control logging configuration centrally without interference from this
module.
1 participant
Description
Implement Football Fixtures Endpoint
Type of Change
Changes Made
Testing
How has this been tested?
Test Configuration:
Platform Impact
Which parts of the system are affected?
Breaking Changes
Does this PR introduce any breaking changes?
If yes, describe the breaking changes and migration path:
Checklist
Before requesting a review, please ensure:
Screenshots (if applicable)
Add screenshots to help explain your changes.
Related Issues
Closes #(issue_number)
Related to #(issue_number)
Additional Notes
Any additional information that reviewers should know.
Summary by CodeRabbit
New Features
Bug Fixes
Tests
Chores
Refactor