How to run tests?

[pgarrison]

I am trying to run the tests for duckdb-wasm. My goal is to run the new tests from this PR, but for now I'm running tests from main.

I'm on macOS with Chrome and Firefox installed.

I'm using the following steps.

cd packages/duckdb-wasm
npm i -d
npm test

I get the following error.

npm test     

> @duckdb/[email protected] test
> npm run test:chrome && npm run test:node


> @duckdb/[email protected] test:chrome
> karma start ./karma/tests-chrome.cjs

CHROME_BIN=/Users/philip.garrison/.cache/puppeteer/chrome/mac_arm-124.0.6367.91/chrome-mac-arm64/Google Chrome for Testing.app/Contents/MacOS/Google Chrome for Testing
04 12 2025 15:31:30.253:INFO [preprocessor.coverage]: coverage not included in reporters [ 'spec' ]
04 12 2025 15:31:30.256:INFO [S3-test-server]: Starting S3 test server on port 4923
04 12 2025 15:31:30.271:WARN [filelist]: Pattern "/Users/philip.garrison/workspace/aics/duckdb-wasm/packages/duckdb-wasm/dist/tests-browser.js" does not match any file.
04 12 2025 15:31:30.271:WARN [filelist]: Pattern "/Users/philip.garrison/workspace/aics/duckdb-wasm/packages/duckdb-wasm/dist/*.js" does not match any file.
04 12 2025 15:31:30.271:WARN [filelist]: Pattern "/Users/philip.garrison/workspace/aics/duckdb-wasm/packages/duckdb-wasm/dist/*.js.map" does not match any file.
04 12 2025 15:31:30.271:WARN [filelist]: Pattern "/Users/philip.garrison/workspace/aics/duckdb-wasm/data/tpch/0*/duckdb/db" does not match any file.
04 12 2025 15:31:30.271:WARN [filelist]: Pattern "/Users/philip.garrison/workspace/aics/duckdb-wasm/data/tpch/0*/parquet/*.parquet" does not match any file.
04 12 2025 15:31:30.271:WARN [filelist]: Pattern "/Users/philip.garrison/workspace/aics/duckdb-wasm/data/uni/*.parquet" does not match any file.
04 12 2025 15:31:30.307:INFO [karma-server]: Karma v6.4.2 server started at http://localhost:9876/
04 12 2025 15:31:30.307:INFO [launcher]: Launching browsers ChromeHeadlessNoSandbox with concurrency 1
04 12 2025 15:31:30.312:INFO [launcher]: Starting browser ChromeHeadless
04 12 2025 15:31:30.882:INFO [Chrome Headless 124.0.6367.91 (Mac OS 10.15.7)]: Connected on socket lBc7ZZ-6AaN23Lz_AAAB with id 62147556

Chrome Headless 124.0.6367.91 (Mac OS 10.15.7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
12/4/2025, 3:31:30 PM - TOTAL: 0 SUCCESS

npm error Lifecycle script `test:chrome` failed with error:
npm error code 1
npm error path /Users/philip.garrison/workspace/aics/duckdb-wasm/packages/duckdb-wasm
npm error workspace @duckdb/[email protected]
npm error location /Users/philip.garrison/workspace/aics/duckdb-wasm/packages/duckdb-wasm
npm error command failed
npm error command sh -c karma start ./karma/tests-chrome.cjs
npm error Lifecycle script `test` failed with error:
npm error code 1
npm error path /Users/philip.garrison/workspace/aics/duckdb-wasm/packages/duckdb-wasm
npm error workspace @duckdb/[email protected]
npm error location /Users/philip.garrison/workspace/aics/duckdb-wasm/packages/duckdb-wasm
npm error command failed
npm error command sh -c npm run test:chrome && npm run test:node

[anntnzrb]

From the repository root, run make js_debug build/data to build the library and generate test data, then run make js_tests_browser for Chrome tests or make js_tests for both browser and node tests. The error occurs because running npm test directly from packages/duckdb-wasm skips the required compilation step.