Skip to content

Conversation

@olaservo
Copy link
Member

@olaservo olaservo commented Jun 25, 2025

Description

Added automated testing support to the Python CI workflow to run pytest tests for Python MCP servers. The workflow now detects packages with tests and runs them .

Server Details

  • Server: CI/CD Infrastructure (affects all 3 Python servers, although fetch doesn't appear to have any tests yet)
  • Changes to: GitHub Actions workflow for Python packages

Motivation and Context

The repository lacked test automation for Python servers. This change ensures that:

  • Python server tests are automatically run on every push and PR
  • Tests must pass before packages are built and published

How Has This Been Tested?

  • Verified the workflow detects Python packages correctly (git, time servers screenshots below)

time

git

Breaking Changes

No breaking changes. This is purely a CI/CD enhancement that doesn't affect server functionality or client configurations.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Protocol Documentation
  • My changes follows MCP security best practices
  • I have updated the server's README accordingly
  • I have tested this with an LLM client
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have documented all environment variables and configuration options

@olaservo olaservo marked this pull request as ready for review June 25, 2025 11:54
@olaservo olaservo enabled auto-merge June 25, 2025 11:54
@olaservo olaservo merged commit 6b0c30d into modelcontextprotocol:main Jun 26, 2025
18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants