#3 (Oct 4, 2018, 10:24:19 AM)

Started by user Alberto Codutti

• origin/release-1.0.x

• Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios
• Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account.Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account
• 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: DV1 Data view publish to CTRL_ACC_REPLY.Scenario: DV1 Data view publish to CTRL_ACC_REPLY
• 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.Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed
• Scenario: Send BIRTH message and then DC message while broker ip is NOT set.And Device birth message is sent
• Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios
• Scenario: Handling of a disconnect message from a non existing device.Scenario: Handling of a disconnect message from a non existing device
• Scenario: Birth and death message handling.Scenario: Birth and death message handling
• Scenario: Birth and missing event handling.Scenario: Birth and missing event handling
• Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios
• Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic.Given Mqtt Device is started
• Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic.Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic
• Scenario: B1 Broker publish to CTRL_ACC_REPLY.Given Mqtt Device is started
• 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.Given Mqtt Device is started
• Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY.Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY
• Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY.Given Mqtt Device is started
• Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY.Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY
• Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account.Given Mqtt Device is started
• Scenario: B5 Broker publish to CTRL_ACC is not allowed.Given Mqtt Device is started
• Scenario: B5 Broker publish to CTRL_ACC is not allowed.Scenario: B5 Broker publish to CTRL_ACC is not allowed
• Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed.Given Mqtt Device is started
• Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed.Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed
• Scenario: B7 Broker subscribe on CTRL_ACC is not allowed.Given Mqtt Device is started
• Scenario: B7 Broker subscribe on CTRL_ACC is not allowed.Scenario: B7 Broker subscribe on CTRL_ACC is not allowed
• Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI.Given Mqtt Device is started
• Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI.Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI
• Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed.Given Mqtt Device is started
• 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.Given Mqtt Device is started
• 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.Given Mqtt Device is started
• Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed.Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed
• Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI.Given Mqtt Device is started
• Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI.Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI
• Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed.Given Mqtt Device is started
• 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.Given Mqtt Device is started
• Scenario: D1 Device publish to CTRL_ACC_REPLY.Given Mqtt Device is started
• 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.Given Mqtt Device is started
• Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY.Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY
• Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY.Given Mqtt Device is started
• Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY.Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY
• Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account.Given Mqtt Device is started
• Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account.Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account
• Scenario: D5 Device subscribe - publish - admin on CTRL_ACC.Given Mqtt Device is started
• Scenario: D5 Device subscribe - publish - admin on CTRL_ACC.Scenario: D5 Device subscribe - publish - admin on CTRL_ACC
• Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI.Given Mqtt Device is started
• Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI.Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI
• Scenario: D7 Device publish to ACL_DATA_ACC is not allowed.Given Mqtt Device is started
• 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.Given Mqtt Device is started
• 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.Given Mqtt Device is started
• Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed.Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed
• Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI.Given Mqtt Device is started
• Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI.Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI
• Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed.Given Mqtt Device is started
• Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed
• Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Given Mqtt Device is started
• Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed
• Scenario: DV1 Data view publish to CTRL_ACC_REPLY.Given Mqtt Device is started
• Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY.Given Mqtt Device is started
• Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY.Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY
• Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY.Given Mqtt Device is started
• Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY.Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY
• Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account.Given Mqtt Device is started
• Scenario: DV5 Data view publish to CTRL_ACC is not allowed.Given Mqtt Device is started
• Scenario: DV5 Data view publish to CTRL_ACC is not allowed.Scenario: DV5 Data view publish to CTRL_ACC is not allowed
• Scenario: DV6 Data view create sub-topic on CTRL_ACC is not allowed.Given Mqtt Device is started
• Scenario: DV6 Data view create sub-topic on CTRL_ACC is not allowed.Scenario: DV6 Data view create sub-topic on CTRL_ACC is not allowed
• Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed.Given Mqtt Device is started
• Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI.Given Mqtt Device is started
• Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI.Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI
• Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed.Given Mqtt Device is started
• 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.Given Mqtt Device is started
• 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: DV11 Data view subscribe on ACL_DATA_ACC is allowed.Given Mqtt Device is started
• Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed.Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed
• Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed.Given Mqtt Device is started
• Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed.Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed
• Scenario: DV13 Data view create sub-topic on ACL_CTRL_ACC_CLI is not allowed.Given Mqtt Device is started
• Scenario: DV13 Data view create sub-topic on ACL_CTRL_ACC_CLI is not allowed.Scenario: DV13 Data view create sub-topic on ACL_CTRL_ACC_CLI is not allowed
• Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed.Given Mqtt Device is started
• 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.Given Mqtt Device is started
• 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.Scenario: Start broker for all scenarios
• Scenario: Send BIRTH message and then DC message while broker ip is NOT set.Scenario: Send BIRTH message and then DC message while broker ip is NOT set
• Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios
• Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios
• Scenario: Positive scenario without stealing link.And topic "$EDC/kapua-sys/client-1/MQTT/BIRTH" content "src/test/resources/mqtt/rpione3_MQTT_BIRTH.mqtt" is published by client named "client-1"
• Scenario: Positive scenario without stealing link.Scenario: Positive scenario without stealing link
• Scenario: Stealing link scenario.And topic "$EDC/kapua-sys/client-1/MQTT/BIRTH" content "src/test/resources/mqtt/rpione3_MQTT_BIRTH.mqtt" is published by client named "client-1"
• Scenario: Stealing link scenario.Scenario: Stealing link scenario
• Scenario: Negative scenario when client connects twice with same client id.And topic "$EDC/kapua-sys/client-1/MQTT/BIRTH" content "src/test/resources/mqtt/rpione3_MQTT_BIRTH.mqtt" is published by client named "client-1-1"
• Scenario: Negative scenario when client connects twice with same client id.Scenario: Negative scenario when client connects twice with same client id
• 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 event broker for all scenarios.Scenario: Start event broker for all scenarios
• Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios
• Scenario: Birth message handling from a new device.When I login as user with name "kapua-sys" and password "kapua-password"
• Scenario: Birth message handling from a new device.Scenario: Birth message handling from a new device
• Scenario: Birth message handling from an existing device.When I login as user with name "kapua-sys" and password "kapua-password"
• Scenario: Birth message handling from an existing device.Scenario: Birth message handling from an existing device
• Scenario: Handling of 2 birth messages.When I login as user with name "kapua-sys" and password "kapua-password"
• Scenario: Handling of 2 birth messages.Scenario: Handling of 2 birth messages
• Scenario: Handling of a disconnect message from a non existing device.When I login as user with name "kapua-sys" and password "kapua-password"
• Scenario: Birth and death message handling.When I login as user with name "kapua-sys" and password "kapua-password"
• Scenario: Birth and missing event handling.When I login as user with name "kapua-sys" and password "kapua-password"
• Scenario: Birth and applications event handling.When I login as user with name "kapua-sys" and password "kapua-password"
• Scenario: Birth and applications event handling.Scenario: Birth and applications event handling
• Scenario: Creating new device and tagging it with specific Tag.When I login as user with name "kapua-sys" and password "kapua-password"
• Scenario: Creating new device and tagging it with specific Tag.Scenario: Creating new device and tagging it with specific Tag
• Scenario: Creating new device, tagging it with specific Tag and then deleting this Tag.When I login as user with name "kapua-sys" and password "kapua-password"
• Scenario: Creating new device, tagging it with specific Tag and then deleting this Tag.Scenario: Creating new device, tagging it with specific Tag and then deleting this Tag