Skip to content

Demo outputs clean - #24

Open
antowaddle wants to merge 3 commits into
mainfrom
demo-outputs-clean
Open

Demo outputs clean#24
antowaddle wants to merge 3 commits into
mainfrom
demo-outputs-clean

Conversation

@antowaddle

Copy link
Copy Markdown
Owner

Demo Output

antowaddle and others added 3 commits April 29, 2026 10:54
Demo artifacts for 3 skills:
1. Risk Assessment (PR #489) - WARN decision with orange color
   - Successfully detects RHOAIENG-57824 ConfigMap rename pattern
   - Shows MEDIUM blast radius, 9 breaking tests, cross-repo coordination needed
   - Fixed decision engine to trigger WARN on qualitative factors

2. Quality Analysis (MAAS) - Repository quality scorecard
   - Comprehensive analysis of models-as-a-service repository
   - CI/CD, test coverage, code quality, security practices

Files included:
- artifacts/pr-analyses/pr-489-analysis.html (WARN - orange)
- demo-outputs/quality-report-models-as-a-service.html
- .claude/skills/risk-assessment/scripts/decision_engine.py (WARN logic fix)
- .claude/skills/risk-assessment/scripts/html_generator.py (orange color fix)

Co-Authored-By: Claude Sonnet 4.5 <[email protected]>
143 blocker bugs analyzed:
- 6% COVERED (9 bugs)
- 13% PARTIALLY COVERED (19 bugs)
- 76% GAP (110 bugs)
- 3% NOT TESTABLE (5 bugs)

Co-Authored-By: Claude Sonnet 4.5 <[email protected]>
Generate Claude Code agent rules for automated test creation in the
opendatahub-io/notebooks repository. This demonstrates the test-rules-generator
skill's ability to analyze existing test patterns and create actionable
testing guidance.

## What's Included

- Testing standards (cross-cutting principles)
- Python integration tests (pytest + testcontainers)
- Python unit tests (pytest)
- Playwright browser tests (TypeScript)
- Comprehensive analysis report

## Key Metrics

- 4 rule files + README (~2,550 lines)
- 15+ test files analyzed
- 100+ code examples extracted
- 3 test types covered (integration, unit, browser)

## Output Structure

test-rules-outputs/
└── notebooks/
    ├── .claude/rules/     # Generated test rules
    └── TEST-RULES-ANALYSIS.md

Co-Authored-By: Claude Sonnet 4.5 <[email protected]>
antowaddle added a commit that referenced this pull request Apr 30, 2026
Add qualitative factors to decision-making beyond just numeric risk score:

**decision_engine.py:**
- Override to WARN if blast radius is MEDIUM or HIGH (coordination required)
- Override to WARN if breaking tests >= 5 (cross-repo impact)
- Override to WARN for K8s resource renames with cross-repo refs (RHOAIENG-57824)
- Base numeric decision remains: 0-40 = APPROVE, 41-100 = WARN

**html_generator.py:**
- Show minimum "medium" (orange) color for WARN decisions
- Prevents confusing UI: low numeric score (green) with WARN decision
- APPROVE decisions still use score-based coloring

These changes make the advisory system more intelligent - it considers both
quantitative (risk score) and qualitative factors (blast radius, coordination
needs, breaking test count) when making recommendations.

From: PR #24 (demo-outputs-clean branch)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant