github.com/tenywen/fabric@v1.0.0-beta.0.20170620030522-a5b1ed380643/test/feature/peer.feature (about) 1 # Copyright IBM Corp. 2017 All Rights Reserved. 2 # 3 # Licensed under the Apache License, Version 2.0 (the "License"); 4 # you may not use this file except in compliance with the License. 5 # You may obtain a copy of the License at 6 # 7 # http://www.apache.org/licenses/LICENSE-2.0 8 # 9 # Unless required by applicable law or agreed to in writing, software 10 # distributed under the License is distributed on an "AS IS" BASIS, 11 # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 12 # See the License for the specific language governing permissions and 13 # limitations under the License. 14 # 15 16 Feature: Peer Service 17 As a user I want to be able have channels and chaincodes to execute 18 19 20 Scenario Outline: FAB-3505: Test chaincode example02 deploy, invoke, and query 21 Given I have a bootstrapped fabric network of type <type> 22 When a user deploys chaincode at path "github.com/hyperledger/fabric/chaincode_example02" with ["init", "a", "1000" , "b", "2000"] with name "mycc" 23 Then the chaincode is deployed 24 When a user queries on the chaincode named "mycc" with args ["query", "a"] 25 Then a user receives expected response of 1000 26 When a user invokes on the chaincode named "mycc" with args ["txId1", "invoke", "a", 10] 27 And a user queries on the chaincode named "mycc" with args ["query", "a"] 28 Then a user receives expected response of 990 29 30 Given "peer1.org1.example.com" is taken down 31 When a user invokes on the chaincode named "mycc" with args ["txId1", "invoke", "a", 10] 32 And I wait "15" seconds 33 Given "peer1.org1.example.com" comes back up 34 When a user queries on the chaincode named "mycc" with args ["query", "a"] on "peer1.org1.example.com" 35 Then a user receives expected response of 980 36 Examples: 37 | type | 38 | solo | 39 | kafka | 40 41 42 Scenario Outline: FAB-1440: Test basic chaincode deploy, invoke, query 43 Given I have a bootstrapped fabric network of type <type> 44 When a user deploys chaincode 45 Then the chaincode is deployed 46 When a user queries on the chaincode 47 Then a user receives expected response 48 Examples: 49 | type | 50 | solo | 51 | kafka | 52 53 54 @skip 55 Scenario: FAB-3861: Basic Chaincode Execution (example02) 56 Given I have a bootstrapped fabric network 57 When a user deploys chaincode 58 Then the chaincode is deployed 59 60 61 @skip 62 Scenario: FAB-3865: Multiple Channels Per Peer 63 Given I have a bootstrapped fabric network 64 When a user deploys chaincode 65 Then the chaincode is deployed 66 67 68 @skip 69 Scenario: FAB-3866: Multiple Chaincodes Per Peer 70 Given I have a bootstrapped fabric network 71 When a user deploys chaincode 72 Then the chaincode is deployed