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
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,8 @@ See the [gateway.proto file](https://github.com/hyperledger/fabric-protos/blob/m
20
20
21
21
This repository comprises three functionally equivalent client APIs, written in Go, Typescript, and Java. In order to
22
22
build these components, the following need to be installed and available in the PATH:
23
-
-[Go 1.20+](https://go.dev/)
23
+
24
+
-[Go 1.21+](https://go.dev/)
24
25
-[Node 18+](https://nodejs.org/)
25
26
-[Java 8+](https://adoptium.net/)
26
27
-[Docker](https://www.docker.com/)
@@ -42,6 +43,7 @@ In order to run any of the Hardware Security Module (HSM) tests, [SoftHSM v2](ht
42
43
> **Note:** When the repository is first cloned, some mock implementations used for testing will not be present and the Go code will show compile errors. These will be generated when the `unit-test` target is run, or can be generated explicitly by running `make generate`.
43
44
44
45
The following Makefile targets are available:
46
+
45
47
-`make generate` - generate mock implementations used by unit tests
46
48
-`make lint` - run linting checks for the Go code
47
49
-`make unit-test-go` - run unit tests for the Go client API, excluding HSM tests
@@ -63,7 +65,7 @@ The following Makefile targets are available:
63
65
### Scenario tests
64
66
65
67
The scenario tests create a Fabric network comprising two orgs (one peer in each org) and a single gateway within a set
66
-
of docker containers. The clients connect to the gateway to submit transactions and query the ledger state.
68
+
of docker containers. The clients connect to the gateway to submit transactions and query the ledger state.
67
69
68
-
The tests are defined as feature files using the Cucumber BDD framework. The same set of feature files
70
+
The tests are defined as feature files using the Cucumber BDD framework. The same set of feature files
69
71
is used across all three client language implementations to ensure consistency of behaviour.
0 commit comments