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
Copy file name to clipboardExpand all lines: .ci/readme.md
+12-13Lines changed: 12 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,38 +13,38 @@ Each `do` section in the yaml is mapped to a low level client method. To aid wit
13
13
way to deal with elasticsearch responses in a semi typed fashion.
14
14
15
15
These `rest-api-spec` tests are in addition to the unit and integration tests that live under `src/Tests/Tests` which for 90% of the cases focuses
16
-
more on the high level client `NEST` where as these `rest-api-spec`test fully focus on the low level client `Elasticsearch.Net`
16
+
more on the high level client `NEST` where as these `rest-api-spec`tests fully focus on the low level client `Elasticsearch.Net`
17
17
18
-
The `DockerFile` in this folder sets up this repos inside a docker container ready to run our build.
18
+
The `DockerFile` in this folder sets up this repo inside a docker container ready to run our build.
19
19
20
20
The `rest-api-spec` runner expects Elasticsearch to be started before invocation and uses the endpoint its passed to discover the current Elasticsearch
21
21
`build hash` that is running and downloads the tests matching that `build hash`.
22
22
23
-
If you want to run the tests the same that the Jenkins instance on elastic.co does you can call
23
+
If you want to run the tests the same way that the Jenkins instance on elastic.co does you can call
0 commit comments