Surfaced while running the EXPath File 4.0 QT4 suite against PR #6257 (174/190 passing). Two tests fail with what look like test-infrastructure issues rather than function bugs.
Failing tests
- `EXPath-file-exists-002` — `file:exists("../sandpit")` returns `false`. The sandpit IS the parent's sibling, so this should be `true`. Likely the current-working-directory isn't being scoped to inside `sandpit/` as the test environment expects.
- `EXPath-file-pathToNative-002` — Throws `exfile:not-found` for `/test.txt` because the file was supposed to be created by a prior test in shared sandpit state. In isolation `pathToNative-005` passes, suggesting test ordering / shared-state setup.
Diagnostic
These look like sandpit-isolation issues that affect both implementations and test fixtures. Worth checking against EXPath File 4.0 spec §3 (test sandbox conventions) and against how other implementations sandbox their EXPath File QT4 runs.
Possibly related: eXist-db/exist-xqts-runner#47 ("Sandpit directory structure doesn't support relative parent paths").
Disposition
Doesn't block PR #6257 from landing. Follow-up — may turn out to be a runner-side or qt4specs fixture issue rather than an eXist bug.
Surfaced while running the EXPath File 4.0 QT4 suite against PR #6257 (174/190 passing). Two tests fail with what look like test-infrastructure issues rather than function bugs.
Failing tests
Diagnostic
These look like sandpit-isolation issues that affect both implementations and test fixtures. Worth checking against EXPath File 4.0 spec §3 (test sandbox conventions) and against how other implementations sandbox their EXPath File QT4 runs.
Possibly related: eXist-db/exist-xqts-runner#47 ("Sandpit directory structure doesn't support relative parent paths").
Disposition
Doesn't block PR #6257 from landing. Follow-up — may turn out to be a runner-side or qt4specs fixture issue rather than an eXist bug.