How pondersource/dev-stock works
Main Components
a) Testing Infrastructure Layer:
• Cypress Test Runner
• GitHub Actions CI Pipeline
• Docker Container Environment
b) Platform Layer:
• EFSS Platforms (Nextcloud, ownCloud, oCIS, Seafile)
• OCM Stub Implementation
• Reva Middleware
c) Test Categories Layer:
• Login Tests
• Share Link Tests
• Share With Tests
• Invite Link Tests
Relationships and Data Flow
• Control flow from CI pipeline to Docker containers
• Test execution flow from Cypress to platforms
• Integration points between Reva and EFSS platforms
Component Details
Docker Environment:
┌─ Docker Environment ──────────────────┐
• ┌─ EFSS Containers ─┐ ┌─ Support ──┐ │
• Nextcloud │ │ - Reva │ │
• ownCloud │ │ - OCMStub │ │
• oCIS │ │ - Database │ │
• Seafile │ └───────────┘ │
• ┘ │
• ┘
Testing Framework:
┌─ Test Infrastructure ───────────────┐
• ┌─ Cypress ──┐ ┌─ CI Pipeline ───┐ │
• E2E Tests │ │ GitHub Actions │ │
• Scenarios │ │ Status Badges │ │
• ┘ └────────────────┘ │
• ┘
Implementation Details
Technical annotations for:
• Docker image versions
• Platform versions
• Test suite organization
• Configuration paths
Architectural Patterns
Highlight:
• Microservices architecture (Docker containers)
• Test automation patterns
• Integration patterns for OCM
• Configuration management
Cross-cutting concerns on the sides
Key considerations:
• Clear separation between test environments
• Version compatibility matrices
• OCM protocol flows
• Test scenario coverage
This system design should emphasize the project's focus on testing interoperability between different EFSS platforms while maintaining a clear view of the infrastructure supporting these tests.