CCARF Practice Question

Paper 3 · Question 42

D3 Claude Code Configuration & Workflows · Paper 3

[Scenario 5: Claude Code for Continuous Integration] You are integrating Claude Code into a CI/CD pipeline for automated code review, test generation, and pull-request feedback — designing prompts that produce actionable findings while minimizing false positives. CI-generated tests ignore your team's fixture library, duplicate helper setup, and test trivialities. Developers reject most of them. What is the configuration-level fix?

• A.Generate three times as many tests so some survive review
• B.Have developers rewrite the generated tests as a standing chore
• C.Lower the temperature of the generation call
• D.Document testing standards, what makes a test valuable, and the available fixtures in CLAUDE.md — the mechanism that supplies project context to CI-invoked Claude Code

Show answer & explanations

Correct answer: D

A: scales the reject pile

B: institutionalizes rework instead of fixing its cause

C: reduces variability of output that is uninformed either way

D: CI invocations get their project context from CLAUDE.md. Standards, value criteria, and fixture documentation there directly raise generation quality — the model can only follow conventions it has been shown.

Related Claude Code Configuration & Workflows questions

More: Paper 3 · All practice questions