Skip to content

Clarify difference between eval-driven development and test-driven development in docs #315

@cantemizyurek

Description

@cantemizyurek

This distinction is important because eval-driven development isn’t about achieving perfect (100%) scores like test-driven development is about passing all tests. Instead, it’s focused on continuous improvement always getting better than before, even if some metrics never reach 100%.

Adding this explanation will help readers set the right expectations and understand that not all metrics need to be “perfect” for eval-driven development to be working as intended.

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions