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: README.md
+38-1Lines changed: 38 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ It allows to launch tests with minimal dependencies.
8
8
9
9
Current development version is `0.2.0-SNAPSHOT`. [](https://travis-ci.org/microcks/microcks-cli)
MicrocksClient got status for test "5c1781cf6310d94f8169384e" - success: false, inProgress: true
47
47
MicrocksTester waiting for 2 seconds before checking again.
48
48
MicrocksClient got status for test "5c1781cf6310d94f8169384e" - success: true, inProgress: false
49
+
```
50
+
51
+
### Advanced options
52
+
53
+
The `test` command provides additional flags for advanced usages and options:
54
+
*`--verbose` allows to dump on standard output all the HTTP requests and responses,
55
+
*`--insecure` allows to interact with Microcks and Keycloak instances through HTTPS without checking certificates issuer CA,
56
+
*`--caCerts=<path1,path2>` allows to specify additional certificates CRT files to add to trusted roots ones,
57
+
*`--operationsHeaders=<JSON>` allows to override some operations headers for the tests to launch.
58
+
59
+
Overriden test operations headers is a JSON strings where 1st level keys are operation name (eg. `GET /beer`) or `globals` for header applying to all the operations of the API. Headers are specified as an array of objects defining `key` and `values` properties.
60
+
61
+
Here's below an example of using some of this flags:
62
+
63
+
```
64
+
./microcks-cli test 'Beer Catalog API:0.9' http://localhost:9090/api/ POSTMAN \
Binary releases for Linux, MacOS or Windows platform are available on the GitHub [releases page](https://github.com/microcks/microcks-cli/releases). Just download the binary corresponding to your system and put the binar into the `PATH` somewhere ;-)
77
+
78
+
### Container image
79
+
80
+
The `microcks-cli` is now available as a container image as version `0.2.0`. So that you'd be able to easily use it from a GitLab CI or a [Tekton pipeline](https://github.com/tektoncd/pipeline). The hosting repository is now on Docker Hub [here](https://cloud.docker.com/u/microcks/repository/docker/microcks/microcks-cli).
81
+
82
+
Below a sample on how using the image without getting the CLI binary:
0 commit comments