You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sanity tests can be run from VS Code, etc directly or via the cmd line:
47
107
```
48
-
$ ./test/run-sanity.sh
108
+
./test/run-sanity.sh
49
109
```
50
110
51
-
### Unit Tests
52
-
Unit tests can be run from VS Code, etc directly or via the cmd line:
53
-
```
54
-
$ ./test/run-unit.sh
111
+
### Unit tests:
112
+
113
+
```sh
114
+
./test/run-unit.sh
55
115
```
56
116
57
-
### Performance Tests
58
-
Performance tests are run in automated testing frameworks, but you may wish to run them locally to benchmark changes. For a given test configuration, you need to modify the `test-config.yaml` file automatically generated from running one of the `run-k8s-integration...` or `run-windows-k8s-integration.sh` scripts to enable performance tests.
117
+
### Performance tests
118
+
119
+
Performance tests are run in automated testing frameworks, but you may wish to
120
+
run them locally to benchmark changes. For a given test configuration, you need
121
+
to modify the `test-config.yaml` file automatically generated from running one
122
+
of the `run-k8s-integration...` or `run-windows-k8s-integration.sh` scripts to
123
+
enable performance tests.
59
124
60
125
```yaml
61
126
DriverInfo:
@@ -71,47 +136,54 @@ DriverInfo:
71
136
72
137
You may modify the parameter values to customize the test.
73
138
74
-
You also need to modify the `StorageClass` file pointed to in `test-config.yaml` to set `volumeBindingMode: Immediate`, as the performance tests only support this mode.
139
+
You also need to modify the `StorageClass` file pointed to in `test-config.yaml`
140
+
to set `volumeBindingMode: Immediate`, as the performance tests only support
141
+
this mode.
75
142
76
-
We will be running the Kubernetes integration tests directly from its repository. Install `kubetest` and set up a test cluster with the driver installed. Now, cd into `$GOPATH/src/k8s.io/kubernetes` and run
143
+
We will be running the Kubernetes integration tests directly from its
144
+
repository. Install `kubetest` and set up a test cluster with the driver
145
+
installed. Now, cd into `$GOPATH/src/k8s.io/kubernetes` and run
77
146
78
-
```bash
147
+
```sh
79
148
# pwd=k/k
80
149
kubetest <custom flags based on your provider> \
81
150
--check-version-skew=false \
82
151
--test \
83
152
--test_args="--ginkgo.focus=External.Storage.*volume-lifecycle-performance --allowed-not-ready-nodes=10 --node-os-distro=<linux or windows> --storage.testdriver=<path-to-test-config>"
84
153
```
85
154
86
-
## Dependency Management
155
+
## Dependency management
87
156
88
157
Use [dep](https://github.com/golang/dep)
89
-
```
90
-
$ dep ensure
158
+
159
+
```sh
160
+
dep ensure
91
161
```
92
162
93
163
To modify dependencies or versions change `./Gopkg.toml`
94
164
95
165
## Debugging
96
166
97
-
We use https://github.com/go-delve/delve and its feature for remote debugging. This feature
98
-
is only available in the PD CSI Controller (which runs in a linux node).
167
+
We use https://github.com/go-delve/delve and its feature for remote debugging.
168
+
This feature is only available in the PD CSI Controller (which runs in a linux
169
+
node).
99
170
100
171
Requirements:
101
172
102
-
- https://github.com/go-delve/delve
173
+
- https://github.com/go-delve/delve
103
174
104
175
Steps:
105
176
106
-
- Build the PD CSI driver with additional compiler flags.
177
+
- Build the PD CSI driver with additional compiler flags.
0 commit comments