1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
|
This is the SQL and C++ DuckDB Unittests
## Test Contract
Within SQL tests, the test runner (unittest) guarantees that these environment variables will be set. Many can be overridden when needed.
| Env Var | Default Value | Overrides | Notes |
|------------------|----------------------------|-------------------------------------------------------------|---------------------------------------------------|
| `TEST_NAME` | e.g. `test/path/filename.test` | N/A | |
| `TEST_NAME_NO_SLASH` | e.g. `test_path_filename.test` | N/A | is always `TEST_NAME s@/@_@g`|
| `TEST_UUID` | random UUID (as string) | N/A | defined per invocation |
| `WORKING_DIR` | e.g., `/Users/me/src/duckdb` | `unittest --test-dir <path>` | default: wherever duckdb was sourced and built <br/> AKA: `__WORKING_DIRECTORY__` |
| `BUILD_DIR` | `{WORKING_DIR}/build/release` | N/A | read-only; derived from unittest path <br/> AKA: `__BUILD_DIRECTORY__` |
| `DATA_DIR` | `{WORKING_DIR}/data` | `DATA_DIR=mydata unittest ...`<br/>also test configs, `test_env` specification | Should provide a copy of `duckdb/data/**`, use to test AWS, Azure, other VFS reads |
| `TEMP_BASE` | `{WORKING_DIR}/duckdb_unittest_tempdir` | via `unittest --test-temp-dir` (retains dir after test) | use to test VFS writes <br/> AKA: `__TEST_DIR__` |
| `TEMP_DIR` | `{TEMP_BASE}/<process-id>` | via `unittest --test-temp-dir` (retains dir after test) | use to test VFS writes <br/> AKA: `__TEST_DIR__` |
Some tests require a particular environment variables to be set so they can properly run, usually this can be seen via `require-env VAR` in the test.
### Parallel CSV Reader
The tests located in `test/parallel_csv/test_parallel_csv.cpp` run the parallel CSV reader over multiple configurations of threads
and buffer sizes.
### ADBC
The ADBC tests are in `test/api/adbc/test_adbc.cpp`. To run them the DuckDB library path must be provided in the `DUCKDB_INSTALL_LIB` variable.
|
