As a contributor
I want integration tests to use the development chaincode Docker image
So that I can confirm that a release version of the codebase will function correctly
The chaincodes used by the integration tests run in microfab. This offers a functional Fabric environment and is extremely quick. However, the chaincode environment is not the same as the chaincode Docker image defined in fabric-chaincode-docker.
It might be sufficient for a smaller set of tests to use the development chaincode Docker image rather than have all integration tests run there. The scenarios should cover both Gradle and Maven chaincode to ensure that the image contents provide all the necessary tools.
As a contributor
I want integration tests to use the development chaincode Docker image
So that I can confirm that a release version of the codebase will function correctly
The chaincodes used by the integration tests run in microfab. This offers a functional Fabric environment and is extremely quick. However, the chaincode environment is not the same as the chaincode Docker image defined in fabric-chaincode-docker.
It might be sufficient for a smaller set of tests to use the development chaincode Docker image rather than have all integration tests run there. The scenarios should cover both Gradle and Maven chaincode to ensure that the image contents provide all the necessary tools.