|
1 |
| -# |
2 |
| -# Test Orderer |
3 |
| -# |
4 | 1 | # 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!!! |
| 2 | +# @doNotDecompose will NOT decompose the named compose_yaml after scenario ends. |
| 3 | +# Useful for setting up environment and reviewing after scenario. |
7 | 4 |
|
8 |
| -#@chaincodeImagesUpToDate |
9 | 5 | @orderer
|
10 | 6 | Feature: Orderer
|
11 | 7 | As a Fabric developer
|
12 | 8 | I want to run and validate a orderer service
|
13 | 9 |
|
14 | 10 |
|
15 |
| - |
16 |
| - |
17 | 11 | # @doNotDecompose
|
18 |
| - Scenario Outline: Basic orderer function |
| 12 | + Scenario Outline: Basic orderer function |
19 | 13 |
|
20 |
| - Given we compose "<ComposeFile>" |
21 |
| - And I wait ".5" seconds |
22 |
| - And user "binhn" is an authorized user of the ordering service |
23 |
| - When user "binhn" broadcasts "<NumMsgsToBroadcast>" unique messages on "orderer0" |
24 |
| - And user "binhn" connects to deliver function on "orderer0" with Ack of "<SendAck>" and properties: |
| 14 | + Given we compose "<ComposeFile>" |
| 15 | + And I wait "<BootTime>" seconds |
| 16 | + And user "binhn" is an authorized user of the ordering service |
| 17 | + When user "binhn" broadcasts "<NumMsgsToBroadcast>" unique messages on "orderer0" |
| 18 | + And user "binhn" connects to deliver function on "orderer0" with Ack of "<SendAck>" and properties: |
25 | 19 | | Start | SpecifiedNumber | WindowSize |
|
26 | 20 | | SPECIFIED | 1 | 10 |
|
27 |
| - Then user "binhn" should get a delivery from "orderer0" of "<ExpectedBlocks>" blocks with "<NumMsgsToBroadcast>" messages within "<BatchTimeout>" seconds |
28 |
| - |
29 |
| - Examples: Orderer Options |
30 |
| - | ComposeFile | SendAck | NumMsgsToBroadcast | ExpectedBlocks | BatchTimeout | |
31 |
| - | docker-compose-orderer-solo.yml | true | 20 | 2 | 10 | |
32 |
| - | docker-compose-orderer-solo.yml | true | 40 | 4 | 10 | |
33 |
| - | docker-compose-orderer-solo.yml | true | 60 | 6 | 10 | |
34 |
| - |
| 21 | + Then user "binhn" should get a delivery from "orderer0" of "<ExpectedBlocks>" blocks with "<NumMsgsToBroadcast>" messages within "<BatchTimeout>" seconds |
35 | 22 |
|
| 23 | + Examples: Orderer Options |
| 24 | + | ComposeFile | SendAck | NumMsgsToBroadcast | ExpectedBlocks | BatchTimeout | BootTime | |
| 25 | + | docker-compose-orderer-solo.yml | true | 20 | 2 | 10 | .5 | |
| 26 | + | docker-compose-orderer-solo.yml | true | 40 | 4 | 10 | .5 | |
| 27 | + | docker-compose-orderer-solo.yml | true | 60 | 6 | 10 | .5 | |
| 28 | + | docker-compose-orderer-kafka.yml | true | 20 | 2 | 10 | 5 | |
| 29 | + | docker-compose-orderer-kafka.yml | true | 40 | 4 | 10 | 5 | |
| 30 | + | docker-compose-orderer-kafka.yml | true | 60 | 6 | 10 | 5 | |
36 | 31 |
|
37 | 32 | # @doNotDecompose
|
38 |
| - Scenario Outline: Basic seek orderer function (Utilizing properties for atomic broadcast) |
| 33 | + Scenario Outline: Basic seek orderer function (Utilizing properties for atomic broadcast) |
39 | 34 |
|
40 |
| - Given we compose "<ComposeFile>" |
41 |
| - And I wait ".5" seconds |
42 |
| - And user "binhn" is an authorized user of the ordering service |
43 |
| - When user "binhn" broadcasts "<NumMsgsToBroadcast>" unique messages on "orderer0" |
44 |
| - And user "binhn" connects to deliver function on "orderer0" with Ack of "<SendAck>" and properties: |
| 35 | + Given we compose "<ComposeFile>" |
| 36 | + And I wait "<BootTime>" seconds |
| 37 | + And user "binhn" is an authorized user of the ordering service |
| 38 | + When user "binhn" broadcasts "<NumMsgsToBroadcast>" unique messages on "orderer0" |
| 39 | + And user "binhn" connects to deliver function on "orderer0" with Ack of "<SendAck>" and properties: |
45 | 40 | | Start | SpecifiedNumber | WindowSize |
|
46 | 41 | | SPECIFIED | 1 | 10 |
|
47 |
| - Then user "binhn" should get a delivery from "orderer0" of "<ExpectedBlocks>" blocks with "<NumMsgsToBroadcast>" messages within "<BatchTimeout>" seconds |
48 |
| - When user "binhn" seeks to block "1" on deliver function on "orderer0" |
49 |
| - Then user "binhn" should get a delivery from "orderer0" of "<ExpectedBlocks>" blocks with "<NumMsgsToBroadcast>" messages within "1" seconds |
50 |
| - |
| 42 | + Then user "binhn" should get a delivery from "orderer0" of "<ExpectedBlocks>" blocks with "<NumMsgsToBroadcast>" messages within "<BatchTimeout>" seconds |
| 43 | + When user "binhn" seeks to block "1" on deliver function on "orderer0" |
| 44 | + Then user "binhn" should get a delivery from "orderer0" of "<ExpectedBlocks>" blocks with "<NumMsgsToBroadcast>" messages within "1" seconds |
51 | 45 |
|
52 | 46 | Examples: Orderer Options
|
53 |
| - | ComposeFile | SendAck | NumMsgsToBroadcast | ExpectedBlocks | BatchTimeout | |
54 |
| - | docker-compose-orderer-solo.yml | true | 20 | 2 | 10 | |
55 |
| -# | docker-compose-orderer-solo.yml | true | 40 | 4 | 10 | |
56 |
| -# | docker-compose-orderer-solo.yml | true | 60 | 6 | 10 | |
| 47 | + | ComposeFile | SendAck | NumMsgsToBroadcast | ExpectedBlocks | BatchTimeout | BootTime | |
| 48 | + | docker-compose-orderer-solo.yml | true | 20 | 2 | 10 | .5 | |
| 49 | + | docker-compose-orderer-solo.yml | true | 40 | 4 | 10 | .5 | |
| 50 | + | docker-compose-orderer-solo.yml | true | 60 | 6 | 10 | .5 | |
| 51 | + | docker-compose-orderer-kafka.yml | true | 20 | 2 | 10 | 5 | |
| 52 | + | docker-compose-orderer-kafka.yml | true | 40 | 4 | 10 | 5 | |
| 53 | + | docker-compose-orderer-kafka.yml | true | 60 | 6 | 10 | 5 | |
57 | 54 |
|
58 | 55 |
|
59 | 56 | # @doNotDecompose
|
60 |
| - Scenario Outline: Basic orderer function varying ACK |
| 57 | + Scenario Outline: Basic orderer function varying ACK |
61 | 58 |
|
62 |
| - Given we compose "<ComposeFile>" |
63 |
| - And I wait ".5" seconds |
64 |
| - And user "binhn" is an authorized user of the ordering service |
65 |
| - When user "binhn" broadcasts "<NumMsgsToBroadcast>" unique messages on "orderer0" |
66 |
| - And user "binhn" connects to deliver function on "orderer0" with Ack of "<SendAck>" and properties: |
| 59 | + Given we compose "<ComposeFile>" |
| 60 | + And I wait "<BootTime>" seconds |
| 61 | + And user "binhn" is an authorized user of the ordering service |
| 62 | + When user "binhn" broadcasts "<NumMsgsToBroadcast>" unique messages on "orderer0" |
| 63 | + And user "binhn" connects to deliver function on "orderer0" with Ack of "<SendAck>" and properties: |
67 | 64 | | Start | SpecifiedNumber | WindowSize |
|
68 | 65 | | SPECIFIED | 1 | 1 |
|
69 |
| - Then user "binhn" should get a delivery from "orderer0" of "<ExpectedBlocks>" blocks with "<NumMsgsToBroadcast>" messages within "<BatchTimeout>" seconds |
70 |
| - |
| 66 | + Then user "binhn" should get a delivery from "orderer0" of "<ExpectedBlocks>" blocks with "<NumMsgsToBroadcast>" messages within "<BatchTimeout>" seconds |
71 | 67 |
|
72 | 68 | Examples: Orderer Options
|
73 |
| - | ComposeFile | SendAck | NumMsgsToBroadcast | ExpectedBlocks | BatchTimeout | |
74 |
| - | docker-compose-orderer-solo.yml | false | 20 | 1 | 10 | |
75 |
| - | docker-compose-orderer-solo.yml | true | 20 | 2 | 10 | |
| 69 | + | ComposeFile | SendAck | NumMsgsToBroadcast | ExpectedBlocks | BatchTimeout | BootTime | |
| 70 | + | docker-compose-orderer-solo.yml | false | 20 | 1 | 10 | .5 | |
| 71 | + | docker-compose-orderer-solo.yml | true | 20 | 2 | 10 | .5 | |
| 72 | + | docker-compose-orderer-kafka.yml | false | 20 | 1 | 10 | 5 | |
| 73 | + | docker-compose-orderer-kafka.yml | true | 20 | 2 | 10 | 5 | |
0 commit comments