Skip to content

Configurable behavior when no tests match (--no-tests) #553

@MatthewMckee4

Description

@MatthewMckee4

When no tests match the given filters, karva should let the user control the behavior:

  • --no-tests=pass — exit 0 (useful in CI with dynamic filters)
  • --no-tests=warn — exit 0 but print a warning
  • --no-tests=fail — exit non-zero (current behavior / good default)

This avoids false positives in CI when filter expressions legitimately match nothing on certain platforms or configurations.

See: https://nexte.st/docs/running/#options-and-arguments

Metadata

Metadata

Assignees

No one assigned

    Labels

    cliRelated to the command-line interfacetest-runningRelated to running tests with karva

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions