From 1ff2ea7035112ac07f7c0af885e8931212439edf Mon Sep 17 00:00:00 2001 From: Jiacai Liu Date: Mon, 6 Feb 2023 22:10:53 +0800 Subject: [PATCH] chore: release 0.3.0 (#33) * chore: release 0.3.0 * center image --- Cargo.toml | 2 +- README.md | 7 ++++++- sqlness-flowchart.svg | 4 ++++ 3 files changed, 11 insertions(+), 2 deletions(-) create mode 100644 sqlness-flowchart.svg diff --git a/Cargo.toml b/Cargo.toml index 00a8659..d5ed694 100644 --- a/Cargo.toml +++ b/Cargo.toml @@ -1,6 +1,6 @@ [package] name = "sqlness" -version = "0.2.0" +version = "0.3.0" edition = "2021" authors = [ "CeresDB Authors ", diff --git a/README.md b/README.md index 7a99df2..dc65bd9 100644 --- a/README.md +++ b/README.md @@ -19,7 +19,7 @@ $ tree examples/ examples/ ├── basic-case # Testcase root directory │ └── simple # One environment -│ ├── config.toml # Config file for current environment +│ ├── config.toml # Config file for current environment, optional │ ├── select.result # Output result file │ └── select.sql # Input SQL testcase ├── basic.rs # Entrypoint of this example @@ -42,6 +42,11 @@ Usually `result` files should be tracked in git, whenever there are failed tests 1. Update `result` to latest version(e.g. `git add`) if the newer result is right, or 2. Restore `result` back to original version (e.g. `git checkout`), troubleshoot bugs in database implementation, and run tests again +Flowchart below illustrates the typical steps when write a test. +

+ +

+ Below is the output of this example: ```bash Run testcase... diff --git a/sqlness-flowchart.svg b/sqlness-flowchart.svg new file mode 100644 index 00000000..352a781 --- /dev/null +++ b/sqlness-flowchart.svg @@ -0,0 +1,4 @@ + + + +
Run tests
Run tests
Expected
Expected
No
No
Create or
update
result
Create or...
check out result
(git checkout)
check out result...
Check in result
(git add)
Check in result...
Write SQL tests
Write SQL tests
Done
Done
fix bugs
fix bugsViewer does not support full SVG 1.1 \ No newline at end of file