hyperledger / hyperledger/fabric-gateway
Test with Fabric v3
- Dominant language
- Java
- Stars
- 194
- Forks
- 110
- Avg merge
- 18h 46m
- Merged PRs (30d)
- 42
Description
**As a** maintainer
**I want** to run scenario tests with Fabric v3
**So that** I have confidence that the client API continues to work with Fabric v3
Testing for pull request and merge builds should continue to be run with Fabric v2.5 while it remains a supported LTS release. Prior to release, Fabric v3 testing could be carried out either as a separate build, or using a matrix to test with both Fabric v2.5 and v3. This work could also be deferred until Fabric v3 is released.
Note that no `hyperledger/fabric-tools` Docker image is published for Fabric v3. This is used in the current scenario tests to run CLI commands when configuring the Fabric network. The scenario tests will need rework to either download and use the CLI commands directly, or to use an alternative approach, such as a Kubernetes operator or [fabric-admin-sdk](https://github.com/hyperledger/fabric-admin-sdk).
Contributor guide
Research direction
Start by locating the current scenario tests and their use of the hyperledger/fabric-tools Docker image for Fabric network configuration. Determine how Fabric v3 testing should coexist with Fabric v2.5 testing, then verify that the scenario tests run successfully against Fabric v3 using an agreed CLI or alternative approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, kubernetes
- Domain
- blockchain, devops, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100