02-Taos¶
¶
taos-CLI command line test
1. Insert data with taosBenchmark json format
2. Check taos-CLI all command lines
¶
taos-CLI basic test
1. Insert data with taosBenchmark json format
2. Check describe show full
3. Check basic command in different conn mode
4. Check version and help
5. Check command options
6. Check data dump in/out
7. Check conn mode priority and except cmd
8. Check max password length
9. Check totp code with input
10. Check password expired tips
11. Check token login with input/args
¶
taos-CLI command line
1. taos-CLI connect with different parameters
2. taos-CLI execute sql with different parameters
3. taos-CLI verify execute result with system database
4. taos-CLI parameters include: -h, -P, -u, -p, -a, -A, -c, -C, -s, -r, -f, -t, -n, -l, -N, -V, -d, -w
5. taos-CLI test -k repeatly
6. taos-CLI test environment: taosd with cluster mode
¶
taos-CLI except
1. taos-CLI connect with different error parameters
2. taos-CLI execute sql with different error parameters
3. taos-CLI expect connect or execute error
4. taos-CLI different parameters include: -h, -P, -u, -p, -a, -f
¶
taos shell hex display for non-printable BINARY
Test that the taos shell displays non-printable BINARY data in
hexadecimal format (e.g., 0x03) instead of raw invisible bytes.
Printable characters should still be displayed as normal text.
1. Check non-printable chars (0x00-0x1F, 0x7F) show as hex
2. Check printable chars (0x20-0x7E) show as normal text
3. Check whitespace chars (tab/newline/cr) are treated as non-printable
4. Check multi-byte non-printable values show as hex
5. Check mixed printable/non-printable shows entire value as hex
6. Check hex display works in file dump output
7. Check invalid multibyte bytes fallback to full hex
¶
taos-CLI net check
1. taosd normal running
2. taos-CLI -k expect 2: service ok
3. taosd stop
4. taos-CLI -k expect 0: unavailable
5. taos-CLI -n server start
6. taos-CLI -n client expect response is received
7. taosd restart
8. taos-CLI -k expect 2: service ok
¶
subscribe -h shows usage help.
¶
subscribe with no arguments shows usage help.
¶
subscribe without -g shows error.
¶
subscribe with unknown option shows warning.
¶
subscribe to non-existent topic shows error.
¶
subscribe with -o earliest receives pre-existing data.
¶
subscribe -n limits the number of rows received.
¶
Same consumer group resumes from committed offset.
¶
Different consumer groups maintain independent offsets.
¶
subscribe with -t custom timeout works normally.
¶
subscribe output contains actual column values.
¶
subscribe output includes column header.
¶
subscribe topic that includes tbname column shows table names.
¶
subscribe receives data from multiple child tables.