Results of 1 - 4 of about 4 for unittest (0.001 sec.)
- Debugging 12426
- 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
...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 more options on running a subset of the tests see the Triggering wh...mode unskip . Any queries between the two statements will not be executed. Triggering Which Tests to Run When running the unittest program, by default all the fast tests are run. A specific test can be run by adding the name of the test as an argument....For the sqllogictests, this is the relative path to the test file. To run only a single test: build/debug/test/unittest test/sql/projection/test_simple_projection.test All tests in a given directory can be executed by providing the directory... - https://man.mtool.work/duckdb/2.0/dev/sqllogictest/debugging.html
- sqllogictest Introduction 8488
- 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
...that the file is in. The name and group of the test are relevant because they can be used to execute only that test in the unittest group. For example, if we wanted to execute only the above test, we would run the command unittest test/sql/projection/tes...t_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 directory are automatically added to the test suite. Note that the..._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 Verification Many simple tests start b... - https://man.mtool.work/duckdb/2.0/dev/sqllogictest/intro.html
- Unit Tester Configuration 8118
- 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
...Arguments See the Configuration Options List for all available options. # booleans unittest --checkpoint-on-shutdown unittest --no-checkpoint-on-shutdown # other types unittest --checkpoint-wal-size 100000 Command...onment variables, prefixed with DUCKDB_TEST_ , upper-cased with underscores: Example: DUCKDB_TEST_CHECKPOINT_ON_SHUTDOWN=1 unittest Configuration Options List The following configuration options are available: Option Description --autoloading <none|avail... - https://man.mtool.work/duckdb/2.0/dev/sqllogictest/test_configuration.html
- Writing Tests 7933
- 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 this is located in either build/release/test/unittest (re...lease) 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 ind... - https://man.mtool.work/duckdb/2.0/dev/sqllogictest/writing_tests.html
PREV
1
NEXT
DuckDB 2.0 Documentation / man.mtool.work