Update chaos test README (#7922)

Signed-off-by: zhuwenxing <wenxing.zhu@zilliz.com>
pull/7924/head
zhuwenxing 2021-09-14 19:13:48 +08:00 committed by GitHub
parent 70438929e6
commit ee4cabffc8
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 6 deletions

View File

@ -40,21 +40,21 @@ Please refer to [Run E2E Tests](https://github.com/milvus-io/milvus/blob/master/
## How it works
- Test scenarios are designed by different chaos objects
- Every chaos object is defined in one yaml file locates in folder <code>chaos_objects</code>
- Every chaos yaml file specified by <code>ALL_CHAOS_YAMLS</code> in <code>constants.py</code> would be parsed as a parameter and be passed into <code>test_chaos.py</code>
- All expectations of every scenario are defined in <code>testcases.yaml</code> locates in folder <code>chaos_objects</code>
- [Chaos Mesh](https://chaos-mesh.org/) is used to inject chaos into Milvus in <code>test_chaos.py</code>
- Every chaos object is defined in one yaml file locates in folder `chaos_objects`
- Every chaos yaml file specified by `ALL_CHAOS_YAMLS` in `constants.py` would be parsed as a parameter and be passed into `test_chaos.py`
- All expectations of every scenario are defined in `testcases.yaml` locates in folder `chaos_objects`
- [Chaos Mesh](https://chaos-mesh.org/) is used to inject chaos into Milvus in `test_chaos.py`
## Run
### Manually
Run a single test scenario manually(take query node pod is killed as instance):
1. update <code>ALL_CHAOS_YAMLS = 'chaos_querynode*.yaml'</code> in <code>constants.py</code>
1. update `ALL_CHAOS_YAMLS = 'chaos_querynode*.yaml'` in `constants.py`
2. run the commands below:
```bash
cd /milvus/tests/python_client/chaos
pytest test_chaos.py --host x.x.x.x -v
pytest test_chaos.py --host ${Milvus_IP} -v
```
### Nightly