github.com/adnan-c/fabric_e2e_couchdb@v0.6.1-preview.0.20170228180935-21ce6b23cf91/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  #  @chaincodeImagesUpToDate use this if all scenarios chaincode images are up to date, and do NOT require building.  BE SURE!!!
     7  
     8  #@chaincodeImagesUpToDate
     9  @endorser
    10  Feature: Endorser
    11      As a application developer
    12      I want to get endorsements and submit transactions and receive events
    13  
    14  #    @doNotDecompose
    15      @FAB-184
    16    	Scenario Outline: Basic deploy endorsement for chaincode through GRPC to multiple endorsers
    17  
    18  	    Given we compose "<ComposeFile>"
    19          And I wait "1" seconds
    20          And I register with CA supplying username "binhn" and secret "7avZQLwcUe9q" on peers:
    21            | vp0  |
    22  
    23          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
    24               | funcName | arg1 |  arg2 | arg3 | arg4 |
    25               |   init   |  a   |  100  |  b   |  200 |
    26          And user "binhn" creates a deployment spec "cc_deploy_spec" using chaincode spec "cc_spec" and devops on peer "vp0"
    27          And user "binhn" creates a deployment proposal "proposal1" using chaincode deployment spec "cc_deploy_spec"
    28          And user "binhn" sends proposal "proposal1" to endorsers with timeout of "20" seconds:
    29            | vp0  | vp1 | vp2 |  vp3  |
    30          And user "binhn" stores their last result as "proposal1Responses"
    31          Then user "binhn" expects proposal responses "proposal1Responses" with status "200" from endorsers:
    32            | vp0  | vp1 | vp2 |  vp3  |
    33  
    34  
    35      Examples: Orderer Options
    36          |          ComposeFile                 |    Waittime   |
    37          |   docker-compose-next-4.yml          |       60      |
    38  
    39  
    40  #    @doNotDecompose
    41      @FAB-314
    42  	Scenario Outline: Advanced deploy endorsement with ESCC for chaincode through GRPC to single endorser
    43  
    44  	    Given we compose "<ComposeFile>"
    45          And I register with CA supplying username "binhn" and secret "7avZQLwcUe9q" on peers:
    46            | vp0  |
    47  
    48          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
    49               | funcName | arg1 |  arg2 | arg3 | arg4 |
    50               |   init   |  a   |  100  |  b   |  200 |
    51          And user "binhn" sets ESCC to "my_escc" for chaincode spec "cc_spec"
    52          And user "binhn" creates a deployment proposal "proposal1" using chaincode spec "cc_spec"
    53          And user "binhn" sends proposal "proposal1" to endorsers with timeout of "20" seconds:
    54            | vp0  | vp1 | vp2 |  vp3  |
    55          And user "binhn" stores their last result as "proposal1Responses"
    56          Then user "binhn" expects proposal responses "proposal1Responses" with status "200" from endorsers:
    57            | vp0  | vp1 | vp2 |  vp3  |
    58  
    59      Examples: Orderer Options
    60          |          ComposeFile           |    Waittime   |
    61          |   docker-compose-next-4.yml    |       60      |
    62  
    63  #    @doNotDecompose
    64      @FAB-314
    65  	Scenario Outline: Advanced deploy endorsement with VSCC for chaincode through GRPC to single endorser
    66  
    67  	    Given we compose "<ComposeFile>"
    68          And I register with CA supplying username "binhn" and secret "7avZQLwcUe9q" on peers:
    69            | vp0  |
    70  
    71          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
    72               | funcName | arg1 |  arg2 | arg3 | arg4 |
    73               |   init   |  a   |  100  |  b   |  200 |
    74          And user "binhn" sets VSCC to "my_vscc" for chaincode spec "cc_spec"
    75          And user "binhn" creates a deployment proposal "proposal1" using chaincode spec "cc_spec"
    76          And user "binhn" sends proposal "proposal1" to endorsers with timeout of "20" seconds:
    77            | vp0  | vp1 | vp2 |  vp3  |
    78          And user "binhn" stores their last result as "proposal1Responses"
    79          Then user "binhn" expects proposal responses "proposal1Responses" with status "200" from endorsers:
    80            | vp0  | vp1 | vp2 |  vp3  |
    81  
    82      Examples: Orderer Options
    83          |          ComposeFile           |    Waittime   |
    84          |   docker-compose-next-4.yml    |       60      |
    85