sdlc-agent-12-testing

Runs integration, regression, and performance tests on Databricks and writes a test report artifact.

1|2|Updated Aug 10, 2026
One-click install
npx skills add https://github.com/TRRaveendra/AI-Agents-Databricks --skill sdlc-agent-12-testing-trraveendra
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdlc-agent-12-testing
Source: https://github.com/TRRaveendra/AI-Agents-Databricks/tree/main/ai-agent-skills/databricks-sdlc-agent-skills/12-testing-agent
Command: npx skills add https://github.com/TRRaveendra/AI-Agents-Databricks --skill sdlc-agent-12-testing-trraveendra

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires databricks-sdk, mlflow, and includes references (resource) components.

What problem does it solve? In a multi-agent Databricks SDLC pipeline, unit test results alone do not prove a pipeline works end-to-end. This Skill acts as Agent 12 of 15, executing integration, regression, and performance tests against a staging schema and producing a consolidated test report that downstream Documentation and Deployment agents consume. ## Core Features & Use Cases - End-to-end test execution: Runs integration, regression, and performance tests against a staging schema/cluster, validating source counts versus target counts and spot-checking transformed rows. - Contract-validated output: Returns JSON matching a strict output contract (status, artifact_path, citations, tool_calls, tokens) that the LangGraph orchestrator validates before handoff. - Lakehouse artifact persistence: Writes test_report.md to /Volumes/{catalog}/state/artifacts/{ticket}/12_testing-agent/ and upserts tracking rows into state.artifacts and state.agent_runs. - Use Case: After the Unit Test Agent finishes, the pipeline hands its results to this agent, which runs regression suites on staging, detects a row-count mismatch, and returns needs_clarification with specific questions instead of inventing results. ## Quick Start Hand this agent the Unit Test results for a ticket and ask it to run integration, regression, and performance tests on the staging schema and write the test report artifact.

Frequently Asked Questions about sdlc-agent-12-testing

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

FAQPage Schema
How do I run integration and regression tests in a Databricks agent pipeline?

Hand the unit test results from the upstream agent to this Testing Agent, which runs integration, regression, and performance tests against a staging schema or cluster. It validates source versus target row counts and writes a consolidated test_report.md artifact to the lakehouse.

What API should Databricks agents use for code generation instead of Genie Code?

Genie Code has no public API and cannot be invoked headlessly. Use the Databricks Foundation Model API (Model Serving pay-per-token endpoints such as databricks-claude-sonnet-4-5) or a deployed Mosaic AI Agent endpoint for code, SQL, and document generation.

Can Genie Agents API be used to write production code in Databricks?

No. The Genie Agents Conversation API answers natural-language data questions but does not write general production code. Use it only as a tool for ad-hoc profiling or business-metric queries, not as a code generation backend.

What happens when the testing agent output fails contract validation?

The agent gets one repair retry with the validation error appended to its context. If the retry still fails, the run is routed to state.needs_human so the approval-gate agents can review it.

When does the testing agent return needs_clarification status?

It returns needs_clarification when required upstream context is missing or contradictory, including specific questions for the orchestrator. It never invents metadata, business rules, or test results to fill gaps.