For QA

Redmine AI plugin for QA – test cases from spec docs, in seconds.

For QA teams running release cycles on Redmine.

MCP server live · 51 tools Test Case Management plugin live Test Agent in trial

Get a Free Demo See pricing →

The QA day, with AI

Six tasks QA teams spend hours on – each becomes a sentence.

Sourced from the 59-scenario test set used to validate the MCP server. Real interactions, real Redmine data.

Cross-project QA queue

“What needs QA across all projects?”

AI: 34 issues need QA verification across 6 projects. Phoenix: 12 (1 critical-path). Mercury: 8 (App Store cut blocker). Atlas: 5. Three issues sitting >7 days without test sign-off - flag for review.

Time: 15 minutes of cross-project filtering → 4 seconds.

Test case generation

“Generate test cases for the new password-reset flow in #3066.”

AI: Drafted 8 test cases linked to issue #3066: happy path, expired token, used token, locked account, mismatched email, rate-limit trigger, password-policy fail, audit-log assertion. Saved as TC-2026-04-26-{a..h}.

Time: 30 minutes of spec parsing + writing → 12 seconds.

Regression check

“Anything closed-WontFix that I should re-test?”

AI: 4 issues closed-WontFix in last sprint that touched changed code paths: #2814 (auth), #2854 (billing), #2912 (audit log), #2967 (Stripe webhook). Recommend smoke regression on each before milestone close.

Time: hand-correlate code-paths to closed bugs → 6 seconds.

Failed-build triage

“Which test runs failed yesterday and what bugs did they raise?”

AI: 3 failures yesterday from CI runs #4421, #4423, #4427. All 3 raised auto-issues - #3082 (flaky e2e on Safari), #3083 (DB migration timing), #3084 (rate-limit threshold). #3083 is High priority - assigned to James.

Time: cross-reference 3 systems → 5 seconds.

Coverage check

“Which features in Phoenix have no test cases linked?”

AI: 14 Phoenix features have no test cases linked: 6 in milestone “v2 launch” (concerning), 5 in “v2.1”, 3 backlog. The v2-launch ones: #2972, #2947, #2891, #2814, #3014, #3052 - recommend prioritising.

Time: manual coverage spreadsheet update → 4 seconds.

Sign-off readiness

“Is the auth-refresh release ready for QA sign-off?”

AI: Auth-refresh - 5 issues, 23 test cases. Status: 22/23 passed, 1 blocked (#3070 migration timing - High). Code coverage 87%. Recommendation: hold sign-off pending #3070 resolution OR scope auth-refresh narrower (excluding migration).

Time: spreadsheet wrangling + Slack questions → 8 seconds.

How it works today

QA teams use the MCP server through any AI assistant.

No new tools. Use Claude or ChatGPT to query Redmine. The MCP server exposes Test Case plugin tools alongside the core Redmine surface – so coverage checks, run results, and test case generation all happen against live data.

Read the MCP server spec → See the Test Case plugin →

In trial with early customers

A specialist Test Agent – bundled with the Test Case Management plugin.

The Test Agent will live inside Redmine’s Test Case page. Drop in a spec doc, get test cases linked to the right issue. Ask “what’s the regression set” and it builds one from your closed-bug history. Bundled with the Test Case Management plugin renewal – no separate SKU.

See the agent roadmap →