Package com.shaft.capture.generate.api

package com.shaft.capture.generate.api

Related Packages

Package	Description
com.shaft.capture.generate
com.shaft.capture.generate.api.internal

Class	Description
ApiCaptureGenerationRequest	Options for generating a SHAFT.API test class from a recorded session.
ApiCaptureGenerationResult	Artifacts and report produced by ApiCaptureGenerator.
ApiCaptureGenerator	Generates, optionally compiles, and optionally replays a SHAFT.API TestNG class from a recorded session's API transactions.
ApiCaptureGenerator.TransactionLeaves	One transaction's classified response leaves, for a "pin this path" picker UI.
ApiCodegenStyle	How recorded transactions are grouped into generated test methods.
ApiTestRenderer	Renders a compiling SHAFT.API TestNG class from recorded, classified, and correlated API transactions.
ApiTransaction	One recorded API transaction with resolved (not just referenced) request/response body text, ready for classification, correlation, and rendering.
ApiValidationDepth	How thoroughly generated code validates each response.
CorrelatedTransaction	One transaction's response leaves after TransactionCorrelator has run, with any VOLATILE leaf found reused by a later request upgraded to LeafClassification.CORRELATED.
CorrelationUse	One place a correlated (previously VOLATILE) response value was found reused by a later transaction's outbound request.
CorrelationUse.Location	Where a correlated value was found reused in a later request.
JsonSchemaInferencer	Infers a standard (draft-04-compatible) JSON Schema document from one recorded sample response body, for use with SHAFT.API's assertThatResponse().matchesSchema(path), which is backed by REST-Assured's io.restassured.module.jsv.JsonSchemaValidator.
LeafClassification	Classification of one scalar JSON leaf discovered in a recorded API response body.
RenderedApiTest	Result of rendering one API test class.
ResponseLeaf	One classified scalar leaf discovered while walking a recorded JSON response body.
ResponseNormalizer	Classifies each scalar leaf of a recorded JSON response body as LeafClassification.STABLE, LeafClassification.VOLATILE, or LeafClassification.SENSITIVE, reusing the exact same key/value volatility and sensitivity detection HttpContractRecorder uses for HTTP contract normalization, so API codegen and contract capture agree on what counts as noise vs. a stable, assertable value.
TransactionCorrelator	Finds VOLATILE response leaves that a later transaction's request reuses (the common create -> read/update case: a generated ID from a POST response reappears in a later GET's URL, or a later PATCH's request body), and upgrades them to LeafClassification.CORRELATED so codegen chains them through a variable (e.g.