mirrors/ceph-csi
1
0
Fork 0
mirror of https://github.com/ceph/ceph-csi.git synced 2024-12-18 02:50:30 +00:00
Code Issues Packages Projects Releases Wiki Activity

doc: correct e2e documentation formatting

Browse Source 
This commit address formatting and alligment issues in e2e README.

Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
This commit is contained in:
Humble Chirammal 2022-08-18 15:06:52 +05:30 committed by mergify[bot]
parent 5cb8f80c10
commit a9446c328e
1 changed files with 25 additions and 22 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

37
e2e/README.md
View File

@ -10,16 +10,16 @@
## Introduction
End-to-end (e2e) in cephcsi provides a mechanism to test the end-to-end
behavior of the system, These tests will interact with live instances of ceph
cluster just like how a user would.
End-to-end (e2e) in cephcsi provides a mechanism to test the end-to-end behavior
of the system, These tests will interact with live instances of ceph cluster
just like how a user would.
The primary objectives of the e2e tests are to ensure a consistent and reliable
behavior of the cephcsi code base and to catch hard-to-test bugs before
users do when unit and integration tests are insufficient.
behavior of the cephcsi code base and to catch hard-to-test bugs before users do
when unit and integration tests are insufficient.
The Test framework is designed
to install Rook, run cephcsi tests, and uninstall Rook.
The Test framework is designed to install Rook, run cephcsi tests, and uninstall
Rook.
The e2e test are built on top of [Ginkgo](http://onsi.github.io/ginkgo/) and
[Gomega](http://onsi.github.io/gomega/)
@ -45,7 +45,8 @@ the following parameters are available to configure kubernetes cluster
| cephcsi | Copy built docker images to kubernetes cluster |
| k8s-sidecar | Copy kubernetes sidecar docker images to kubernetes cluster |
following environment variables can be exported to customize kubernetes deployment
following environment variables can be exported to customize kubernetes
deployment
| ENV | Description | Default |
|----------------------|--------------------------------------------------|--------------------------------------------------------------------|
@ -74,9 +75,11 @@ following environment variables can be exported to customize kubernetes deployme
## Deploy Rook
The cephcsi E2E tests expects that you already have rook running in your cluster.
The cephcsi E2E tests expects that you already have rook running in your
cluster.
Thanks to [minikube](../scripts/minikube.sh) script for the handy `deploy-rook` option.
Thanks to [minikube](../scripts/minikube.sh) script for the handy `deploy-rook`
option.
```console
./scripts/minikube.sh deploy-rook
@ -84,8 +87,8 @@ Thanks to [minikube](../scripts/minikube.sh) script for the handy `deploy-rook`
## Test parameters
In addition to standard go tests parameters, the following custom parameters
are available while running tests:
In addition to standard go tests parameters, the following custom parameters are
available while running tests:
| flag | description |
| ----------------- | ------------------------------------------------------------------------------------------------- |
@ -108,8 +111,8 @@ are available while running tests:
## E2E for snapshot
After the support for snapshot/clone has been added to ceph-csi,
you need to follow these steps before running e2e.
After the support for snapshot/clone has been added to ceph-csi, you need to
follow these steps before running e2e.
- Install snapshot controller and snapshot CRD
@ -126,9 +129,9 @@ you need to follow these steps before running e2e.
## Running E2E
`
Note:- Prior to running the tests, you may need to copy the kubernetes configuration
file to `$HOME/.kube/config` which is required to communicate with kubernetes
cluster or you can pass `kubeconfig`flag while running tests.
Note:- Prior to running the tests, you may need to copy the kubernetes
configuration file to `$HOME/.kube/config` which is required to communicate with
kubernetes cluster or you can pass `kubeconfig` flag while running tests.
`
Functional tests are run by the `go test` command.