Results of 1 - 5 of about 5 for sqllogictest (0.001 sec.)
- Overview 12575
- 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
...types and options. Troubleshooting covers common build issues. Testing Testing gives an 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... - https://man.mtool.work/duckdb/2.0/dev/overview.html
- sqllogictest Introduction 9670
- 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
...d in the test directory 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 take...ion for all unit tests, except those involving larger datasets (more than ~10-100 rows). Editors & Syntax Highlighting The sqllogictests are not exactly an industry standard, but several other systems have adopted them as well. Parsing sqllogictests is inten...ult. A syntax highlighter exists for Visual Studio Code . We have also made a fork that supports the DuckDB dialect of the sqllogictests . You can use the fork by installing the original, then copying the syntaxes/sqllogictest.tmLanguage.json into the instal... - https://man.mtool.work/duckdb/2.0/dev/sqllogictest/intro.html
- Writing Tests 8107
- 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
...Tests . However, in most cases you should write your tests in plain SQL. Frameworks SQL tests should be written using the sqllogictest framework . C++ tests can be written using the Catch framework . Client Connector Tests DuckDB also has tests for various... - https://man.mtool.work/duckdb/2.0/dev/sqllogictest/writing_tests.html
- Result Verification 7887
- The standard way of verifying results of queries is using the query statement, followed by the letter I times the number of columns that are expected in the result. After the query, four dashes ( ---- ) are expected followed by the result v
...cy reasons the letters R and T are also accepted to denote columns. Deprecated DuckDB deprecated the usage of types in the sqllogictest. The DuckDB test runner does not use or need them internally – therefore, only I should be used to denote columns. NULL Va...lues and Empty Strings Empty lines have special significance for the SQLLogic test runner: they signify an end of the current statement or query. For that reason, empty strings and NULL values have specia...LECT 42, 84 UNION ALL SELECT 10, 20; ---- 42 84 10 20 Hashes and Outputting Values Besides direct result verification, the sqllogic test suite also has the option of using MD5 hashes for value comparisons. A test using hashes for result verification looks li... - https://man.mtool.work/duckdb/2.0/dev/sqllogictest/result_verification.html
- Unit Tester Configuration 7666
- 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
...ed-extensions <comma-separated strings> Extensions to be loaded (from the statically available ones) --stdin Read a single sqllogictest script from stdin --storage-fuzzer , --no-storage-fuzzer Run storage fuzzer tests --storage-version <string> Database stor... - https://man.mtool.work/duckdb/2.0/dev/sqllogictest/test_configuration.html
PREV
1
NEXT
DuckDB 2.0 Documentation / man.mtool.work