eb50cee601
* feat: Remove create_mock_sql_handler() create_to_request() and alter_to_request() don't need `&self`, so we don't need to mock the sql handler to test them * feat: Enable procedure manager by default * docs: Update config example * test: Enable procedure framework in all tests * refactor(datanode): rename methods using procedure * test(catalog): Fix temp dir drops before test finishes * tests: Enable procedure framework in sqlness * test: Fix sqlness standalone rename test * fix: Drop procedure allows table not in engine * test: Change rename table test * fix: add options to table meta when creating table by procedure * test: adjust error message in schema test case * test: Fix test_sql_api error message
Sqlness Test
Sqlness manual
Case file
Sqlness has two types of file
.sql: test input, SQL only.result: expected test output, SQL and its results
.result is the output (execution result) file. If you see .result files is changed,
it means this test gets a different result and indicates it fails. You should
check change logs to solve the problem.
You only need to write test SQL in .sql file, and run the test.
Case organization
The root dir of input cases is tests/cases. It contains several sub-directories stand for different test
modes. E.g., standalone/ contains all the tests to run under greptimedb standalone start mode.
Under the first level of sub-directory (e.g. the cases/standalone), you can organize your cases as you like.
Sqlness walks through every file recursively and runs them.
Run the test
Unlike other tests, this harness is in a binary target form. You can run it with
cargo sqlness
It automatically finishes the following procedures: compile GreptimeDB, start it, grab tests and feed it to
the server, then collect and compare the results. You only need to check if the .result files are changed.
If not, congratulations, the test is passed 🥳!