-
Notifications
You must be signed in to change notification settings - Fork 301
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrates more tests from duckdb #1168
Comments
Could we introduce the Sqllogictest-rs framework to perform tests? |
We already have sqlness https://docs.greptime.com/developer-guide/tests/sqlness-test |
I see. I thought we could utilize the existing sqllogictest test files, but we still need to modify them. |
Hello!I'm new to here.Can I have a try to migrate select tests?What test cases can I refer to that have been migrated? where are they? |
@Gump9 We are expecting the duckdb's test cases, the SQLs, to be ported into our sqlness tests. To start, you can learn everything about sqlness tests here. Then you can check the duckdb's test cases, to see if the SQL is already present in our sqlness tests. If not, just add that case to our sqlness tests. |
What type of enhancement is this?
Tech debt reduction, Other
What does the enhancement do?
We already migrate some tests from duckdb's SQL test: https://github.com/duckdb/duckdb/tree/master/test/sql. And it already helps us figure out some bugs such as #790 #791 #759 etc.
But there are still many tests that still need to be migrated. Let's create an issue to track them:
I list the main tests. Of course, our current tests still miss many cases; they must also be migrated.
Implementation challenges
No response
The text was updated successfully, but these errors were encountered: