Package io.karatelabs.core
package io.karatelabs.core
-
ClassDescriptionBacking object for the
bootglobal exposed insidekarate-boot.js.Discoverskarate-boot.js(workdir root, then classpath root) and evaluates it once per Suite.Represents an async channel (e.g. kafka, grpc) created by aChannelFactory.Factory for creatingChannelinstances.Config-only evaluation: evaluate a project'skarate-base.js+karate-config.js(+ the env-specifickarate-config-<env>.js) for a working dir and return the merged configMapwithout running any features (noSUITE_ENTER/SUITE_EXIT, no scenarios).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.Turns a bareReferenceError: X is not definedinside a step into an actionable failure — whenXis a global that an ext would have bound, had the project declared it.Faker API for generating random test data.Wrapper for a Feature with an optional tag selector.Feature-level events (FEATURE_ENTER, FEATURE_EXIT).Global constants and utilities for Karate runtime.HTTP-level events (HTTP_ENTER, HTTP_EXIT).ARunListenerthat streams events to a JSON Lines (.jsonl) file.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.Stateless utility methods for the karate.* JavaScript API.Applies system-property and environment-variable overrides to aRunner.Builderat the start ofparallel().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.Main entry point for running Karate tests programmatically.Shared helpers for run-event JSON shaping — cross-run-stable slug computation and tag-text extraction.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.Factory for creating SSLContext instances from SslConfig.SSL utilities for creating SSL contexts and self-signed certificates.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).Static utility methods for step execution.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).Advanced tag selector supporting V1-compatible expressions.Values helper class for valuesFor('@tag') functionality.