gvsafronov/futriix
1
0
Fork 0
Code Issues Pull Requests Actions 3 Packages Projects Releases Wiki Activity

Replcae sentinel commands sanity check with infrastructure work test (#11950)

Browse Source 
The sanity check test intention was to detect that when a command is
added to sentinel it is on purpose. This test is easily broken, like
CLIENT SETINFO introduced by #11758.

We replace it with a test that validates that a few specific commands
are either there or missing (to test the infrastructure works correctly).
This commit is contained in:
Binbin 2023-03-22 18:18:03 +08:00 committed by GitHub
parent ef50118c92
commit 9c4c90c1bf
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 15 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
tests/sentinel/tests/00-base.tcl
View File

@ -12,10 +12,22 @@ if {$::simulate_error} {
}
}
test "Sentinel commands sanity check" {
test "Sentinel command flag infrastructure works correctly" {
foreach_sentinel_id id {
assert_equal {72} [llength [S $id command list]]
assert_equal {15} [S $id command count]
set command_list [S $id command list]
foreach cmd {ping info subscribe client|setinfo} {
assert_not_equal [S $id command docs $cmd] {}
assert_not_equal [lsearch $command_list $cmd] -1
}
foreach cmd {save bgrewriteaof blpop replicaof} {
assert_equal [S $id command docs $cmd] {}
assert_equal [lsearch $command_list $cmd] -1
assert_error {ERR unknown command*} {S $id $cmd}
}
assert_error {ERR unknown subcommand*} {S $id client no-touch}
}
}