The store type to test, defaults to StoreClient
Optional ReadonlytargetExecute only the sub-suites or tests whose path contains any of the given patterns.
Patterns are matched as substrings against the full test path, formed by joining the well-known sub-suite tag
(PersistUpdate, RetrieveTemplate, …) with the inner describe/it names using > as separator, for
example PersistUpdate > update > contract > should return the resource id for an existing resource.
Well-known sub-suite tags are listed inline as autocomplete hints; arbitrary patterns are accepted via the
(string & {}) branch and may target individual describe blocks or test names. When omitted (or empty), every
sub-suite and test runs unless ignored.
Optional ReadonlyignoreIgnore sub-suites or tests whose path contains any of the given patterns.
Same matching semantics as target. An ignore match always wins: a path matched by both target and
ignore is skipped.
ReadonlyopenOptional ReadonlycloseCloses the store instance after all tests complete.
ReadonlycontainsChecks whether the store contains a resource with the given identifier.
Returns true if the resource has any stored data at all; false otherwise. Unlike includes, this performs an identity-only check without verifying specific property values.
The resource identifier to check
ReadonlyincludesChecks whether every fact described by a resource is present in the store.
Returns true if every fact described by entry (scalar values, references, nested structures) is present;
false otherwise. Mutation tests rely on it to verify persisted content without depending on
StoreClient.lookup.
Accepts partial resources: only the slots explicitly set on entry contribute facts, and omitted slots are not
checked. Full validated states behave as whole-state equality checks; narrower probes assert a targeted subset
of facts.
The resource shape the probe and its facts conform to
A resource (possibly partial) whose specified facts must all be present
The resource shape describing the resource structure
ReadonlyexcludesChecks whether every fact described by a resource is absent from the store.
Returns true if none of the facts described by entry (scalar values, references, nested structures) are
present; false if any fact is still present. Mirror of includes: where
includes asserts all-present, excludes asserts all-absent.
Accepts partial resources under the same semantics as includes: only explicitly-set slots contribute facts. Probes narrow to the exact slots whose facts are expected to be gone, since a fuller state would also cover facts the operation under test leaves in place.
The resource shape the probe and its facts conform to
A resource (typically partial) whose specified facts must all be absent
The resource shape describing the resource structure
ReadonlypopulatePopulates the store with the sample dataset.
Must clear all existing data and perform a full reload: any resources created, updated, or deleted by previous tests must be removed so that only the original sample data is present.
Called by the retrieval sub-suites before their tests run, so each of them reads the pristine sample dataset.
ReadonlygenerateGenerates an isolated copy of a sample resource with a unique identifier and inserts it into the store.
Mutation tests rely on it to create isolated resources that do not conflict with the sample dataset or other tests. The clone helper mints a suitable copy.
The sample resource to use as template, typically drawn from the sample dataset
The resource shape describing the resource structure
The inserted copy with a unique id
Options for running a store conformance suite.