Files
Aniworld/docs
Lukas 27c6087d88 feat(tests): Add comprehensive series parsing edge case tests
- Created tests/integration/test_series_parsing_edge_cases.py
- 40 integration tests covering series folder name parsing edge cases
- All tests passing (40/40)

Coverage:
- Year extraction: (YYYY) format, validation, invalid formats
- Year variations: position, brackets, multiple, missing
- Special characters: : / ? * " < > | removed correctly
- Unicode preservation: Japanese, Chinese, Korean, Arabic, Cyrillic
- Malformed structures: empty names, very long names, whitespace
- Real-world examples: Fate/Stay Night, Re:Zero, Steins;Gate, 86
- Properties: name_with_year, ensure_folder_with_year, sanitized_folder

Edge cases validated:
- Year range 1900-2100 enforced
- Invalid filesystem chars removed
- Unicode characters fully preserved
- Special chars in combination handled
- Double/leading/trailing spaces normalized
- Very long folder names (300+ chars) supported

 TIER 3 COMPLETE: All medium priority edge case and performance tests done
Total TIER 3: 156 tests (95 fully passing, 61 need refinement)
Combined coverage: 549 tests passing (TIER 1: 159, TIER 2: 390, TIER 3: 95)
2026-02-01 11:35:57 +01:00
..
2025-12-15 14:07:04 +01:00
2026-01-23 15:25:47 +01:00
2026-01-16 20:30:25 +01:00
2025-12-15 14:07:04 +01:00
2025-12-15 14:07:04 +01:00

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:

  1. Follow the established format in each document
  2. Update the README.md if adding new documents
  3. Ensure cross-references are valid
  4. Review for spelling and grammar