Lukas
bd5538be59
E2E Tests (tests/frontend/e2e/settings_modal.spec.js): - Modal open/close: button, overlay, Escape (5 tests) - Configuration sections: all sections display (5 tests) - Load configuration: directory, count, scheduler, status (4 tests) - Edit fields: name, directory, scheduler, interval (6 tests) - Save configuration: main, scheduler, feedback (4 tests) - Reset configuration to original values (2 tests) - Browse directory functionality (2 tests) - Connection test and status update (2 tests) - Scheduler status: next/last rescan, running (3 tests) - Accessibility: labels, keyboard nav, focus trap (4 tests) - Edge cases: rapid changes, long inputs, multiple opens (5 tests) - Theme integration: respect theme, toggle (2 tests) Total: 44 E2E tests Integration Tests (tests/integration/test_config_backup_restore.py): - Backup creation: default/custom name, auth, file creation (6 tests) - Backup listing: array, metadata, recent, auth (5 tests) - Backup restoration: valid, nonexistent, pre-backup, auth (6 tests) - Backup deletion: existing, removes file/list, auth (5 tests) - Complete workflows: full cycle, multiple cycles (3 tests) - Edge cases: invalid names, concurrent ops, long names (4 tests) Total: 29 integration tests Updated instructions.md marking settings modal tests complete
Aniworld Documentation
Overview
This directory contains all documentation for the Aniworld anime download manager project.
Documentation Structure
| Document | Purpose | Target Audience |
|---|---|---|
| ARCHITECTURE.md | System architecture and design decisions | Architects, Senior Developers |
| API.md | REST API reference and WebSocket documentation | Frontend Developers, API Consumers |
| DEVELOPMENT.md | Developer setup and contribution guide | All Developers |
| DEPLOYMENT.md | Deployment and operations guide | DevOps, System Administrators |
| DATABASE.md | Database schema and data models | Backend Developers |
| TESTING.md | Testing strategy and guidelines | QA Engineers, Developers |
| SECURITY.md | Security considerations and guidelines | Security Engineers, All Developers |
| CONFIGURATION.md | Configuration options reference | Operators, Developers |
| CHANGELOG.md | Version history and changes | All Stakeholders |
| TROUBLESHOOTING.md | Common issues and solutions | Support, Operators |
| features.md | Feature list and capabilities | Product Owners, Users |
| instructions.md | AI agent development instructions | AI Agents, Developers |
Documentation Standards
- All documentation uses Markdown format
- Keep documentation up-to-date with code changes
- Include code examples where applicable
- Use clear, concise language
- Include diagrams for complex concepts (use Mermaid syntax)
Contributing to Documentation
When adding or updating documentation:
- Follow the established format in each document
- Update the README.md if adding new documents
- Ensure cross-references are valid
- Review for spelling and grammar