Summary
sdks/js/browser-sdk/test/Opfs.test.ts currently wraps the entire OPFS suite in describe.skip("Opfs", ...), so none of the tests for Opfs run.
The skipped coverage includes:
listFiles() / fileCount()poolCapacity()fileExists()deleteFile()exportDb() / importDb()clearAll()
Impact
Opfs is exported by the browser SDK and manages the SDK's OPFS-backed SQLite files, but its main behavior is not currently covered by CI. Regressions in import/export/delete/cleanup behavior can slip through unnoticed.
Expected behavior
The OPFS tests should either run in an environment that supports OPFS, or be conditionally skipped with an explicit feature/environment guard instead of skipping the whole suite unconditionally.
Possible fix
Move the suite to a browser-capable test environment, or replace the unconditional describe.skip with a feature-detected describe.skipIf(...)/equivalent so the tests run wherever OPFS is available.
Summary
sdks/js/browser-sdk/test/Opfs.test.tscurrently wraps the entire OPFS suite indescribe.skip("Opfs", ...), so none of the tests forOpfsrun.The skipped coverage includes:
listFiles()/fileCount()poolCapacity()fileExists()deleteFile()exportDb()/importDb()clearAll()Impact
Opfsis exported by the browser SDK and manages the SDK's OPFS-backed SQLite files, but its main behavior is not currently covered by CI. Regressions in import/export/delete/cleanup behavior can slip through unnoticed.Expected behavior
The OPFS tests should either run in an environment that supports OPFS, or be conditionally skipped with an explicit feature/environment guard instead of skipping the whole suite unconditionally.
Possible fix
Move the suite to a browser-capable test environment, or replace the unconditional
describe.skipwith a feature-detecteddescribe.skipIf(...)/equivalent so the tests run wherever OPFS is available.