github.com/leonlxy/hyperledger@v1.0.0-alpha.0.20170427033203-34922035d248/bddtests/features/endorser.feature (about) 1 # 2 # Test Endorser function 3 # 4 # Tags that can be used and will affect test internals: 5 # @doNotDecompose will NOT decompose the named compose_yaml after scenario ends. Useful for setting up environment and reviewing after scenario. 6 7 @endorser 8 Feature: Endorser 9 As a application developer 10 I want to get endorsements and submit transactions and receive events 11 12 # @doNotDecompose 13 @FAB-184 14 Scenario Outline: Basic deploy endorsement for chaincode through GRPC to multiple endorsers 15 16 Given we compose "<ComposeFile>" 17 And I wait "1" seconds 18 And I register with CA supplying username "binhn" and secret "7avZQLwcUe9q" on peers: 19 | vp0 | 20 21 When user "binhn" creates a chaincode spec "cc_spec" of type "GOLANG" for chaincode "github.com/hyperledger/fabric/examples/chaincode/go/chaincode_example02" with args 22 | funcName | arg1 | arg2 | arg3 | arg4 | 23 | init | a | 100 | b | 200 | 24 And user "binhn" creates a deployment spec "cc_deploy_spec" using chaincode spec "cc_spec" and devops on peer "vp0" 25 And user "binhn" creates a deployment proposal "proposal1" using chaincode deployment spec "cc_deploy_spec" 26 And user "binhn" sends proposal "proposal1" to endorsers with timeout of "20" seconds: 27 | vp0 | vp1 | vp2 | vp3 | 28 And user "binhn" stores their last result as "proposal1Responses" 29 Then user "binhn" expects proposal responses "proposal1Responses" with status "200" from endorsers: 30 | vp0 | vp1 | vp2 | vp3 | 31 32 33 Examples: Orderer Options 34 | ComposeFile | Waittime | 35 | docker-compose-next-4.yml | 60 | 36 37 38 # @doNotDecompose 39 @FAB-314 40 Scenario Outline: Advanced deploy endorsement with ESCC for chaincode through GRPC to single endorser 41 42 Given we compose "<ComposeFile>" 43 And I register with CA supplying username "binhn" and secret "7avZQLwcUe9q" on peers: 44 | vp0 | 45 46 When user "binhn" creates a chaincode spec of type "GOLANG" for chaincode "github.com/hyperledger/fabric/examples/chaincode/go/chaincode_example02" aliased as "cc_spec" with args 47 | funcName | arg1 | arg2 | arg3 | arg4 | 48 | init | a | 100 | b | 200 | 49 And user "binhn" sets ESCC to "my_escc" for chaincode spec "cc_spec" 50 And user "binhn" creates a deployment proposal "proposal1" using chaincode spec "cc_spec" 51 And user "binhn" sends proposal "proposal1" to endorsers with timeout of "20" seconds: 52 | vp0 | vp1 | vp2 | vp3 | 53 And user "binhn" stores their last result as "proposal1Responses" 54 Then user "binhn" expects proposal responses "proposal1Responses" with status "200" from endorsers: 55 | vp0 | vp1 | vp2 | vp3 | 56 57 Examples: Orderer Options 58 | ComposeFile | Waittime | 59 | docker-compose-next-4.yml | 60 | 60 61 # @doNotDecompose 62 @FAB-314 63 Scenario Outline: Advanced deploy endorsement with VSCC for chaincode through GRPC to single endorser 64 65 Given we compose "<ComposeFile>" 66 And I register with CA supplying username "binhn" and secret "7avZQLwcUe9q" on peers: 67 | vp0 | 68 69 When user "binhn" creates a chaincode spec of type "GOLANG" for chaincode "github.com/hyperledger/fabric/examples/chaincode/go/chaincode_example02" aliased as "cc_spec" with args 70 | funcName | arg1 | arg2 | arg3 | arg4 | 71 | init | a | 100 | b | 200 | 72 And user "binhn" sets VSCC to "my_vscc" for chaincode spec "cc_spec" 73 And user "binhn" creates a deployment proposal "proposal1" using chaincode spec "cc_spec" 74 And user "binhn" sends proposal "proposal1" to endorsers with timeout of "20" seconds: 75 | vp0 | vp1 | vp2 | vp3 | 76 And user "binhn" stores their last result as "proposal1Responses" 77 Then user "binhn" expects proposal responses "proposal1Responses" with status "200" from endorsers: 78 | vp0 | vp1 | vp2 | vp3 | 79 80 Examples: Orderer Options 81 | ComposeFile | Waittime | 82 | docker-compose-next-4.yml | 60 | 83