-
Notifications
You must be signed in to change notification settings - Fork 9.9k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
tests: Document linearizability tests
Signed-off-by: Marek Siarkowicz <siarkowicz@google.com>
- Loading branch information
Showing
3 changed files
with
30 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,24 @@ | ||
# etcd Linearizability Testing | ||
|
||
This directory consists of etcd linearizability tests, that validate the correct | ||
behavior of etcd under various system and network malfunctions. | ||
|
||
This is done by comparing how real etcd cluster behaves versus an in memory model of etcd. | ||
During the test we continuously inject different types of failures and validate etcd correctness. | ||
|
||
TODO: How linearizability is used to validate tests | ||
|
||
## Run locally | ||
|
||
1. Build etcd with failpoints (can be skipped if you ) | ||
```bash | ||
make install-gofail | ||
FAILPOINTS=true make build | ||
``` | ||
2. Run linearizability tests | ||
|
||
```bash | ||
make test-linearizability | ||
``` | ||
|
||
TODO: How to validate results |