Skip to content
This repository was archived by the owner on Feb 4, 2026. It is now read-only.

Commit 1ff2ea7

Browse files
authored
chore: release 0.3.0 (#33)
* chore: release 0.3.0 * center image
1 parent 2cc78f3 commit 1ff2ea7

3 files changed

Lines changed: 11 additions & 2 deletions

File tree

Cargo.toml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
[package]
22
name = "sqlness"
3-
version = "0.2.0"
3+
version = "0.3.0"
44
edition = "2021"
55
authors = [
66
"CeresDB Authors <ceresdbservice@gmail.com>",

README.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ $ tree examples/
1919
examples/
2020
├── basic-case # Testcase root directory
2121
│ └── simple # One environment
22-
│ ├── config.toml # Config file for current environment
22+
│ ├── config.toml # Config file for current environment, optional
2323
│ ├── select.result # Output result file
2424
│ └── select.sql # Input SQL testcase
2525
├── basic.rs # Entrypoint of this example
@@ -42,6 +42,11 @@ Usually `result` files should be tracked in git, whenever there are failed tests
4242
1. Update `result` to latest version(e.g. `git add`) if the newer result is right, or
4343
2. Restore `result` back to original version (e.g. `git checkout`), troubleshoot bugs in database implementation, and run tests again
4444

45+
Flowchart below illustrates the typical steps when write a test.
46+
<p align="center">
47+
<img src="sqlness-flowchart.svg" />
48+
</p>
49+
4550
Below is the output of this example:
4651
```bash
4752
Run testcase...

sqlness-flowchart.svg

Lines changed: 4 additions & 0 deletions
Loading

0 commit comments

Comments
 (0)