slug: keploy
provider: Keploy
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Software & Technology
min_confidence: 0.7
capability_model:
  source: https://github.com/vincentmakes/turbo-ea-capabilities
  license: CC-BY-4.0
  attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities,
    CC BY 4.0
  notice: NOTICE
edge_count: 6
edges:
- tag: Test Suites
  spec_file: keploy-test-suites-api-openapi.yml
  capability_id: BC-4200.50
  capability_id_l1: BC-4200
  capability_name: Software Quality Engineering
  confidence: 0.93
  evidence: POST /apps/{appId}/test-suites/generate  generateTestSuites  Generate test suites via AI;
    POST /apps/{appId}/test-suites/run  runTestSuites  Run test suites
  reason: Full CRUD, AI generation, validation and execution of test suites — unambiguously automated
    test suite stewardship under Software Quality Engineering.
- tag: Test Reports
  spec_file: keploy-test-reports-api-openapi.yml
  capability_id: BC-4200.50
  capability_id_l1: BC-4200
  capability_name: Software Quality Engineering
  confidence: 0.9
  evidence: GET /apps/{appId}/test-reports/{reportId}  getTestReport  Get a test run report; schemas TestCoverage,
    OssFailureInfo, MockMismatchInfo
  reason: Read-only reporting over test run/test set/test case results including coverage and failure
    detail — clearly test result reporting under Software Quality Engineering.
- tag: Test Runs
  spec_file: keploy-test-runs-api-openapi.yml
  capability_id: BC-4200.50
  capability_id_l1: BC-4200
  capability_name: Software Quality Engineering
  confidence: 0.88
  evidence: GET /apps/{appId}/test-runs  listTestRuns  List test runs; POST /apps/{appId}/test-runs/{runId}/normalize  Normalize
    a test run
  reason: Lifecycle and normalisation of automated test runs and their suite reports — execution management
    of the automated test suite, i.e. software quality engineering.
- tag: Recordings
  spec_file: keploy-recordings-api-openapi.yml
  capability_id: BC-4200.50
  capability_id_l1: BC-4200
  capability_name: Software Quality Engineering
  confidence: 0.85
  evidence: GET /apps/{appId}/recordings/{testSetId}  getRecording  Get recorded test cases; POST /apps/{appId}/recordings/{testSetId}/mocks  createMock
  reason: Recordings here are captured traffic turned into test cases and auto-generated mocks, with test-set/mock
    mapping management — stewardship of an automated test suite, i.e. software quality engineering, not
    media or call recording.
- tag: SmartSet
  spec_file: keploy-smartset-api-openapi.yml
  capability_id: BC-4200.50
  capability_id_l1: BC-4200
  capability_name: Software Quality Engineering
  confidence: 0.85
  evidence: GET /apps/{appId}/smart-set/cases  listSmartTestCases  List smart test cases; POST /apps/{appId}/smart-set/cases/{name}/obsolete  Mark
    a smart test case obsolete
  reason: Operations curate smart test cases and their mocks (edit, delete, mark obsolete, upsert mock)
    — automated test suite stewardship within software quality engineering.
- tag: API Keys
  spec_file: keploy-api-keys-api-openapi.yml
  capability_id: BC-4270.40
  capability_id_l1: BC-4270
  capability_name: Developer Identity & Credential Management
  confidence: 0.72
  evidence: '"Create an API key", "Revoke an API key", schema PublicAPIKey; "Every endpoint requires a
    minimum scope (`read`, `write`, or `admin`)"'
  reason: Issuance, listing and revocation of scoped API credentials for programmatic/CI consumers is
    developer credential management on the vendor's public API. It is also arguably plain access-control
    plumbing, so confidence is moderate.