Skip to content

Comprehensive Testing Plan for GitLab MCP Server

Testing Plan Overview

Once issue #9 (closed) (MCP Server Functions Not Available) is resolved, the following comprehensive testing plan should be executed to validate all GitLab MCP server functionality.

Phase 1: Read Operations Testing

Repository Operations

  • search_repositories - Search for repositories by name/keyword
  • get_branches - List all branches in repository
  • get_branch - Get specific branch information
  • get_file_contents - Read file contents from repository

Test Repository: john/melange-mvp-template Expected Files to Test: CLAUDE.md, package.json, .gitlab-ci.yml

Issue Operations

  • get_issues - List all issues with pagination
  • get_issue - Get specific issue details
  • get_issue_notes - Get comments/notes on issues

Test Cases: Repository should have existing issues to test against

Merge Request Operations

  • get_merge_requests - List all MRs with filtering
  • get_merge_request - Get specific MR details

CI/CD Operations

  • get_pipelines - List pipelines with status
  • get_latest_pipeline - Get most recent pipeline
  • get_pipeline - Get specific pipeline details
  • get_pipeline_jobs - List jobs in pipeline
  • get_jobs - List jobs
  • get_job - Get specific job details
  • get_job_log - Get job execution logs

Metadata Operations

  • get_variables - List project variables
  • get_labels - List available labels
  • get_milestones - List project milestones

Phase 2: Write Operations Testing

Test Repository: Create john/mcp-test-repo for write testing

Issue Management

  • create_issue - Create new issues
  • Test with various labels, milestones, assignees
  • Test with markdown formatting in descriptions
  • Verify proper error handling for invalid data

Test Validation Criteria

Each operation should be tested for:

  1. Success Cases: Normal operation with valid inputs
  2. Error Handling: Invalid inputs, non-existent resources
  3. Edge Cases: Empty results, large datasets, special characters
  4. Authentication: Proper handling of permissions
  5. Data Integrity: Returned data matches GitLab web interface

Test Environment Setup

  • Host: git.haley.io (GitLab CE self-hosted)
  • Authentication: glab CLI pre-configured
  • Test against real repository data
  • Document any API limitations or differences from GitLab.com

Reporting Requirements

For each issue found:

  • Exact function call and parameters used
  • Expected vs actual behavior
  • Full error messages and stack traces
  • Steps to reproduce
  • Impact assessment

Success Metrics

  • All read operations return expected data
  • Write operations create/modify resources correctly
  • Error handling provides meaningful messages
  • Performance is acceptable for typical use cases
  • Integration works seamlessly in Claude Code environment