rust/greptimedb
1
0
Fork 0
mirror of https://github.com/GreptimeTeam/greptimedb.git synced 2026-05-30 11:50:38 +00:00
Code Issues Packages Projects Releases Wiki Activity

chore(deps): bump sqlness to v0.4 (#1101)

Browse Source 
deps: bump sqlness to v0.4

Signed-off-by: Ruihang Xia <waynestxia@gmail.com>
This commit is contained in:
Ruihang Xia
2023-03-01 17:27:16 +08:00
committed by GitHub
parent 8e7e68708f
commit d5a2a26916
4 changed files with 9 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
Cargo.lock generated
View File

@@ -7207,8 +7207,9 @@ dependencies = [
[[package]]
name = "sqlness"
version = "0.3.0"
source = "git+https://github.com/CeresDB/sqlness.git?rev=e6d602ed7d894ffb806580f17f4a6f1283abbf1f#e6d602ed7d894ffb806580f17f4a6f1283abbf1f"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "bc90b1d2e46d618148d3118ec25c3cb4c18563fef8589095fc21389952c54864"
dependencies = [
"async-trait",
"derive_builder 0.11.2",

14
tests/README.md
View File

@@ -6,20 +6,12 @@
Sqlness has three types of file
- `.sql`: test input, SQL only
- `.result`: expected test output, SQL and its results
- `.output`: different output, SQL and its results
Both `.result` and `.output` are output (execution result) files. The difference is that `.result` is the
the standard (expected) output, and `.output` is the error output. Therefore, if you see `.output` files generated,
`.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. On the first run it produces
an `.output` file because there is no `.result` to compare with. If you can make sure the content in
`.output` is correct, you can rename it to `.result`, which means it is the expected output.
And at any time there should only be two file types, `.sql` and `.result` -- otherwise, an existing `.output`
file means your test fails. That's why we should not ignore `.output` file type in `.gitignore`, instead, track
it and make sure it doesn't exist.
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
@@ -34,5 +26,5 @@ 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 whether there are new `.output` files.
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 🥳!

2
tests/runner/Cargo.toml
View File

@@ -13,6 +13,6 @@ common-grpc = { path = "../../src/common/grpc" }
common-query = { path = "../../src/common/query" }
common-time = { path = "../../src/common/time" }
serde.workspace = true
sqlness = { git = "https://github.com/CeresDB/sqlness.git", rev = "e6d602ed7d894ffb806580f17f4a6f1283abbf1f" }
sqlness = "0.4"
tinytemplate = "1.2"
tokio.workspace = true

4
tests/runner/src/env.rs
View File

@@ -26,7 +26,7 @@ use common_error::ext::ErrorExt;
use common_error::snafu::ErrorCompat;
use common_query::Output;
use serde::Serialize;
use sqlness::{Database, EnvController};
use sqlness::{Database, EnvController, QueryContext};
use tinytemplate::TinyTemplate;
use tokio::process::{Child, Command};
use tokio::sync::Mutex;
@@ -269,7 +269,7 @@ pub struct GreptimeDB {
#[async_trait]
impl Database for GreptimeDB {
async fn query(&self, query: String) -> Box<dyn Display> {
async fn query(&self, _ctx: QueryContext, query: String) -> Box<dyn Display> {
let mut client = self.client.lock().await;
if query.trim().starts_with("USE ") {
let database = query