#508 (May 27, 2019, 8:40:01 AM)

1. Add Gitter chat room references (details / githubweb)
2. Fix for String Channel values not displayed correctly (#2602) (details / githubweb)

Started by an SCM change (71 times)

• origin/develop

• Scenario: Start broker for all scenarios.Given Start Broker
• Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios
• Scenario: Test LOOSE user coupling on single connection.And The connection status is "CONNECTED"
• Scenario: Test LOOSE user coupling on single connection.Scenario: Test LOOSE user coupling on single connection
• Scenario: New connection with reserved ID.And The connection status is "CONNECTED"
• Scenario: New connection with reserved ID.Scenario: New connection with reserved ID
• Scenario: Test STRICT user coupling on single connection.And The connection status is "CONNECTED"
• Scenario: Test STRICT user coupling on single connection.Scenario: Test STRICT user coupling on single connection
• Scenario: Test STRICT user coupling with user change allowed on single connection.And The connection status is "CONNECTED"
• Scenario: Test STRICT user coupling with user change allowed on single connection.Scenario: Test STRICT user coupling with user change allowed on single connection
• Scenario: Test LOOSE user coupling with 3 connections.And The connection status is "CONNECTED"
• Scenario: Test LOOSE user coupling with 3 connections.Scenario: Test LOOSE user coupling with 3 connections
• Scenario: Test STRICT user coupling with 3 connections and a reserved user.And The connection status is "CONNECTED"
• Scenario: Test STRICT user coupling with 3 connections and a reserved user.Scenario: Test STRICT user coupling with 3 connections and a reserved user
• Scenario: Extra long continuous test with multiple subscenarios with LOOSE default connection mode.And The connection status is "CONNECTED"
• Scenario: Extra long continuous test with multiple subscenarios with LOOSE default connection mode.Scenario: Extra long continuous test with multiple subscenarios with LOOSE default connection mode
• Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode.And The connection status is "CONNECTED"
• Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode.Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode
• Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode and no previously defined devices.Then I find 1 connection
• Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode and no previously defined devices.Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode and no previously defined devices
• Scenario: Start broker for all scenarios.Given Start Broker
• Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios
• Scenario: Start broker for all scenarios.Given Start Broker
• Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios
• Scenario: Start broker for all scenarios.Given Start Broker
• Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios
• Scenario: Start broker for all scenarios.Given Start Broker
• Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios
• Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed.Then Broker receives string "Hello broker" on topic "$EDC/acme/client-1/CONF-V1/REPLY"
• Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed.Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed
• Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY.Then Broker receives string "Hello broker" on topic "$EDC/acme/client-1/CONF-V1/REPLY/foo"
• Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY.Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY
• Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account.Then An exception was thrown
• Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account.Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account
• Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed.Then An exception was thrown
• Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed.Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed
• Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed.Then Broker receives string "Hello broker" on topic "$EDC/acme/foo/bar/NOTIFY/client-1"
• Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed
• Scenario: DM13 Data manage subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Then An exception was thrown
• Scenario: DM13 Data manage subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Scenario: DM13 Data manage subscribe on ACL_CTRL_ACC_NOTIFY is not allowed
• Scenario: Start broker for all scenarios.Given Start Broker
• Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios
• Scenario: B1 Broker publish to CTRL_ACC_REPLY.Then Broker receives string "Hello broker" on topic "$EDC/acme/client-1/CONF-V1/REPLY"
• Scenario: B1 Broker publish to CTRL_ACC_REPLY.Scenario: B1 Broker publish to CTRL_ACC_REPLY
• Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY.Then Broker receives string "Hello broker" on topic "$EDC/acme/client-1/CONF-V1/REPLY/foo"
• Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY.Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY
• Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account.Then An exception was thrown
• Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account.Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account
• Scenario: B7 Broker subscribe on CTRL_ACC is not allowed.Then An exception was thrown
• Scenario: B7 Broker subscribe on CTRL_ACC is not allowed.Scenario: B7 Broker subscribe on CTRL_ACC is not allowed
• Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed.Then Broker doesn't receive string "Hello broker" on topic "acme"
• Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed.Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed
• Scenario: B10 Broker create sub-topic on ACL_DATA_ACC is not allowed.Then Broker doesn't receive string "Hello broker" on topic "acme/foo"
• Scenario: B10 Broker create sub-topic on ACL_DATA_ACC is not allowed.Scenario: B10 Broker create sub-topic on ACL_DATA_ACC is not allowed
• Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed.Then An exception was thrown
• Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed.Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed
• Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed.Then Broker receives string "Hello broker" on topic "$EDC/acme/foo/bar/NOTIFY/client-1"
• Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed
• Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Then An exception was thrown
• Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed
• Scenario: D1 Device publish to CTRL_ACC_REPLY.Then Broker receives string "Hello broker" on topic "$EDC/acme/client-1/CONF-V1/REPLY"
• Scenario: D1 Device publish to CTRL_ACC_REPLY.Scenario: D1 Device publish to CTRL_ACC_REPLY
• Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY.Then Broker receives string "Hello broker" on topic "$EDC/acme/client-1/CONF-V1/REPLY/foo"
• Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY.Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY
• Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account.Then An exception was thrown
• Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account.Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account
• Scenario: D7 Device publish to ACL_DATA_ACC is not allowed.Then Broker doesn't receive string "Hello broker" on topic "acme"
• Scenario: D7 Device publish to ACL_DATA_ACC is not allowed.Scenario: D7 Device publish to ACL_DATA_ACC is not allowed
• Scenario: D8 Device create sub-topic on ACL_DATA_ACC is not allowed.Then Broker doesn't receive string "Hello broker" on topic "acme/foo"
• Scenario: D8 Device create sub-topic on ACL_DATA_ACC is not allowed.Scenario: D8 Device create sub-topic on ACL_DATA_ACC is not allowed
• Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed.Then An exception was thrown
• Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed.Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed
• Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed.Then Broker receives string "Hello broker" on topic "$EDC/acme/foo/bar/NOTIFY/client-1"
• Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed
• Scenario: DV1 Data view publish to CTRL_ACC_REPLY.Then Broker receives string "Hello broker" on topic "$EDC/acme/client-1/CONF-V1/REPLY"
• Scenario: DV1 Data view publish to CTRL_ACC_REPLY.Scenario: DV1 Data view publish to CTRL_ACC_REPLY
• Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY.Then Broker receives string "Hello broker" on topic "$EDC/acme/client-1/CONF-V1/REPLY/foo"
• Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY.Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY
• Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account.Then An exception was thrown
• Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account.Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account
• Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed.Then An exception was thrown
• Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed.Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed
• Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed.Then Broker doesn't receive string "Hello broker" on topic "acme"
• Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed.Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed
• Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed.Then Broker doesn't receive string "Hello broker" on topic "acme/foo"
• Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed.Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed
• Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed.Then Broker receives string "Hello broker" on topic "$EDC/acme/foo/bar/NOTIFY/client-1"
• Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed
• Scenario: DV17 Data view subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Then An exception was thrown
• Scenario: DV17 Data view subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Scenario: DV17 Data view subscribe on ACL_CTRL_ACC_NOTIFY is not allowed
• Scenario: Start broker for all scenarios.Given Start Broker
• Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios
• Scenario: Send BIRTH message and then DC message.And Bundles are requested
• Scenario: Send BIRTH message and then DC message.Scenario: Send BIRTH message and then DC message
• Scenario: Start broker for all scenarios.Given Start Broker
• Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios
• Scenario: Send BIRTH message and then DC message while broker ip is set by config file.Then Device is connected with "localhost" server ip
• Scenario: Send BIRTH message and then DC message while broker ip is set by config file.Scenario: Send BIRTH message and then DC message while broker ip is set by config file
• Scenario: Start broker for all scenarios.Given Start Broker
• Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios
• Scenario: Send BIRTH message and then DC message while broker ip is set by System.Then Device is connected with "localhost" server ip
• Scenario: Send BIRTH message and then DC message while broker ip is set by System.Scenario: Send BIRTH message and then DC message while broker ip is set by System
• Scenario: Start broker for all scenarios.Given Start Broker
• Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios
• Scenario: Start broker for all scenarios.Given Start Broker
• Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios
• Scenario: Stealing link scenario.And Client named "client-2" is not connected
• Scenario: Stealing link scenario.Scenario: Stealing link scenario
• Scenario: Start broker for all scenarios.Given Start Broker
• Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios
• Scenario: Connect to the system and publish some data.Then Device sim-1 for account kapua-sys is registered after 5 seconds
• Scenario: Connect to the system and publish some data.Scenario: Connect to the system and publish some data
• Scenario: Start broker for all scenarios.Given Start Broker
• Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios
• Scenario: Start broker for all scenarios.Given Start Broker
• Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios
• Scenario: Starting and stopping the simulator should create a device entry and properly set its status.Then Device sim-1 for account kapua-sys is registered after 5 seconds
• Scenario: Starting and stopping the simulator should create a device entry and properly set its status.Scenario: Starting and stopping the simulator should create a device entry and properly set its status
• Scenario: Installing a package.Then Device sim-1 for account kapua-sys is registered after 5 seconds
• Scenario: Installing a package.Scenario: Installing a package
• Scenario: Start broker for all scenarios.Given Start Broker
• Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios