LangChain Reference home pageLangChain ReferenceLangChain Reference
  • GitHub
  • Main Docs
Deep Agents
LangChain
LangGraph
Integrations
LangSmith
LangGraph
  • Web
  • Channels
  • Pregel
  • Prebuilt
  • Remote
  • Stream
LangGraph SDK
  • Ui
  • Client
  • Auth
  • React
  • Logging
  • React Ui
  • Utils
  • Server
  • Stream
LangGraph Checkpoint
LangGraph Checkpoint MongoDB
LangGraph Checkpoint Postgres
  • Store
LangGraph Checkpoint Redis
  • Shallow
  • Store
LangGraph Checkpoint SQLite
LangGraph Checkpoint Validation
  • Cli
LangGraph API
LangGraph CLI
LangGraph CUA
  • Utils
LangGraph Supervisor
LangGraph Swarm
⌘I

LangChain Assistant

Ask a question to get started

Enter to send•Shift+Enter new line

Menu

LangGraph
WebChannelsPregelPrebuiltRemoteStream
LangGraph SDK
UiClientAuthReactLoggingReact UiUtilsServerStream
LangGraph Checkpoint
LangGraph Checkpoint MongoDB
LangGraph Checkpoint Postgres
Store
LangGraph Checkpoint Redis
ShallowStore
LangGraph Checkpoint SQLite
LangGraph Checkpoint Validation
Cli
LangGraph API
LangGraph CLI
LangGraph CUA
Utils
LangGraph Supervisor
LangGraph Swarm
Language
Theme
JavaScript@langchain/langgraph-checkpoint-validationindexdeltaChannelHistoryTests
Function

deltaChannelHistoryTests

Copy
deltaChannelHistoryTests<T extends BaseCheckpointSaver<number>>(
  initializer: CheckpointSaverTestInitializer<T>
)
View source on GitHub

Parameters

NameTypeDescription
initializer*CheckpointSaverTestInitializer<T>

Conformance tests for BaseCheckpointSaver.getDeltaChannelHistory — the walk that reconstructs DeltaChannel state from checkpoint_writes.

This is the one checkpointer method with no coverage in the default spec suite, and it is intentionally opt-in: it is not run by specTest, so adding it does not raise the conformance bar for third-party savers (the method is Beta and inherits a default implementation from BaseCheckpointSaver). Each in-repo saver's .spec.ts calls it explicitly so the shared base walk is validated against every backend's real storage — Postgres, SQLite, Redis, MongoDB, and the MemorySaver override.

The scenarios target the per-backend behaviours the walk depends on: round-tripping DeltaSnapshot and plain-array seed blobs, following parentConfig up the ancestor chain, and — critically — replaying concurrent same-superstep writes in the canonical (task_id, idx) order regardless of how a given store happens to return pendingWrites (insertion order, locale collation, etc.).