Related Issues/PRs

What changes are proposed in this pull request?

The redundant-test-docstring clint rule previously used string similarity heuristics to determine if a single-line test docstring was redundant. This PR simplifies the rule to flag all single-line test docstrings, as they rarely add meaningful context beyond what the test name already conveys.

Rule changes:

• Removed similarity check logic (_is_redundant_docstring method and related imports)
• Now flags any single-line docstring in test functions, test classes, and test modules
• Updated error messages for clarity

Codebase cleanup:

• Created automation script to remove flagged docstrings
• Removed 546 single-line test docstrings across 104 files
• Verified zero violations remain with uv run clint .

Before:

def test_feature_validation():
    """Test feature validation."""  # Only flagged if similar to function name
    assert validate_feature()

After:

def test_feature_validation():
    # All single-line docstrings now flagged, multi-line still allowed
    assert validate_feature()

How is this PR tested?

• Existing unit/integration tests
• New unit/integration tests
• Manual tests

Updated test expectations in test_redundant_test_docstring.py to reflect new behavior. All 11 tests pass.

Does this PR require documentation update?

• No. You can skip the rest of this section.
• Yes. I've updated:
  • Examples
  • API references
  • Instructions

Release Notes

Is this a user-facing change?

• No. You can skip the rest of this section.
• Yes. Give a description of this change to be included in the release notes for MLflow users.

What component(s), interfaces, languages, and integrations does this PR affect?

Components

• area/tracking: Tracking Service, tracking client APIs, autologging
• area/models: MLmodel format, model serialization/deserialization, flavors
• area/model-registry: Model Registry service, APIs, and the fluent client calls for Model Registry
• area/scoring: MLflow Model server, model deployment tools, Spark UDFs
• area/evaluation: MLflow model evaluation features, evaluation metrics, and evaluation workflows
• area/gateway: MLflow AI Gateway client APIs, server, and third-party integrations
• area/prompts: MLflow prompt engineering features, prompt templates, and prompt management
• area/tracing: MLflow Tracing features, tracing APIs, and LLM tracing functionality
• area/projects: MLproject format, project running backends
• area/uiux: Front-end, user experience, plotting, JavaScript, JavaScript dev server
• area/build: Build and test infrastructure for MLflow
• area/docs: MLflow documentation pages

How should the PR be classified in the release notes? Choose one:

• rn/none - No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" section
• rn/breaking-change - The PR will be mentioned in the "Breaking Changes" section
• rn/feature - A new user-facing feature worth mentioning in the release notes
• rn/bug-fix - A user-facing bug fix worth mentioning in the release notes
• rn/documentation - A user-facing documentation change worth mentioning in the release notes

Should this PR be included in the next patch release?

• Yes (this PR will be cherry-picked and included in the next patch release)
• No (this PR will be included in the next minor release)

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.