mr-test-cases

Generate prioritized test cases from GitLab Merge Request branch diffs.

3|4|Updated Nov 30, 2023

Search Tags:#automation #testing #code review #qa #gitlab #merge request

One-click install

npx skills add https://github.com/openhive-network/denser --skill mr-test-cases

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: mr-test-cases
Source: https://github.com/openhive-network/denser/tree/main/.claude/skills/mr-test-cases
Command: npx skills add https://github.com/openhive-network/denser --skill mr-test-cases

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the generation of comprehensive test cases for Merge Requests, ensuring thorough quality assurance before code is merged.

Core Features & Use Cases

Automated Diff Analysis: Compares changes between branches to identify affected code areas.
Prioritized Test Case Generation: Creates test cases categorized by priority (P0-P4) based on impact.
Use Case: When a developer submits a Merge Request, this Skill can automatically generate a list of critical tests to be performed, covering UI, API, and utility changes, ensuring no regressions are introduced.

Quick Start

Generate test cases for the current merge request by running the mr-test-cases skill.

Frequently Asked Questions about mr-test-cases

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate test cases for a GitLab Merge Request automatically?▼

Merge Request test case generation works by comparing branch diffs to identify affected components, utilities, and API calls. It then produces prioritized test cases categorized by impact level from P0 to P4, ensuring comprehensive coverage for software engineering workflows.

What is the best way to ensure comprehensive test coverage before merging code changes?▼

The best way to ensure test coverage is by automating diff analysis between branches to identify affected code areas. This generates prioritized test cases covering UI, API, and utility changes to prevent regressions before code is merged.

Can I generate test cases by comparing local branches instead of providing a GitLab URL?▼

Yes, you can generate test cases using local branch comparisons. The process supports both GitLab MR URLs and local branch diffs to provide deterministic test planning for your code changes.

How are generated test cases prioritized during automated QA analysis?▼

Generated test cases are prioritized into categories from P0 to P4 based on the impact of the identified code changes. This ensures critical UI, API, and utility modifications receive appropriate testing attention.

Does automated merge request test generation work without external dependencies?▼

Yes, automated merge request test generation operates without external dependencies. It performs diff analysis and prioritized test case generation using only the provided branch comparisons or GitLab MR URLs.