CARBON — Engineering ConfidenceUser Guide
CHAPTER 53 / 60 Pro

/carbon-integrations

Connect CARBON to Jira with Xray or TestRail so external test cases, results, and known issues can inform plans and reports.

Jay · Your AI test managerTesting operations

When to use it

Your issue tracker or test manager holds relevant quality evidence.

Before you start

Start with an approved account and read-only mapping. Review exactly what would be synchronized before authorizing writes. A local proposal is not a created Jira issue or TestRail result.

Try this in your coding agent.

/carbon-integrations Propose a Jira and TestRail mapping for checkout tests; do not write externally yet.

Replace sample paths with your project. Slash names are shorthand; your host may use a plugin prefix or a skill picker. Invocation help →

ILLUSTRATIVE WALKTHROUGH

Jira and TestRail mapping

An expanded teaching example, not a recorded or live execution. The report stays visible while the replay explains how to read it.

  1. 01Read context
  2. 02Analyze
  3. 03Show evidence
  4. 04Report

Coding-agent conversation

Read context

I’m reviewing jira and testrail mapping. I’ll keep the scope and permissions explicit.

Analyze

Analyze: Propose a Jira and TestRail mapping for checkout tests; do not write externally yet.

Show evidence

Here is the evidence trail to inspect: Local finding → proposed Jira issue fields → proposed TestRail case and evidence URL.

Report

A proposed mapping links findings, test cases and evidence without writing externally. Account access and approval are required before external writes.

CARBON

Example report

Illustration
Project → decisions → retained evidence
Project → decisions → retained evidence — TestBucks teaching screen

TestBucks course screen with illustrative analysis. The screenshot supplies context; the demo does not establish a newly observed bug.

  1. TestBucks project
  2. Command action
  3. Reviewable output

Illustrated outcome

A proposed mapping links findings, test cases and evidence without writing externally.

Evidence to inspect

Local finding → proposed Jira issue fields → proposed TestRail case and evidence URL.

Still untested / not established

Account access and approval are required before external writes.

Ready. Read the full example or play its steps.

What a useful result contains

A bounded claim

For jira and testrail mapping, state the target, revision, environment and actual work performed. Keep planned, executed, blocked and untested work separate.

An inspectable trail

Local finding → proposed Jira issue fields → proposed TestRail case and evidence URL. In a real run, retain the source, trace, screenshot or fixture behind the conclusion.

The qualification

Account access and approval are required before external writes.

The next decision

Decide whether the evidence calls for a focused check, a reviewed fix or more context. Do not convert a plausible example into a verified finding.

Adapt the example to your project

  1. Replace jira and testrail mapping with a real feature, path or decision in your project.
  2. State the expected rule and its source. Include safe fixtures, constraints and a budget where appropriate.
  3. Ask for exact evidence and remaining gaps. Approve consequential actions separately.
/jay Review the /carbon-integrations result. Separate observed evidence, assumptions and untested scope, then recommend the next useful check.

Where to go next

/carbon-tests →/carbon-settings →

Content checked against the local command definition: skills/carbon-integrations/SKILL.md. Examples adapted from the homepage’s TestBucks walkthroughs. Availability is edition- and host-dependent.