github.com/darrenli6/fabric-sdk-example@v0.0.0-20220109053535-94b13b56df8c/bddtests/features/endorser.feature (about)

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