Update the testdata to check the expected behavior
Using same value 42 can not test against the behavior that duplicated key should result in a failure
This commit is contained in:
parent
5d93197f0b
commit
595612479d
|
|
@ -18,7 +18,7 @@ TEST_CASE("sync operations") {
|
||||||
// add
|
// add
|
||||||
CHECK(0 == etcd.add("/test/key1", "42").error_code());
|
CHECK(0 == etcd.add("/test/key1", "42").error_code());
|
||||||
CHECK(etcd::ERROR_KEY_ALREADY_EXISTS ==
|
CHECK(etcd::ERROR_KEY_ALREADY_EXISTS ==
|
||||||
etcd.add("/test/key1", "42").error_code()); // Key already exists
|
etcd.add("/test/key1", "41").error_code()); // Key already exists
|
||||||
CHECK("42" == etcd.get("/test/key1").value().as_string());
|
CHECK("42" == etcd.get("/test/key1").value().as_string());
|
||||||
|
|
||||||
// modify
|
// modify
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue