Skip to content

Expand test coverage for contrib/components and core modules #205

@manaspros

Description

@manaspros

Problem

Currently, the project has limited test coverage with only 24 test files covering 151 source files (~16% ratio).
Several critical areas have no test coverage at all:

  • contrib/components/: 25 source files, 0 test files
  • contrib/language_models/: 10 provider implementations, minimal integration tests
  • components/game_master/: 15 files, only 4 test files
  • environment/engines/: 4 engine implementations, 3 test files

Impact

Low test coverage leads to:

  • Increased risk of regressions when refactoring
  • Difficulty ensuring new contributions work correctly
  • Reduced confidence in production deployments
  • Harder to validate bug fixes

References


I'm interested in working on this . I can start with Phase 1 (contrib/components) and
gradually expand coverage across the codebase.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions