How githubmaster07/enterprise-test-strategy-blueprint works
This is a documentation-first Quality Engineering blueprint, not an executable test framework. Its principal workflow turns business risk into test depth, automation and layer choices, CI/CD evidence, a release recommendation, and feedback for reassessment. The graph follows the README’s documented relationships; source excerpts were unavailable, so implementation-level calls are not inferred.
Main entry points: Test-Layers.md Test Layers · Test-Strategy.md Test Strategy · CI-CD.md CI/CD Gates · Release-Readiness.md Release Readiness
Components 15
Strategy
- Risk Assessment
docs/Risk-Based-Testing.md - Test Strategy
docs/Test-Strategy.md - Automation Decision
docs/Automation-Decision-Framework.md - Manual Exploration
docs/Test-Strategy.md
Test Design
- Test Layers
docs/Test-Layers.md - Framework Architecture
docs/Framework-Architecture.md - Reference Examples
docs/Examples - Advanced Testing
docs/Advanced-Testing.md
Release Evidence
- CI/CD Gates
docs/CI-CD.md - Release Readiness
docs/Release-Readiness.md
Governance
- Quality Metrics
docs/Quality-Metrics.md - Risk Ownership
docs/Release-Readiness.md
Other components
- Product / Business
- Release Decision
- Production Feedback
Connections 17
- Product / Business → Risk Assessment: sets impact
- Risk Assessment → Test Strategy: guides depth
- Test Strategy → Automation Decision: evaluates candidates
- Test Strategy → Manual Exploration: allows exploration
- Test Strategy → Test Layers: selects layer
- Test Layers → Framework Architecture: informs design
- Test Layers → Reference Examples: illustrated by
- Test Layers → Advanced Testing: covers NFRs
- Automation Decision → CI/CD Gates: informs pipeline
- Test Layers → CI/CD Gates: supplies evidence
- Advanced Testing → CI/CD Gates: adds signals
- CI/CD Gates → Release Readiness: provides evidence
- Release Readiness → Release Decision: recommends
- Risk Ownership → Release Decision: shares ownership
- Production Feedback → Quality Metrics: provides signals
- Quality Metrics → Risk Assessment: informs reassessment
- Release Readiness → Quality Metrics: tracks residual risk