refactor: move Gitea integration tests to release-management capability
Moved 35 Gitea API integration tests from main markitect test suite to the release-management capability where the Gitea functionality now resides. Changes: - Moved: tests/test_l6_integration_gitea_api.py -> capabilities/release-management/tests/test_gitea_integration.py - Updated documentation to clarify these tests are for future functionality - Tests remain skipped as Gitea issue/milestone/label management is not yet implemented in the capability (only package registry operations exist) The tests serve as specification for future features: - Issue management (create, update, close) - Milestone tracking - Label operations Test Results: - Main markitect: 1,158 passed, 3 skipped (down from 38 skipped) - Capability: 35 tests available, all skipped (future functionality) This separation improves test organization by keeping tests with the code they're intended to test, even if that functionality isn't implemented yet. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
This commit is contained in:
@@ -1,21 +1,38 @@
|
||||
"""
|
||||
Comprehensive tests for the Gitea facade/integration layer.
|
||||
Tests for Gitea Issue/Milestone/Label Management (Future Functionality)
|
||||
|
||||
This test suite covers all Gitea API operations through the facade pattern,
|
||||
ensuring the gitea.client module provides reliable, well-tested functionality
|
||||
for the rest of the application.
|
||||
IMPORTANT: These tests are for Gitea issue tracker integration functionality
|
||||
that is NOT YET IMPLEMENTED in the release-management capability.
|
||||
|
||||
NOTE: This test suite needs to be updated for the new capability-based architecture
|
||||
where Gitea functionality has been moved to capabilities/release-management.
|
||||
Skipping for now until the test can be restructured or moved to the appropriate capability.
|
||||
The current release-management capability focuses on:
|
||||
- Package registry operations (GiteaRegistry)
|
||||
- Version management and tagging
|
||||
- Package building and publishing
|
||||
|
||||
This test suite covers future Gitea API operations for:
|
||||
- Issue management (create, update, close issues)
|
||||
- Milestone tracking
|
||||
- Label operations
|
||||
|
||||
These tests serve as:
|
||||
1. Specification for future issue management features
|
||||
2. Documentation of expected API behavior
|
||||
3. Placeholder for when issue tracking integration is added
|
||||
|
||||
Current Status: SKIPPED - Functionality not implemented
|
||||
Related: capabilities/release-management/src/release_management/registries/gitea/
|
||||
"""
|
||||
|
||||
import pytest
|
||||
from unittest.mock import Mock, MagicMock, patch
|
||||
from datetime import datetime
|
||||
|
||||
# Skip all tests in this file until gitea tests are moved to release-management capability
|
||||
pytestmark = pytest.mark.skip(reason="Gitea functionality moved to release-management capability - tests need restructuring")
|
||||
# Skip all tests - this functionality doesn't exist in the capability yet
|
||||
# Remove this skip marker when implementing Gitea issue management features
|
||||
pytestmark = pytest.mark.skip(
|
||||
reason="Gitea issue/milestone/label management not yet implemented in release-management capability. "
|
||||
"Current capability only supports package registry operations."
|
||||
)
|
||||
|
||||
|
||||
class TestGiteaConfig:
|
||||
Reference in New Issue
Block a user