How kamiljaneczek/c11n-testing works
Main Components Identification
The system should be represented with these key components:
a) Test Execution Layer
• Playwright Test Runner
• Cucumber Test Runner
• CLI Interface (test_runner/cli.ts)
b) Test Definition Layer
• Feature Files (features/*.feature)
• Step Definitions (step-definitions/*)
• E2E Tests (e2e/*)
c) Support Infrastructure
• Test Data Management (data/*)
• Library Components (lib/*)
• Configuration Management (config/*)
Component Relationships
Test Execution Layer
• ↓
Test Definition Layer
• ↓
Support Infrastructure
• ↓
System Under Test (External)
Specific Implementation Details
┌─ Test Execution Layer ─────────────────┐
• Playwright Runner │
• Cucumber Runner │
• CLI Interface │
• ┘
• ↓
┌─ Test Definition Layer ────────────────┐
• ┌─ Features ─┐ ┌─ E2E Tests ─┐ │
• Cucumber │ │ API Tests │ │
• Features │ │ UI Tests │ │
• ┘ └────────────┘ │
• ┌─ Step Definitions ─┐ │
• Case Worker │ │
• Dispatcher │ │
• Incident │ │
• Portal │ │
• ┘ │
• ┘
• ↓
┌─ Support Infrastructure ──────────────┐
• ┌─ Library ─┐ ┌─ Test Data ─┐ │
• API │ │ Case Data │ │
• Fixtures │ │ User Data │ │
• Controls │ │ Portal Data │ │
• ┘ └────────────┘ │
• ┌─ Configuration ─┐ │
• Environment │ │
• Playwright │ │
• Cucumber │ │
• ┘ │
• ┘
Important Elements
a) Authentication Flow:
• How different user roles (Customer, Case Worker, Manager, Dispatcher) are handled
• API authentication with CLIENT_ID/CLIENT_SECRET
b) Test Data Management:
• Relationship between JSON schemas and test data
• How fixtures are used
c) Test Types:
• Distinguish between API and UI tests
• Parallel test execution capability