Results of 1 - 10 of about 16 for tests (0.002 sec.)
- Debugging 12441
- The purpose of the tests is to figure out when things break. Inevitably changes made to the system will cause one of the tests to fail, and when that happens the test needs to be debugged. First, it is always recommended to run in debug mod
..., it is recommended to only run the test that breaks. This can be done by passing the filename of the breaking test to the test suite as a command line parameter (e.g., build/debug/test/unittest test/sql/projection/test_simple_projection.test ). For m...ore options on running a subset of the tests see the Triggering which tests to run section. After that, a debugger can be attached to the program and the test can be d...ebugged. In the sqllogictests it is normally difficult to break on a specific query, however, we have expanded the test suite so that a function called... - https://man.mtool.work/duckdb/2.0/dev/sqllogictest/debugging.html
- Unit Tester Configuration 11731
- There are three ways of setting options for the unit tester: Command Line Arguments Configuration File Environment Variables Configuration Options List See the Configuration Options List for the full list of available options. Command Line
...ns can also be used in the configuration file: Option Description extends List of config files to extend from inherit_skip_tests Path of config to inherit skip_tests from skip_tests Tests to be skipped Example: { "extends": ["base_config.json"], "inhe...rit_skip_tests": "test/configs/force_storage.json", "skip_tests": [ { "reason": "Contains explicit use of the memory catalog.", "paths":...Max threads to be used by the test runner itself (for e.g. concurrent loop) --max-threads <num> Max threads to use during tests --on-cleanup <string> SQL statements to execute on test end --on-init <string> SQL statements to execute on init --on-load... - https://man.mtool.work/duckdb/2.0/dev/sqllogictest/test_configuration.html
- Writing Tests 11090
- Development and Testing It is crucial that any new features that get added have correct tests that not only test the “happy path”, but also test edge cases and incorrect usage of the feature. In this section, we describe how DuckDB tests ar
...e structured and how to make new tests for DuckDB. The tests can be run by running the unittest program located in the test folder. For the default compilations...ease/test/unittest (release) or build/debug/test/unittest (debug). Philosophy When testing DuckDB, we aim to route all the tests through SQL. We try to avoid testing components individually because that makes those components more difficult to change...later on. As such, almost all of our tests can (and should) be expressed in pure SQL. There are certain exceptions to this, which we will discuss in Catch Tests . Ho... - https://man.mtool.work/duckdb/2.0/dev/sqllogictest/writing_tests.html
- sqllogictest Introduction 10466
- For testing plain SQL, we use an extended version of the SQL logic test suite, adopted from SQLite . Every test is a single self-contained file located in the test/sql directory. To run tests located outside of the default test directory, s
...he above test, we would run the command unittest test/sql/projection/test_simple_projection.test . If we wanted to run all tests in a specific directory, we would run the command unittest "[projection]" . Any tests that are placed in the test director...y are automatically added to the test suite. Note that the extension of the test is significant. The sqllogictests should either use the .test extension, or the....test_slow extension. The .test_slow extension indicates that the test takes a while to run, and will only be run when all tests are explicitly run using unittest * . Tests with the extension .test will be included in the fast set of tests. Query Veri... - https://man.mtool.work/duckdb/2.0/dev/sqllogictest/intro.html
- Python 8785
- The DuckDB Python package has its own repository at duckdb/duckdb-python and uses nanobind 3 to create Python bindings with DuckDB. Prerequisites This guide assumes: You have a full clone of the DuckDB Python package source, including its g
...rify Installation uv run python -c "import duckdb; print(duckdb.sql('SELECT 42').fetchall())" Development Workflow Running Tests Run all tests: uv run --no-build-isolation pytest ./tests --verbose Run fast tests only (excludes slow directory): uv run...--no-build-isolation pytest ./tests --verbose --ignore=./tests/slow Test Coverage Build with coverage (compiles the extension with --coverage into build/cover...age/ for C++ coverage), then run the tests under coverage: COVERAGE=1 uv sync --no-build-isolation -v --reinstall -p 3.13 COVERAGE=1 uv run --no-build-isolation cove... - https://man.mtool.work/duckdb/2.0/dev/building/python.html
- Overview 8491
- The pages in this section are intended for developers who contribute to DuckDB or build extensions for it. If you would like to contribute, please also read the contributing guidelines . Project Structure and Processes DuckDB Repositories l
...n overview of how DuckDB is tested. sqllogictest Introduction introduces the sqllogictest format used for most of DuckDB's tests. Writing Tests describes how to write new tests. Internal Errors explains what internal errors are and how to debug them.... - https://man.mtool.work/duckdb/2.0/dev/overview.html
- Persistent Testing 8491
- By default, all tests are run in in-memory mode (unless --force-storage is enabled). In certain cases, we want to force the usage of a persistent database. We can initiate a persistent database using the load command, and trigger a reload o
..., (14), (15), (NULL) # ... restart query I SELECT * FROM test ORDER BY a ---- NULL 11 12 13 14 15 Note that by default the tests run with SET wal_autocheckpoint = '0KB' – meaning a checkpoint is triggered after every statement. WAL tests typically run... - https://man.mtool.work/duckdb/2.0/dev/sqllogictest/persistent_testing.html
- Catch C/C++ Tests 8404
- While we prefer the sqllogic tests for testing most functionality, for certain tests only SQL is not sufficient. This typically happens when you want to test the C++ API. When using pure SQL is really not an option it might be necessary to
...make a C++ test using Catch. Catch tests reside in the test directory as well. Here is an example of a catch test that tests the storage of the system: #include "c...atch.hpp" #include "test_helpers.hpp" TEST_CASE("Test simple storage", "[storage]") { auto config = GetTestConfig(); unique_ptr<QueryResult> result; auto storage_database = Test... - https://man.mtool.work/duckdb/2.0/dev/sqllogictest/catch.html
- Overview 8109
- How is DuckDB Tested? Testing is vital to make sure that DuckDB works properly and keeps working properly. For that reason, we put a large emphasis on thorough and frequent testing: * We run a batch of small tests on every commit using GitH
...ub Actions , and run a more exhaustive batch of tests on pull requests and commits in the main branch. * We use a fuzzer , which automatically reports issues found through fuzz... - https://man.mtool.work/duckdb/2.0/dev/sqllogictest/overview.html
- Loops 7485
- Loops can be used in sqllogictests when it is required to execute the same query many times but with slight modifications in constant values. For example, suppose we want to fire off 100 queries that check for the presence of the values 0..
...preset combinations that should be used when required. In this manner, when new combinations are added to the preset, old tests will automatically pick up these new combinations. Preset Expansion ⟨compression⟩ none uncompressed rle bitpacking diction...ic⟩ bool interval varchar json Use large loops sparingly. Executing hundreds of thousands of SQL statements will slow down tests unnecessarily. Do not use loops for inserting data. Data Generation without Loops Loops should be used sparingly. While it... - https://man.mtool.work/duckdb/2.0/dev/sqllogictest/loops.html
DuckDB 2.0 Documentation / man.mtool.work