#2 (Oct 4, 2018, 8:56:28 AM)

Started by user Alberto Codutti

• origin/release-1.0.x

• Scenario: Account with future expiration date.Scenario: Account with future expiration date
• Scenario: Account with future expiration date.Scenario: Account with future expiration date
• Scenario: Account with no expiration date.Scenario: Account with no expiration date
• Scenario: Account with no expiration date.Scenario: Account with no expiration date
• Scenario: Account past its expiration date.Scenario: Account past its expiration date
• Scenario: Account past its expiration date.Scenario: Account past its expiration date
• Scenario: Account exactly on its expiration date.Scenario: Account exactly on its expiration date
• Scenario: Account exactly on its expiration date.Scenario: Account exactly on its expiration date
• Scenario: Child account expires before parent.Scenario: Child account expires before parent
• Scenario: Child account expires before parent.Scenario: Child account expires before parent
• Scenario: Both the parent and child accounts have the same expiration date.Scenario: Both the parent and child accounts have the same expiration date
• Scenario: Both the parent and child accounts have the same expiration date.Scenario: Both the parent and child accounts have the same expiration date
• Scenario: Both the parent and child accounts do not expire.Scenario: Both the parent and child accounts do not expire
• Scenario: Both the parent and child accounts do not expire.Scenario: Both the parent and child accounts do not expire
• Scenario: Child account expires after parent.Scenario: Child account expires after parent
• Scenario: Child account expires after parent.Scenario: Child account expires after parent
• Scenario: Child account has null expiration date.Scenario: Child account has null expiration date
• Scenario: Child account has null expiration date.Scenario: Child account has null expiration date
• Scenario: Modify parent expiration so that it still expires after child.Scenario: Modify parent expiration so that it still expires after child
• Scenario: Modify parent expiration so that it still expires after child.Scenario: Modify parent expiration so that it still expires after child
• Scenario: Delete parent expiration.Scenario: Delete parent expiration
• Scenario: Delete parent expiration.Scenario: Delete parent expiration
• Scenario: Modify parent expiration to before child expiration.Scenario: Modify parent expiration to before child expiration
• Scenario: Modify parent expiration to before child expiration.Scenario: Modify parent expiration to before child expiration
• Scenario: Modify middle child expiration so that it still expires before parent.Scenario: Modify middle child expiration so that it still expires before parent
• Scenario: Modify middle child expiration so that it still expires before parent.Scenario: Modify middle child expiration so that it still expires before parent
• Scenario: Modify last child expiration so that it still expires before parent.Scenario: Modify last child expiration so that it still expires before parent
• Scenario: Modify last child expiration so that it still expires before parent.Scenario: Modify last child expiration so that it still expires before parent
• Scenario: Modify middle child expiration to outlive parent.Scenario: Modify middle child expiration to outlive parent
• Scenario: Modify middle child expiration to outlive parent.Scenario: Modify middle child expiration to outlive parent
• Scenario: Delete middle child expiration.Scenario: Delete middle child expiration
• Scenario: Delete middle child expiration.Scenario: Delete middle child expiration
• Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios
• Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios
• Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios
• 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: Start broker for all scenarios.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: Start broker for all scenarios
• Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios
• Scenario: Test LOOSE user coupling on single connection.Scenario: Test LOOSE user coupling on single connection
• Scenario: Test LOOSE user coupling on single connection.Scenario: Test LOOSE user coupling on single connection
• Scenario: Test LOOSE user coupling on single connection.Scenario: Test LOOSE user coupling on single connection
• Scenario: Test LOOSE user coupling on single connection.Scenario: Test LOOSE user coupling on single connection
• Scenario: New connection with reserved ID.Scenario: New connection with reserved ID
• Scenario: New connection with reserved ID.Scenario: New connection with reserved ID
• Scenario: New connection with reserved ID.Scenario: New connection with reserved ID
• Scenario: New connection with reserved ID.Scenario: New connection with reserved ID
• Scenario: Test STRICT user coupling on single connection.Scenario: Test STRICT user coupling on single connection
• Scenario: Test STRICT user coupling on single connection.Scenario: Test STRICT user coupling on single connection
• Scenario: Test STRICT user coupling on single connection.Scenario: Test STRICT user coupling on single connection
• 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.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 STRICT user coupling with user change allowed on single connection
• 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 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.Scenario: Test LOOSE user coupling with 3 connections
• Scenario: Test LOOSE user coupling with 3 connections.Scenario: Test LOOSE user coupling with 3 connections
• Scenario: Test LOOSE user coupling with 3 connections.Scenario: Test LOOSE user coupling with 3 connections
• 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.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: Test STRICT user coupling with 3 connections and a reserved user
• 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: 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.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 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 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 LOOSE 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
• 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.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
• 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: 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: 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: 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: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios
• Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios
• Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios
• Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios
• Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios
• Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios
• Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios
• Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios
• 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: Start broker for all scenarios.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: Start broker for all scenarios
• 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: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Delete items by the datastore ID.Scenario: Delete items by the datastore ID
• Scenario: Delete items by the datastore ID.Scenario: Delete items by the datastore ID
• Scenario: Delete items by the datastore ID.Scenario: Delete items by the datastore ID
• Scenario: Delete items by the datastore ID.Scenario: Delete items by the datastore ID
• Scenario: Delete items by the datastore ID.Scenario: Delete items by the datastore ID
• Scenario: Delete items based on query results.Scenario: Delete items based on query results
• Scenario: Delete items based on query results.Scenario: Delete items based on query results
• Scenario: Delete items based on query results.Scenario: Delete items based on query results
• Scenario: Delete items based on query results.Scenario: Delete items based on query results
• Scenario: Delete items based on query results.Scenario: Delete items based on query results
• Scenario: Check the mapping for message semantic topics.Scenario: Check the mapping for message semantic topics
• Scenario: Check the mapping for message semantic topics.Scenario: Check the mapping for message semantic topics
• Scenario: Check the mapping for message semantic topics.Scenario: Check the mapping for message semantic topics
• Scenario: Check the mapping for message semantic topics.Scenario: Check the mapping for message semantic topics
• Scenario: Check the mapping for message semantic topics.Scenario: Check the mapping for message semantic topics
• Scenario: Query before schema search.Scenario: Query before schema search
• Scenario: Query before schema search.Scenario: Query before schema search
• Scenario: Query before schema search.Scenario: Query before schema search
• Scenario: Query before schema search.Scenario: Query before schema search
• Scenario: Query before schema search.Scenario: Query before schema search
• Scenario: Check the database cache coherency.Scenario: Check the database cache coherency
• Scenario: Check the database cache coherency.Scenario: Check the database cache coherency
• Scenario: Check the database cache coherency.Scenario: Check the database cache coherency
• Scenario: Check the database cache coherency.Scenario: Check the database cache coherency
• Scenario: Check the database cache coherency.Scenario: Check the database cache coherency
• Scenario: Check the message store.Scenario: Check the message store
• Scenario: Check the message store.Scenario: Check the message store
• Scenario: Check the message store.Scenario: Check the message store
• Scenario: Check the message store.Scenario: Check the message store
• Scenario: Check the message store.Scenario: Check the message store
• Scenario: Query based on message ordering.Scenario: Query based on message ordering
• Scenario: Query based on message ordering.Scenario: Query based on message ordering
• Scenario: Query based on message ordering.Scenario: Query based on message ordering
• Scenario: Query based on message ordering.Scenario: Query based on message ordering
• Scenario: Query based on message ordering.Scenario: Query based on message ordering
• Scenario: Test the message store with timestamp indexing.Scenario: Test the message store with timestamp indexing
• Scenario: Test the message store with timestamp indexing.Scenario: Test the message store with timestamp indexing
• Scenario: Test the message store with timestamp indexing.Scenario: Test the message store with timestamp indexing
• Scenario: Test the message store with timestamp indexing.Scenario: Test the message store with timestamp indexing
• Scenario: Test the message store with timestamp indexing.Scenario: Test the message store with timestamp indexing
• Scenario: Test the message store with server timestamp indexing.Scenario: Test the message store with server timestamp indexing
• Scenario: Test the message store with server timestamp indexing.Scenario: Test the message store with server timestamp indexing
• Scenario: Test the message store with server timestamp indexing.Scenario: Test the message store with server timestamp indexing
• Scenario: Test the message store with server timestamp indexing.Scenario: Test the message store with server timestamp indexing
• Scenario: Test the message store with server timestamp indexing.Scenario: Test the message store with server timestamp indexing
• Scenario: ChannelInfo client ID based on the account id.Scenario: ChannelInfo client ID based on the account id
• Scenario: ChannelInfo client ID based on the account id.Scenario: ChannelInfo client ID based on the account id
• Scenario: ChannelInfo client ID based on the account id.Scenario: ChannelInfo client ID based on the account id
• Scenario: ChannelInfo client ID based on the account id.Scenario: ChannelInfo client ID based on the account id
• Scenario: ChannelInfo client ID based on the account id.Scenario: ChannelInfo client ID based on the account id
• Scenario: ChannelInfo last published date.Scenario: ChannelInfo last published date
• Scenario: ChannelInfo last published date.Scenario: ChannelInfo last published date
• Scenario: ChannelInfo last published date.Scenario: ChannelInfo last published date
• Scenario: ChannelInfo last published date.Scenario: ChannelInfo last published date
• Scenario: ChannelInfo last published date.Scenario: ChannelInfo last published date
• Scenario: ChannelInfo topic data based on the account id.Scenario: ChannelInfo topic data based on the account id
• Scenario: ChannelInfo topic data based on the account id.Scenario: ChannelInfo topic data based on the account id
• Scenario: ChannelInfo topic data based on the account id.Scenario: ChannelInfo topic data based on the account id
• Scenario: ChannelInfo topic data based on the account id.Scenario: ChannelInfo topic data based on the account id
• Scenario: ChannelInfo topic data based on the account id.Scenario: ChannelInfo topic data based on the account id
• Scenario: ChannelInfo client ID and topic data based on the client id.Scenario: ChannelInfo client ID and topic data based on the client id
• Scenario: ChannelInfo client ID and topic data based on the client id.Scenario: ChannelInfo client ID and topic data based on the client id
• Scenario: ChannelInfo client ID and topic data based on the client id.Scenario: ChannelInfo client ID and topic data based on the client id
• Scenario: ChannelInfo client ID and topic data based on the client id.Scenario: ChannelInfo client ID and topic data based on the client id
• Scenario: ChannelInfo client ID and topic data based on the client id.Scenario: ChannelInfo client ID and topic data based on the client id
• Scenario: Account wide metrics check.Scenario: Account wide metrics check
• Scenario: Account wide metrics check.Scenario: Account wide metrics check
• Scenario: Account wide metrics check.Scenario: Account wide metrics check
• Scenario: Account wide metrics check.Scenario: Account wide metrics check
• Scenario: Account wide metrics check.Scenario: Account wide metrics check
• Scenario: MetricsInfo last published date.Scenario: MetricsInfo last published date
• Scenario: MetricsInfo last published date.Scenario: MetricsInfo last published date
• Scenario: MetricsInfo last published date.Scenario: MetricsInfo last published date
• Scenario: MetricsInfo last published date.Scenario: MetricsInfo last published date
• Scenario: MetricsInfo last published date.Scenario: MetricsInfo last published date
• Scenario: MetricsInfo client ID and topic data based on the client id.Scenario: MetricsInfo client ID and topic data based on the client id
• Scenario: MetricsInfo client ID and topic data based on the client id.Scenario: MetricsInfo client ID and topic data based on the client id
• Scenario: MetricsInfo client ID and topic data based on the client id.Scenario: MetricsInfo client ID and topic data based on the client id
• Scenario: MetricsInfo client ID and topic data based on the client id.Scenario: MetricsInfo client ID and topic data based on the client id
• Scenario: MetricsInfo client ID and topic data based on the client id.Scenario: MetricsInfo client ID and topic data based on the client id
• Scenario: Query based on metrics ordering.Scenario: Query based on metrics ordering
• Scenario: Query based on metrics ordering.Scenario: Query based on metrics ordering
• Scenario: Query based on metrics ordering.Scenario: Query based on metrics ordering
• Scenario: Query based on metrics ordering.Scenario: Query based on metrics ordering
• Scenario: Query based on metrics ordering.Scenario: Query based on metrics ordering
• Scenario: Account based ClientInfo data check.Scenario: Account based ClientInfo data check
• Scenario: Account based ClientInfo data check.Scenario: Account based ClientInfo data check
• Scenario: Account based ClientInfo data check.Scenario: Account based ClientInfo data check
• Scenario: Account based ClientInfo data check.Scenario: Account based ClientInfo data check
• Scenario: Account based ClientInfo data check.Scenario: Account based ClientInfo data check
• Scenario: Captured date based ClientInfo data check.Scenario: Captured date based ClientInfo data check
• Scenario: Captured date based ClientInfo data check.Scenario: Captured date based ClientInfo data check
• Scenario: Captured date based ClientInfo data check.Scenario: Captured date based ClientInfo data check
• Scenario: Captured date based ClientInfo data check.Scenario: Captured date based ClientInfo data check
• Scenario: Captured date based ClientInfo data check.Scenario: Captured date based ClientInfo data check
• Scenario: Client Id based ClientInfo data check.Scenario: Client Id based ClientInfo data check
• Scenario: Client Id based ClientInfo data check.Scenario: Client Id based ClientInfo data check
• Scenario: Client Id based ClientInfo data check.Scenario: Client Id based ClientInfo data check
• Scenario: Client Id based ClientInfo data check.Scenario: Client Id based ClientInfo data check
• Scenario: Client Id based ClientInfo data check.Scenario: Client Id based ClientInfo data check
• Scenario: Channel info queries based on datastore channel filters.Scenario: Channel info queries based on datastore channel filters
• Scenario: Channel info queries based on datastore channel filters.Scenario: Channel info queries based on datastore channel filters
• Scenario: Channel info queries based on datastore channel filters.Scenario: Channel info queries based on datastore channel filters
• Scenario: Channel info queries based on datastore channel filters.Scenario: Channel info queries based on datastore channel filters
• Scenario: Channel info queries based on datastore channel filters.Scenario: Channel info queries based on datastore channel filters
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios
• Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios
• Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios
• Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios
• Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios
• Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios
• Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios
• Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios
• Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios
• 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: Start broker for all scenarios.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: Start broker for all scenarios
• 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: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios
• Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios
• Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios
• Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios
• Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios
• 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: Start broker for all scenarios.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: Start broker for all scenarios
• Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Simple positive scenario for creating default - weekly index.Scenario: Simple positive scenario for creating default - weekly index
• Scenario: Simple positive scenario for creating default - weekly index.Scenario: Simple positive scenario for creating default - weekly index
• Scenario: Simple positive scenario for creating default - weekly index.Scenario: Simple positive scenario for creating default - weekly index
• Scenario: Simple positive scenario for creating default - weekly index.Scenario: Simple positive scenario for creating default - weekly index
• Scenario: Simple positive scenario for creating default - weekly index.Scenario: Simple positive scenario for creating default - weekly index
• Scenario: Creating two indexes with weekly index.Scenario: Creating two indexes with weekly index
• Scenario: Creating two indexes with weekly index.Scenario: Creating two indexes with weekly index
• Scenario: Creating two indexes with weekly index.Scenario: Creating two indexes with weekly index
• Scenario: Creating two indexes with weekly index.Scenario: Creating two indexes with weekly index
• Scenario: Creating two indexes with weekly index.Scenario: Creating two indexes with weekly index
• Scenario: Creating index with regular user.Scenario: Creating index with regular user
• Scenario: Creating index with regular user.Scenario: Creating index with regular user
• Scenario: Creating index with regular user.Scenario: Creating index with regular user
• Scenario: Creating index with regular user.Scenario: Creating index with regular user
• Scenario: Creating index with regular user.Scenario: Creating index with regular user
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios
• Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios
• Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios
• Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios
• Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios
• Scenario: Check the database cache coherency.Scenario: Check the database cache coherency
• Scenario: Check the database cache coherency.Scenario: Check the database cache coherency
• Scenario: Check the database cache coherency.Scenario: Check the database cache coherency
• Scenario: Check the database cache coherency.Scenario: Check the database cache coherency
• Scenario: Check the database cache coherency.Scenario: Check the database cache coherency
• Scenario: Captured date based ClientInfo data check.Scenario: Captured date based ClientInfo data check
• Scenario: Captured date based ClientInfo data check.Scenario: Captured date based ClientInfo data check
• Scenario: Captured date based ClientInfo data check.Scenario: Captured date based ClientInfo data check
• Scenario: Captured date based ClientInfo data check.Scenario: Captured date based ClientInfo data check
• Scenario: Captured date based ClientInfo data check.Scenario: Captured date based ClientInfo data check
• 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: 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: 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: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios
• Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios
• Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios
• Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios
• Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios
• Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore 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: B4 Broker subscribe on CTRL_ACC_REPLY of another account.Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account
• 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: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.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: 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: DV1 Data view publish to CTRL_ACC_REPLY.Scenario: DV1 Data view publish to CTRL_ACC_REPLY
• 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: DV4 Data view subscribe on CTRL_ACC_REPLY of another account.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: 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: DV7 Data view subscribe on CTRL_ACC is not allowed.Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed
• Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed.Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios
• Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios
• Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios
• 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: 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: 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: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop datastore after all scenario.Scenario: Stop datastore after all scenario
• Scenario: Stop datastore after all scenario.Scenario: Stop datastore after all scenario
• Scenario: Stop datastore after all scenario.Scenario: Stop datastore after all scenario
• Scenario: Stop event broker after all scenarios.Scenario: Stop event broker after all scenarios
• Scenario: Stop event broker after all scenarios.Scenario: Stop event broker after all scenarios
• Scenario: Stop event broker after all scenarios.Scenario: Stop event broker after all scenarios
• Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios
• Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios
• Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after 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: Handling of a disconnect message from a non existing device.Scenario: Handling of a disconnect message from a non existing device
• 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 death message handling.Scenario: Birth and death message handling
• 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: Birth and missing event handling.Scenario: Birth and missing event handling
• Scenario: Birth and missing event handling.Scenario: Birth and missing event handling
• Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios
• 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: Start broker for all scenarios.Scenario: Start broker for all scenarios
• Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Creating tag.Scenario: Creating tag
• Scenario: Creating tag.Scenario: Creating tag
• Scenario: Deleting tag.Scenario: Deleting tag
• Scenario: Deleting tag.Scenario: Deleting tag
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios
• Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: If user credential is in state enabled, user can login.Scenario: If user credential is in state enabled, user can login
• Scenario: If user credential is in state enabled, user can login.Scenario: If user credential is in state enabled, user can login
• Scenario: If user credential is in state disabled, user can not login.Scenario: If user credential is in state disabled, user can not login
• Scenario: If user credential is in state disabled, user can not login.Scenario: If user credential is in state disabled, user can not login
• Scenario: If user credential expiration date is before today, user can not login.Scenario: If user credential expiration date is before today, user can not login
• Scenario: If user credential expiration date is before today, user can not login.Scenario: If user credential expiration date is before today, user can not login
• Scenario: If user credential expiration date is today, user can not login it is day inclusive.Scenario: If user credential expiration date is today, user can not login it is day inclusive
• Scenario: If user credential expiration date is today, user can not login it is day inclusive.Scenario: If user credential expiration date is today, user can not login it is day inclusive
• Scenario: If user credential expiration date is tomorrow, user can login.Scenario: If user credential expiration date is tomorrow, user can login
• Scenario: If user credential expiration date is tomorrow, user can login.Scenario: If user credential expiration date is tomorrow, user can login
• Scenario: If user expiration date is before today, user can not login.Scenario: If user expiration date is before today, user can not login
• Scenario: If user expiration date is before today, user can not login.Scenario: If user expiration date is before today, user can not login
• Scenario: If user expiration date is today, user can not login because expiration date was reached.Scenario: If user expiration date is today, user can not login because expiration date was reached
• Scenario: If user expiration date is today, user can not login because expiration date was reached.Scenario: If user expiration date is today, user can not login because expiration date was reached
• Scenario: If user expiration date is tomorrow, user can login.Scenario: If user expiration date is tomorrow, user can login
• Scenario: If user expiration date is tomorrow, user can login.Scenario: If user expiration date is tomorrow, user can login
• Scenario: User locking itself out by using out login attempts.Scenario: User locking itself out by using out login attempts
• Scenario: User locking itself out by using out login attempts.Scenario: User locking itself out by using out login attempts
• Scenario: User not locking itself out by using less than max failed login attempts.Scenario: User not locking itself out by using less than max failed login attempts
• Scenario: User not locking itself out by using less than max failed login attempts.Scenario: User not locking itself out by using less than max failed login attempts
• Scenario: User locking itself out with failed attempts and waiting to unlock.Scenario: User locking itself out with failed attempts and waiting to unlock
• Scenario: User locking itself out with failed attempts and waiting to unlock.Scenario: User locking itself out with failed attempts and waiting to unlock
• Scenario: User locking itself out with failed attempts and not waiting to unlock.Scenario: User locking itself out with failed attempts and not waiting to unlock
• Scenario: User locking itself out with failed attempts and not waiting to unlock.Scenario: User locking itself out with failed attempts and not waiting to unlock
• Scenario: User login with wrong pass, but with enough time between login failures.Scenario: User login with wrong pass, but with enough time between login failures
• Scenario: User login with wrong pass, but with enough time between login failures.Scenario: User login with wrong pass, but with enough time between login failures
• Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios
• Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios
• Scenario: To be defined.Scenario: To be defined
• Scenario: To be defined.Scenario: To be defined
• Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios
• Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios
• Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios
• Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios
• Scenario: Deleting user in account that is lower in hierarchy.Scenario: Deleting user in account that is lower in hierarchy
• Scenario: Deleting user in account that is lower in hierarchy.Scenario: Deleting user in account that is lower in hierarchy
• Scenario: Deleting user in account that is higher in hierarchy.Scenario: Deleting user in account that is higher in hierarchy
• Scenario: Deleting user in account that is higher in hierarchy.Scenario: Deleting user in account that is higher in hierarchy
• Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios
• Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Create index with specific prefix.Scenario: Create index with specific prefix
• Scenario: Create index with specific prefix.Scenario: Create index with specific prefix
• Scenario: Create index with specific prefix.Scenario: Create index with specific prefix
• Scenario: Create index with specific prefix.Scenario: Create index with specific prefix
• Scenario: Create index with specific prefix.Scenario: Create index with specific prefix
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios
• Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios
• Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios
• Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios
• Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios
• Scenario: Simple positive scenario for creating daily index.Scenario: Simple positive scenario for creating daily index
• Scenario: Simple positive scenario for creating daily index.Scenario: Simple positive scenario for creating daily index
• Scenario: Simple positive scenario for creating daily index.Scenario: Simple positive scenario for creating daily index
• Scenario: Simple positive scenario for creating daily index.Scenario: Simple positive scenario for creating daily index
• Scenario: Simple positive scenario for creating daily index.Scenario: Simple positive scenario for creating daily index
• Scenario: Simple positive scenario for creating hourly index.Scenario: Simple positive scenario for creating hourly index
• Scenario: Simple positive scenario for creating hourly index.Scenario: Simple positive scenario for creating hourly index
• Scenario: Simple positive scenario for creating hourly index.Scenario: Simple positive scenario for creating hourly index
• Scenario: Simple positive scenario for creating hourly index.Scenario: Simple positive scenario for creating hourly index
• Scenario: Simple positive scenario for creating hourly index.Scenario: Simple positive scenario for creating hourly index
• Scenario: Creating two indexes with daily index.Scenario: Creating two indexes with daily index
• Scenario: Creating two indexes with daily index.Scenario: Creating two indexes with daily index
• Scenario: Creating two indexes with daily index.Scenario: Creating two indexes with daily index
• Scenario: Creating two indexes with daily index.Scenario: Creating two indexes with daily index
• Scenario: Creating two indexes with daily index.Scenario: Creating two indexes with daily index
• Scenario: Creating two indexes with hourly index.Scenario: Creating two indexes with hourly index
• Scenario: Creating two indexes with hourly index.Scenario: Creating two indexes with hourly index
• Scenario: Creating two indexes with hourly index.Scenario: Creating two indexes with hourly index
• Scenario: Creating two indexes with hourly index.Scenario: Creating two indexes with hourly index
• Scenario: Creating two indexes with hourly index.Scenario: Creating two indexes with hourly index
• Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios
• Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios
• Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios
• Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios
• 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: Start broker for all scenarios.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: Start broker for all scenarios
• 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: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Delete items by the datastore ID.Scenario: Delete items by the datastore ID
• Scenario: Delete items by the datastore ID.Scenario: Delete items by the datastore ID
• Scenario: Delete items by the datastore ID.Scenario: Delete items by the datastore ID
• Scenario: Delete items by the datastore ID.Scenario: Delete items by the datastore ID
• Scenario: Delete items by the datastore ID.Scenario: Delete items by the datastore ID
• Scenario: Delete items based on query results.Scenario: Delete items based on query results
• Scenario: Delete items based on query results.Scenario: Delete items based on query results
• Scenario: Delete items based on query results.Scenario: Delete items based on query results
• Scenario: Delete items based on query results.Scenario: Delete items based on query results
• Scenario: Delete items based on query results.Scenario: Delete items based on query results
• Scenario: Check the mapping for message semantic topics.Scenario: Check the mapping for message semantic topics
• Scenario: Check the mapping for message semantic topics.Scenario: Check the mapping for message semantic topics
• Scenario: Check the mapping for message semantic topics.Scenario: Check the mapping for message semantic topics
• Scenario: Check the mapping for message semantic topics.Scenario: Check the mapping for message semantic topics
• Scenario: Check the mapping for message semantic topics.Scenario: Check the mapping for message semantic topics
• Scenario: Query before schema search.Scenario: Query before schema search
• Scenario: Query before schema search.Scenario: Query before schema search
• Scenario: Query before schema search.Scenario: Query before schema search
• Scenario: Query before schema search.Scenario: Query before schema search
• Scenario: Query before schema search.Scenario: Query before schema search
• Scenario: Check the message store.Scenario: Check the message store
• Scenario: Check the message store.Scenario: Check the message store
• Scenario: Check the message store.Scenario: Check the message store
• Scenario: Check the message store.Scenario: Check the message store
• Scenario: Check the message store.Scenario: Check the message store
• Scenario: Query based on message ordering.Scenario: Query based on message ordering
• Scenario: Query based on message ordering.Scenario: Query based on message ordering
• Scenario: Query based on message ordering.Scenario: Query based on message ordering
• Scenario: Query based on message ordering.Scenario: Query based on message ordering
• Scenario: Query based on message ordering.Scenario: Query based on message ordering
• Scenario: Test the message store with timestamp indexing.Scenario: Test the message store with timestamp indexing
• Scenario: Test the message store with timestamp indexing.Scenario: Test the message store with timestamp indexing
• Scenario: Test the message store with timestamp indexing.Scenario: Test the message store with timestamp indexing
• Scenario: Test the message store with timestamp indexing.Scenario: Test the message store with timestamp indexing
• Scenario: Test the message store with timestamp indexing.Scenario: Test the message store with timestamp indexing
• Scenario: Test the message store with server timestamp indexing.Scenario: Test the message store with server timestamp indexing
• Scenario: Test the message store with server timestamp indexing.Scenario: Test the message store with server timestamp indexing
• Scenario: Test the message store with server timestamp indexing.Scenario: Test the message store with server timestamp indexing
• Scenario: Test the message store with server timestamp indexing.Scenario: Test the message store with server timestamp indexing
• Scenario: Test the message store with server timestamp indexing.Scenario: Test the message store with server timestamp indexing
• Scenario: ChannelInfo client ID based on the account id.Scenario: ChannelInfo client ID based on the account id
• Scenario: ChannelInfo client ID based on the account id.Scenario: ChannelInfo client ID based on the account id
• Scenario: ChannelInfo client ID based on the account id.Scenario: ChannelInfo client ID based on the account id
• Scenario: ChannelInfo client ID based on the account id.Scenario: ChannelInfo client ID based on the account id
• Scenario: ChannelInfo client ID based on the account id.Scenario: ChannelInfo client ID based on the account id
• Scenario: ChannelInfo last published date.Scenario: ChannelInfo last published date
• Scenario: ChannelInfo last published date.Scenario: ChannelInfo last published date
• Scenario: ChannelInfo last published date.Scenario: ChannelInfo last published date
• Scenario: ChannelInfo last published date.Scenario: ChannelInfo last published date
• Scenario: ChannelInfo last published date.Scenario: ChannelInfo last published date
• Scenario: ChannelInfo topic data based on the account id.Scenario: ChannelInfo topic data based on the account id
• Scenario: ChannelInfo topic data based on the account id.Scenario: ChannelInfo topic data based on the account id
• Scenario: ChannelInfo topic data based on the account id.Scenario: ChannelInfo topic data based on the account id
• Scenario: ChannelInfo topic data based on the account id.Scenario: ChannelInfo topic data based on the account id
• Scenario: ChannelInfo topic data based on the account id.Scenario: ChannelInfo topic data based on the account id
• Scenario: ChannelInfo client ID and topic data based on the client id.Scenario: ChannelInfo client ID and topic data based on the client id
• Scenario: ChannelInfo client ID and topic data based on the client id.Scenario: ChannelInfo client ID and topic data based on the client id
• Scenario: ChannelInfo client ID and topic data based on the client id.Scenario: ChannelInfo client ID and topic data based on the client id
• Scenario: ChannelInfo client ID and topic data based on the client id.Scenario: ChannelInfo client ID and topic data based on the client id
• Scenario: ChannelInfo client ID and topic data based on the client id.Scenario: ChannelInfo client ID and topic data based on the client id
• Scenario: Account wide metrics check.Scenario: Account wide metrics check
• Scenario: Account wide metrics check.Scenario: Account wide metrics check
• Scenario: Account wide metrics check.Scenario: Account wide metrics check
• Scenario: Account wide metrics check.Scenario: Account wide metrics check
• Scenario: Account wide metrics check.Scenario: Account wide metrics check
• Scenario: MetricsInfo last published date.Scenario: MetricsInfo last published date
• Scenario: MetricsInfo last published date.Scenario: MetricsInfo last published date
• Scenario: MetricsInfo last published date.Scenario: MetricsInfo last published date
• Scenario: MetricsInfo last published date.Scenario: MetricsInfo last published date
• Scenario: MetricsInfo last published date.Scenario: MetricsInfo last published date
• Scenario: MetricsInfo client ID and topic data based on the client id.Scenario: MetricsInfo client ID and topic data based on the client id
• Scenario: MetricsInfo client ID and topic data based on the client id.Scenario: MetricsInfo client ID and topic data based on the client id
• Scenario: MetricsInfo client ID and topic data based on the client id.Scenario: MetricsInfo client ID and topic data based on the client id
• Scenario: MetricsInfo client ID and topic data based on the client id.Scenario: MetricsInfo client ID and topic data based on the client id
• Scenario: MetricsInfo client ID and topic data based on the client id.Scenario: MetricsInfo client ID and topic data based on the client id
• Scenario: Query based on metrics ordering.Scenario: Query based on metrics ordering
• Scenario: Query based on metrics ordering.Scenario: Query based on metrics ordering
• Scenario: Query based on metrics ordering.Scenario: Query based on metrics ordering
• Scenario: Query based on metrics ordering.Scenario: Query based on metrics ordering
• Scenario: Query based on metrics ordering.Scenario: Query based on metrics ordering
• Scenario: Account based ClientInfo data check.Scenario: Account based ClientInfo data check
• Scenario: Account based ClientInfo data check.Scenario: Account based ClientInfo data check
• Scenario: Account based ClientInfo data check.Scenario: Account based ClientInfo data check
• Scenario: Account based ClientInfo data check.Scenario: Account based ClientInfo data check
• Scenario: Account based ClientInfo data check.Scenario: Account based ClientInfo data check
• Scenario: Client Id based ClientInfo data check.Scenario: Client Id based ClientInfo data check
• Scenario: Client Id based ClientInfo data check.Scenario: Client Id based ClientInfo data check
• Scenario: Client Id based ClientInfo data check.Scenario: Client Id based ClientInfo data check
• Scenario: Client Id based ClientInfo data check.Scenario: Client Id based ClientInfo data check
• Scenario: Client Id based ClientInfo data check.Scenario: Client Id based ClientInfo data check
• Scenario: Channel info queries based on datastore channel filters.Scenario: Channel info queries based on datastore channel filters
• Scenario: Channel info queries based on datastore channel filters.Scenario: Channel info queries based on datastore channel filters
• Scenario: Channel info queries based on datastore channel filters.Scenario: Channel info queries based on datastore channel filters
• Scenario: Channel info queries based on datastore channel filters.Scenario: Channel info queries based on datastore channel filters
• Scenario: Channel info queries based on datastore channel filters.Scenario: Channel info queries based on datastore channel filters
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios
• Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios
• Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios
• Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios
• Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios
• Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios
• Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios
• 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: Start broker for all scenarios.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: Start broker for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed.Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed
• Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed.Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed
• 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.Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY
• Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY.Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY
• Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY.Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY
• Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY.Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY
• Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY.Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY
• Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY.Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY
• 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: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account.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: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account
• Scenario: DM5 Data manage publish to CTRL_ACC is not allowed.Scenario: DM5 Data manage publish to CTRL_ACC is not allowed
• Scenario: DM5 Data manage publish to CTRL_ACC is not allowed.Scenario: DM5 Data manage publish to CTRL_ACC is not allowed
• Scenario: DM5 Data manage publish to CTRL_ACC is not allowed.Scenario: DM5 Data manage publish to CTRL_ACC is not allowed
• Scenario: DM6 Data manage create sub-topic on CTRL_ACC is not allowed.Scenario: DM6 Data manage create sub-topic on CTRL_ACC is not allowed
• Scenario: DM6 Data manage create sub-topic on CTRL_ACC is not allowed.Scenario: DM6 Data manage create sub-topic on CTRL_ACC is not allowed
• Scenario: DM6 Data manage create sub-topic on CTRL_ACC is not allowed.Scenario: DM6 Data manage create sub-topic on CTRL_ACC is not allowed
• Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed.Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed
• Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed.Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed
• Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed.Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed
• Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI.Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI
• Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI.Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI
• Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI.Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI
• Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC.Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC
• Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC.Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC
• Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC.Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC
• Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI.Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI
• Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI.Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI
• Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI.Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI
• 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: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed.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: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed
• 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: Start broker for all scenarios.Scenario: Start broker for all scenarios
• Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios
• 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: A1 User with admin rights publishes arbitrary message to arbitrary topic.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: A1 User with admin rights publishes arbitrary message to arbitrary topic
• Scenario: B1 Broker publish to CTRL_ACC_REPLY.Scenario: B1 Broker publish to CTRL_ACC_REPLY
• Scenario: B1 Broker publish to CTRL_ACC_REPLY.Scenario: B1 Broker publish to CTRL_ACC_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.Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY
• Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY.Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY
• 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.Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY
• Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY.Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY
• Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY.Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY
• Scenario: B5 Broker publish to CTRL_ACC is not allowed.Scenario: B5 Broker publish to CTRL_ACC is not allowed
• Scenario: B5 Broker publish to CTRL_ACC is not allowed.Scenario: B5 Broker publish to CTRL_ACC is not allowed
• 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.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: B6 Broker create sub-topic on CTRL_ACC is not allowed
• 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.Scenario: B7 Broker subscribe on CTRL_ACC is not allowed
• Scenario: B7 Broker subscribe on CTRL_ACC is not allowed.Scenario: B7 Broker subscribe on CTRL_ACC is not allowed
• 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.Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI
• Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI.Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI
• 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.Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed
• Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed.Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed
• 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.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: 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: B10 Broker create sub-topic on ACL_DATA_ACC is not allowed
• Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed.Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed
• Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed.Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed
• 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.Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI
• Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI.Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI
• 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.Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed
• Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed
• Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed
• Scenario: D1 Device publish to CTRL_ACC_REPLY.Scenario: D1 Device publish to CTRL_ACC_REPLY
• Scenario: D1 Device publish to CTRL_ACC_REPLY.Scenario: D1 Device publish to CTRL_ACC_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.Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY
• Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY.Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY
• 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.Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY
• Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY.Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY
• 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.Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account
• Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account.Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account
• 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.Scenario: D5 Device subscribe - publish - admin on CTRL_ACC
• Scenario: D5 Device subscribe - publish - admin on CTRL_ACC.Scenario: D5 Device subscribe - publish - admin on CTRL_ACC
• 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.Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI
• Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI.Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI
• 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.Scenario: D7 Device publish to ACL_DATA_ACC is not allowed
• Scenario: D7 Device publish to ACL_DATA_ACC is not allowed.Scenario: D7 Device publish to ACL_DATA_ACC is not allowed
• 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.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: 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: D8 Device create sub-topic on ACL_DATA_ACC is not allowed
• Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed.Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed
• Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed.Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed
• 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.Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI
• Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI.Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI
• 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.Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed
• Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed
• 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.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: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed
• 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: DV2 Data view create sub-topic on CTRL_ACC_REPLY.Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY
• Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY.Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY
• 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.Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY
• Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY.Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY
• Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY.Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY
• Scenario: DV5 Data view publish to CTRL_ACC is not allowed.Scenario: DV5 Data view publish to CTRL_ACC is not allowed
• Scenario: DV5 Data view publish to CTRL_ACC is not allowed.Scenario: DV5 Data view publish to CTRL_ACC is not allowed
• 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.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: 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: DV6 Data view create sub-topic on CTRL_ACC is not allowed
• Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI.Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI
• Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI.Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI
• 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.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: DV9 Data view publish to ACL_DATA_ACC is not allowed
• 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.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: 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: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed
• Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed.Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed
• Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed.Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed
• 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.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: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed
• 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.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: 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: 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.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: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed
• 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.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: 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: DV17 Data view subscribe on ACL_CTRL_ACC_NOTIFY is not allowed
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• 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: Start broker for all scenarios.Scenario: Start broker for all scenarios
• Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios
• Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios
• Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios
• Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Send BIRTH message and then DC message.Scenario: Send BIRTH message and then DC message
• Scenario: Send BIRTH message and then DC message.Scenario: Send BIRTH message and then DC message
• Scenario: Send BIRTH message and then DC message.Scenario: Send BIRTH message and then DC message
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop event broker after all scenarios.Scenario: Stop event broker after all scenarios
• Scenario: Stop event broker after all scenarios.Scenario: Stop event broker after all scenarios
• Scenario: Stop event broker after all scenarios.Scenario: Stop event broker after all scenarios
• 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: Start broker for all scenarios.Scenario: Start broker for all scenarios
• Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• 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: 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: 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: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• 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: Start broker for all scenarios.Scenario: Start broker for all scenarios
• Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• 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: Start broker for all scenarios.Scenario: Start broker for all scenarios
• Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore 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: 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: 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: Start broker for all scenarios.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: Start broker for all scenarios
• 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: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Positive scenario without stealing link.Scenario: Positive scenario without stealing link
• Scenario: Positive scenario without stealing link.Scenario: Positive scenario without stealing link
• Scenario: Positive scenario without stealing link.Scenario: Positive scenario without stealing link
• Scenario: Stealing link scenario.Scenario: Stealing link scenario
• Scenario: Stealing link scenario.Scenario: Stealing link scenario
• Scenario: Stealing link scenario.Scenario: Stealing link scenario
• Scenario: Negative scenario when client connects twice with same client id.Scenario: Negative scenario when client connects twice with same client id
• Scenario: Negative scenario when client connects twice with same client id.Scenario: Negative scenario when client connects twice with same client id
• 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: Start broker for all scenarios.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: Start broker for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Connect to the system and publish some data.Scenario: Connect to the system and publish some data
• Scenario: Connect to the system and publish some data.Scenario: Connect to the system and publish some data
• Scenario: Connect to the system and publish some data.Scenario: Connect to the system and publish some data
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios
• Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios
• Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios
• Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios
• Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios
• 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: Start broker for all scenarios.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: Start broker for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Birth message handling from a new device.Scenario: Birth message handling from a new device
• Scenario: Birth message handling from a new device.Scenario: Birth message handling from a new device
• Scenario: Birth message handling from a new device.Scenario: Birth message handling from a new device
• Scenario: Birth message handling from an existing device.Scenario: Birth message handling from an existing device
• Scenario: Birth message handling from an existing device.Scenario: Birth message handling from an existing device
• Scenario: Birth message handling from an existing device.Scenario: Birth message handling from an existing device
• Scenario: Handling of 2 birth messages.Scenario: Handling of 2 birth messages
• Scenario: Handling of 2 birth messages.Scenario: Handling of 2 birth messages
• Scenario: Handling of 2 birth messages.Scenario: Handling of 2 birth messages
• Scenario: Birth and applications event handling.Scenario: Birth and applications event handling
• Scenario: Birth and applications event handling.Scenario: Birth and applications event handling
• Scenario: Birth and applications event handling.Scenario: Birth and applications event handling
• Scenario: Creating new device and tagging it with specific Tag.Scenario: Creating new device and tagging it with specific Tag
• Scenario: Creating new device and tagging it with specific Tag.Scenario: Creating new device and tagging it with specific Tag
• 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.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.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.Scenario: Creating new device, tagging it with specific Tag and then deleting this Tag
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios
• Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios
• Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios
• Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios
• Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios
• 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: Start broker for all scenarios.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: Start broker for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• 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: 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: 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.Scenario: Installing a package
• Scenario: Installing a package.Scenario: Installing a package
• Scenario: Installing a package.Scenario: Installing a package
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios
• Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios
• Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios
• org.eclipse.kapua.service.datastore.internal.MessageStoreServiceTest.deleteByDate