Indexing of newly uploaded resources is asynchronous; the search step
slept a fixed 10s and searched once, so under load a just-uploaded file
was missing from the result and the following assertion failed. The
search step now remembers its query, and new eventually-contain steps
re-run the search until the expected entries are present (or the
WaitHelper timeout elapses), then assert as before. contentSearch
scenarios use them for their positive assertions; the exact-count check
runs after the expected entries have appeared.
Property extraction reaches the driveItem asynchronously, so the GET
step previously waited only until any extraction facet key appeared and
a separate step then validated the full schema, which could run on a
partial payload and fail intermittently. The GET and the status check
stay plain steps; a new explicit Then step re-fetches the item until
the response satisfies the expected schema (a partial never matches) or
the WaitHelper timeout elapses.
both engines now agree on names, titles, tags, paths, types, sizes, dates,
hidden flags, facet values and wildcards. quotes only delimit phrases and
the equals operator matches the whole field value, following the kql spec.
the index name carries a generation so a changed mapping starts on a fresh
index, MIGRATION.md says how to fill it.
* separate When steps using root and permissions endpoints
test: separate resource sharing GIven step from space share
test: share space via root endpoint in Given steps
test: use existing step
test: fix more steps
* test: separate resource and space link share creation
test: fix php code style
* split large API test suites
* remove 30s sleep
* organize core-api test suites
* organize core-api test suites
* divide into 9 pipelines
* organize core-api test suites
* organize api-search suites
* organize api-search suites
* fix config file
Dominik Schmidt