github.com/adnan-c/fabric_e2e_couchdb@v0.6.1-preview.0.20170228180935-21ce6b23cf91/bddtests/peer_logging.feature (about) 1 # 2 # Test Logging Features of Peers 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 @preV1 8 Feature: Peer Logging 9 As a Fabric Developer 10 I want to verify my Peers log correctly 11 12 Scenario: Invoke is attempted after deploy in Dev Mode 13 Given we compose "docker-compose-1-devmode.yml" 14 When I deploy chaincode with name "testCC" and with ctor "init" to "vp0" 15 | arg1 | arg2 | arg3 | arg4 | 16 | a | 100 | b | 200 | 17 And I invoke chaincode "testCC" function name "invoke" on "vp0" 18 |arg1|arg2|arg3| 19 | a | b | 10 | 20 Then ensure after 2 seconds there are no errors in the logs for peer vp0 21 22 Scenario: Query is attempted after deploy in Dev Mode 23 Given we compose "docker-compose-1-devmode.yml" 24 When I deploy chaincode with name "testCC" and with ctor "init" to "vp0" 25 | arg1 | arg2 | arg3 | arg4 | 26 | a | 100 | b | 200 | 27 And I query chaincode "testCC" function name "query" on "vp0": 28 |arg1| 29 | a | 30 Then ensure after 2 seconds there are no errors in the logs for peer vp0 31 32 Scenario: Invoke is attempted before deploy in Dev Mode 33 Given we compose "docker-compose-1-devmode.yml" 34 When I mock deploy chaincode with name "testCC" 35 And I invoke chaincode "testCC" function name "invoke" on "vp0" 36 |arg1|arg2|arg3| 37 | a | b | 10 | 38 Then I wait up to 5 seconds for an error in the logs for peer vp0 39 40 Scenario: Query is attempted before deploy in Dev Mode 41 Given we compose "docker-compose-1-devmode.yml" 42 When I mock deploy chaincode with name "testCC" 43 And I query chaincode "testCC" function name "query" on "vp0": 44 |arg1| 45 | a | 46 Then I wait up to 5 seconds for an error in the logs for peer vp0