Uses of Package
io.karatelabs.core
Packages that use io.karatelabs.core
Package
Description
-
Classes in io.karatelabs.core used by com.intuit.karate
-
Classes in io.karatelabs.core used by com.intuit.karate.coreClassDescriptionPublic API for creating mock servers from feature files.Builder for creating MockServer instances.
-
Classes in io.karatelabs.core used by io.karatelabs.coreClassDescriptionBacking object for the
bootglobal exposed insidekarate-boot.js.Represents an async channel (e.g. kafka, grpc) created by aChannelFactory.Factory for creatingChannelinstances.Error event (ERROR).Karate ext SPI — singletons-per-Suite that observe the run viaRunListener.Mints a per-scenario ext-global instance, bound fresh into each scenario's JS scope.Feature-level events (FEATURE_ENTER, FEATURE_EXIT).HTTP-level events (HTTP_ENTER, HTTP_EXIT).Holds runtime configuration settings set via the 'configure' keyword.The exception surfaced to callers (JUnit / surefire, the fluentRunnerAPI, any code that catches a Karate failure) when a step fails.Main implementation of the karate.* JavaScript API.Minimal context interface for KarateJs to access runtime information.Represents Karate project configuration loaded from karate-pom.json.Logging configuration nested object.Output configuration nested object.Assertion-level events (MATCH_EXIT).Configuration holder for mock servers.Mock server request handler that routes requests to matching scenarios.Public API for creating mock servers from feature files.Builder for creating MockServer instances.Scenario-outline-level event (OUTLINE_ENTER).Interface for capturing custom performance events from Java code.Represents a performance event for Gatling integration.Hook interface for performance testing integration (e.g., Gatling).Progress event (PROGRESS).Imperative spec for one ext's report-asset contribution, built fluently insideExt.onBoot(Suite)and handed toSuite.registerReportAssets(ReportAssets, ClassLoader)(see EXT.md § Report assets).One nav-page (or other slot) contribution.Base interface for runtime events fired during test execution.Event types for the unified runtime event system.Unified listener interface for runtime events.Factory for creating per-thread RunListener instances.Manages locks for parallel scenario execution.Handle for releasing acquired locks.Scenario-level events (SCENARIO_ENTER, SCENARIO_EXIT).SSL/TLS configuration for both client and server contexts.A named report embed, generalised to one-or-moreStepResult.Parts plus optionalmeta(see EXT.md § Embeds).One asset within anStepResult.Embed: either inlinedata(core writes the file and setsfileName) or a report-relativeurl(the ext wrote the asset itself, e.g. underext/image/assets/).Step-level events (STEP_ENTER, STEP_EXIT).The callable target and (optional) argument expression of a call step, e.g.Parsed result of a feature path with optional tag selector or line filter.Immutable suite configuration and execution engine.Suite-level events (SUITE_ENTER, SUITE_EXIT).Values helper class for valuesFor('@tag') functionality. -
Classes in io.karatelabs.core used by io.karatelabs.driver
-
Classes in io.karatelabs.core used by io.karatelabs.httpClassDescriptionHolds runtime configuration settings set via the 'configure' keyword.
-
Classes in io.karatelabs.core used by io.karatelabs.outputClassDescriptionImperative spec for one ext's report-asset contribution, built fluently inside
Ext.onBoot(Suite)and handed toSuite.registerReportAssets(ReportAssets, ClassLoader)(see EXT.md § Report assets).A named report embed, generalised to one-or-moreStepResult.Parts plus optionalmeta(see EXT.md § Embeds).Immutable suite configuration and execution engine.