Skip to content

Test Result : (root)

907 failures (+89) , 3,270 skipped (+1420)
5,714 tests (+205)
Took 3 min 54 sec.

All Failed Tests

Test NameDurationAge
 Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic.Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic34 ms2
 Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic.Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic13 ms2
 Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic.Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic0 ms2
 Scenario: Account based ClientInfo data check.Scenario: Account based ClientInfo data check1 ms2
 Scenario: Account based ClientInfo data check.Scenario: Account based ClientInfo data check45 ms1
 Scenario: Account based ClientInfo data check.Scenario: Account based ClientInfo data check30 ms1
 Scenario: Account based ClientInfo data check.Scenario: Account based ClientInfo data check56 ms1
 Scenario: Account based ClientInfo data check.Scenario: Account based ClientInfo data check18 ms2
 Scenario: Account based ClientInfo data check.Scenario: Account based ClientInfo data check56 ms2
 Scenario: Account based ClientInfo data check.Scenario: Account based ClientInfo data check15 ms1
 Scenario: Account based ClientInfo data check.Scenario: Account based ClientInfo data check32 ms2
 Scenario: Account based ClientInfo data check.Scenario: Account based ClientInfo data check44 ms2
 Scenario: Account based ClientInfo data check.Scenario: Account based ClientInfo data check0 ms1
 Scenario: Account exactly on its expiration date.Scenario: Account exactly on its expiration date0 ms1
 Scenario: Account exactly on its expiration date.Scenario: Account exactly on its expiration date9 ms1
 Scenario: Account past its expiration date.Scenario: Account past its expiration date0 ms1
 Scenario: Account past its expiration date.Scenario: Account past its expiration date9 ms1
 Scenario: Account wide metrics check.Scenario: Account wide metrics check33 ms1
 Scenario: Account wide metrics check.Scenario: Account wide metrics check41 ms2
 Scenario: Account wide metrics check.Scenario: Account wide metrics check12 ms1
 Scenario: Account wide metrics check.Scenario: Account wide metrics check44 ms1
 Scenario: Account wide metrics check.Scenario: Account wide metrics check0 ms2
 Scenario: Account wide metrics check.Scenario: Account wide metrics check57 ms2
 Scenario: Account wide metrics check.Scenario: Account wide metrics check27 ms2
 Scenario: Account wide metrics check.Scenario: Account wide metrics check9 ms2
 Scenario: Account wide metrics check.Scenario: Account wide metrics check21 ms1
 Scenario: Account wide metrics check.Scenario: Account wide metrics check1 ms1
 Scenario: Account with future expiration date.Scenario: Account with future expiration date0 ms1
 Scenario: Account with future expiration date.Scenario: Account with future expiration date8 ms1
 Scenario: Account with no expiration date.Scenario: Account with no expiration date0 ms1
 Scenario: Account with no expiration date.Scenario: Account with no expiration date9 ms1
 Scenario: B1 Broker publish to CTRL_ACC_REPLY.Scenario: B1 Broker publish to CTRL_ACC_REPLY0 ms2
 Scenario: B1 Broker publish to CTRL_ACC_REPLY.Scenario: B1 Broker publish to CTRL_ACC_REPLY13 ms2
 Scenario: B1 Broker publish to CTRL_ACC_REPLY.Scenario: B1 Broker publish to CTRL_ACC_REPLY27 ms2
 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 allowed11 ms2
 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 allowed24 ms2
 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 allowed1 ms2
 Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed.Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed25 ms2
 Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed.Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed11 ms2
 Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed.Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed0 ms2
 Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI.Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI10 ms2
 Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI.Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI0 ms2
 Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI.Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI23 ms2
 Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed24 ms2
 Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed11 ms2
 Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed1 ms2
 Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed26 ms1
 Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed0 ms1
 Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed11 ms1
 Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY.Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY1 ms2
 Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY.Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY30 ms2
 Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY.Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY13 ms2
 Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY.Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY26 ms2
 Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY.Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY13 ms2
 Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY.Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY0 ms2
 Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account.Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account12 ms1
 Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account.Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account27 ms1
 Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account.Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account1 ms1
 Scenario: B5 Broker publish to CTRL_ACC is not allowed.Scenario: B5 Broker publish to CTRL_ACC is not allowed0 ms2
 Scenario: B5 Broker publish to CTRL_ACC is not allowed.Scenario: B5 Broker publish to CTRL_ACC is not allowed11 ms2
 Scenario: B5 Broker publish to CTRL_ACC is not allowed.Scenario: B5 Broker publish to CTRL_ACC is not allowed24 ms2
 Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed.Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed11 ms2
 Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed.Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed25 ms2
 Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed.Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed0 ms2
 Scenario: B7 Broker subscribe on CTRL_ACC is not allowed.Scenario: B7 Broker subscribe on CTRL_ACC is not allowed25 ms2
 Scenario: B7 Broker subscribe on CTRL_ACC is not allowed.Scenario: B7 Broker subscribe on CTRL_ACC is not allowed0 ms2
 Scenario: B7 Broker subscribe on CTRL_ACC is not allowed.Scenario: B7 Broker subscribe on CTRL_ACC is not allowed12 ms2
 Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI.Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI26 ms2
 Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI.Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI11 ms2
 Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI.Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI1 ms2
 Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed.Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed27 ms2
 Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed.Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed0 ms2
 Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed.Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed13 ms2
 Scenario: Birth and applications event handling.Scenario: Birth and applications event handling0 ms2
 Scenario: Birth and applications event handling.Scenario: Birth and applications event handling11 ms2
 Scenario: Birth and applications event handling.Scenario: Birth and applications event handling24 ms2
 Scenario: Birth and death message handling.Scenario: Birth and death message handling25 ms1
 Scenario: Birth and death message handling.Scenario: Birth and death message handling0 ms1
 Scenario: Birth and death message handling.Scenario: Birth and death message handling11 ms1
 Scenario: Birth and missing event handling.Scenario: Birth and missing event handling1 ms1
 Scenario: Birth and missing event handling.Scenario: Birth and missing event handling26 ms1
 Scenario: Birth and missing event handling.Scenario: Birth and missing event handling12 ms1
 Scenario: Birth message handling from a new device.Scenario: Birth message handling from a new device14 ms2
 Scenario: Birth message handling from a new device.Scenario: Birth message handling from a new device33 ms2
 Scenario: Birth message handling from a new device.Scenario: Birth message handling from a new device0 ms2
 Scenario: Birth message handling from an existing device.Scenario: Birth message handling from an existing device0 ms2
 Scenario: Birth message handling from an existing device.Scenario: Birth message handling from an existing device14 ms2
 Scenario: Birth message handling from an existing device.Scenario: Birth message handling from an existing device31 ms2
 Scenario: Both the parent and child accounts do not expire.Scenario: Both the parent and child accounts do not expire10 ms1
 Scenario: Both the parent and child accounts do not expire.Scenario: Both the parent and child accounts do not expire0 ms1
 Scenario: Both the parent and child accounts have the same expiration date.Scenario: Both the parent and child accounts have the same expiration date0 ms1
 Scenario: Both the parent and child accounts have the same expiration date.Scenario: Both the parent and child accounts have the same expiration date9 ms1
 Scenario: Captured date based ClientInfo data check.Scenario: Captured date based ClientInfo data check68 ms1
 Scenario: Captured date based ClientInfo data check.Scenario: Captured date based ClientInfo data check0 ms1
 Scenario: Captured date based ClientInfo data check.Scenario: Captured date based ClientInfo data check31 ms1
 Scenario: Captured date based ClientInfo data check.Scenario: Captured date based ClientInfo data check20 ms1
 Scenario: Captured date based ClientInfo data check.Scenario: Captured date based ClientInfo data check34 ms1
 Scenario: Captured date based ClientInfo data check.Scenario: Captured date based ClientInfo data check8 ms1
 Scenario: Captured date based ClientInfo data check.Scenario: Captured date based ClientInfo data check42 ms1
 Scenario: Captured date based ClientInfo data check.Scenario: Captured date based ClientInfo data check11 ms1
 Scenario: Captured date based ClientInfo data check.Scenario: Captured date based ClientInfo data check22 ms1
 Scenario: Captured date based ClientInfo data check.Scenario: Captured date based ClientInfo data check0 ms1
 Scenario: Channel info queries based on datastore channel filters.Scenario: Channel info queries based on datastore channel filters33 ms2
 Scenario: Channel info queries based on datastore channel filters.Scenario: Channel info queries based on datastore channel filters49 ms2
 Scenario: Channel info queries based on datastore channel filters.Scenario: Channel info queries based on datastore channel filters66 ms2
 Scenario: Channel info queries based on datastore channel filters.Scenario: Channel info queries based on datastore channel filters11 ms2
 Scenario: Channel info queries based on datastore channel filters.Scenario: Channel info queries based on datastore channel filters33 ms1
 Scenario: Channel info queries based on datastore channel filters.Scenario: Channel info queries based on datastore channel filters12 ms1
 Scenario: Channel info queries based on datastore channel filters.Scenario: Channel info queries based on datastore channel filters0 ms1
 Scenario: Channel info queries based on datastore channel filters.Scenario: Channel info queries based on datastore channel filters21 ms1
 Scenario: Channel info queries based on datastore channel filters.Scenario: Channel info queries based on datastore channel filters0 ms2
 Scenario: Channel info queries based on datastore channel filters.Scenario: Channel info queries based on datastore channel filters44 ms1
 Scenario: ChannelInfo client ID and topic data based on the client id.Scenario: ChannelInfo client ID and topic data based on the client id10 ms2
 Scenario: ChannelInfo client ID and topic data based on the client id.Scenario: ChannelInfo client ID and topic data based on the client id28 ms2
 Scenario: ChannelInfo client ID and topic data based on the client id.Scenario: ChannelInfo client ID and topic data based on the client id14 ms1
 Scenario: ChannelInfo client ID and topic data based on the client id.Scenario: ChannelInfo client ID and topic data based on the client id57 ms2
 Scenario: ChannelInfo client ID and topic data based on the client id.Scenario: ChannelInfo client ID and topic data based on the client id41 ms2
 Scenario: ChannelInfo client ID and topic data based on the client id.Scenario: ChannelInfo client ID and topic data based on the client id0 ms2
 Scenario: ChannelInfo client ID and topic data based on the client id.Scenario: ChannelInfo client ID and topic data based on the client id24 ms1
 Scenario: ChannelInfo client ID and topic data based on the client id.Scenario: ChannelInfo client ID and topic data based on the client id1 ms1
 Scenario: ChannelInfo client ID and topic data based on the client id.Scenario: ChannelInfo client ID and topic data based on the client id37 ms1
 Scenario: ChannelInfo client ID and topic data based on the client id.Scenario: ChannelInfo client ID and topic data based on the client id49 ms1
 Scenario: ChannelInfo client ID based on the account id.Scenario: ChannelInfo client ID based on the account id1 ms1
 Scenario: ChannelInfo client ID based on the account id.Scenario: ChannelInfo client ID based on the account id42 ms2
 Scenario: ChannelInfo client ID based on the account id.Scenario: ChannelInfo client ID based on the account id14 ms1
 Scenario: ChannelInfo client ID based on the account id.Scenario: ChannelInfo client ID based on the account id10 ms2
 Scenario: ChannelInfo client ID based on the account id.Scenario: ChannelInfo client ID based on the account id38 ms1
 Scenario: ChannelInfo client ID based on the account id.Scenario: ChannelInfo client ID based on the account id28 ms2
 Scenario: ChannelInfo client ID based on the account id.Scenario: ChannelInfo client ID based on the account id57 ms2
 Scenario: ChannelInfo client ID based on the account id.Scenario: ChannelInfo client ID based on the account id51 ms1
 Scenario: ChannelInfo client ID based on the account id.Scenario: ChannelInfo client ID based on the account id0 ms2
 Scenario: ChannelInfo client ID based on the account id.Scenario: ChannelInfo client ID based on the account id24 ms1
 Scenario: ChannelInfo last published date.Scenario: ChannelInfo last published date42 ms2
 Scenario: ChannelInfo last published date.Scenario: ChannelInfo last published date26 ms1
 Scenario: ChannelInfo last published date.Scenario: ChannelInfo last published date40 ms1
 Scenario: ChannelInfo last published date.Scenario: ChannelInfo last published date1 ms2
 Scenario: ChannelInfo last published date.Scenario: ChannelInfo last published date83 ms1
 Scenario: ChannelInfo last published date.Scenario: ChannelInfo last published date28 ms2
 Scenario: ChannelInfo last published date.Scenario: ChannelInfo last published date14 ms1
 Scenario: ChannelInfo last published date.Scenario: ChannelInfo last published date57 ms2
 Scenario: ChannelInfo last published date.Scenario: ChannelInfo last published date0 ms1
 Scenario: ChannelInfo last published date.Scenario: ChannelInfo last published date10 ms2
 Scenario: ChannelInfo topic data based on the account id.Scenario: ChannelInfo topic data based on the account id1 ms2
 Scenario: ChannelInfo topic data based on the account id.Scenario: ChannelInfo topic data based on the account id25 ms1
 Scenario: ChannelInfo topic data based on the account id.Scenario: ChannelInfo topic data based on the account id0 ms1
 Scenario: ChannelInfo topic data based on the account id.Scenario: ChannelInfo topic data based on the account id29 ms2
 Scenario: ChannelInfo topic data based on the account id.Scenario: ChannelInfo topic data based on the account id43 ms2
 Scenario: ChannelInfo topic data based on the account id.Scenario: ChannelInfo topic data based on the account id10 ms2
 Scenario: ChannelInfo topic data based on the account id.Scenario: ChannelInfo topic data based on the account id59 ms2
 Scenario: ChannelInfo topic data based on the account id.Scenario: ChannelInfo topic data based on the account id14 ms1
 Scenario: ChannelInfo topic data based on the account id.Scenario: ChannelInfo topic data based on the account id52 ms1
 Scenario: ChannelInfo topic data based on the account id.Scenario: ChannelInfo topic data based on the account id39 ms1
 Scenario: Check the database cache coherency.Scenario: Check the database cache coherency0 ms1
 Scenario: Check the database cache coherency.Scenario: Check the database cache coherency33 ms1
 Scenario: Check the database cache coherency.Scenario: Check the database cache coherency44 ms1
 Scenario: Check the database cache coherency.Scenario: Check the database cache coherency62 ms1
 Scenario: Check the database cache coherency.Scenario: Check the database cache coherency29 ms1
 Scenario: Check the database cache coherency.Scenario: Check the database cache coherency14 ms1
 Scenario: Check the database cache coherency.Scenario: Check the database cache coherency47 ms1
 Scenario: Check the database cache coherency.Scenario: Check the database cache coherency10 ms1
 Scenario: Check the database cache coherency.Scenario: Check the database cache coherency58 ms1
 Scenario: Check the database cache coherency.Scenario: Check the database cache coherency0 ms1
 Scenario: Check the mapping for message semantic topics.Scenario: Check the mapping for message semantic topics43 ms1
 Scenario: Check the mapping for message semantic topics.Scenario: Check the mapping for message semantic topics29 ms1
 Scenario: Check the mapping for message semantic topics.Scenario: Check the mapping for message semantic topics0 ms1
 Scenario: Check the mapping for message semantic topics.Scenario: Check the mapping for message semantic topics41 ms2
 Scenario: Check the mapping for message semantic topics.Scenario: Check the mapping for message semantic topics8 ms2
 Scenario: Check the mapping for message semantic topics.Scenario: Check the mapping for message semantic topics57 ms1
 Scenario: Check the mapping for message semantic topics.Scenario: Check the mapping for message semantic topics0 ms2
 Scenario: Check the mapping for message semantic topics.Scenario: Check the mapping for message semantic topics55 ms2
 Scenario: Check the mapping for message semantic topics.Scenario: Check the mapping for message semantic topics14 ms1
 Scenario: Check the mapping for message semantic topics.Scenario: Check the mapping for message semantic topics29 ms2
 Scenario: Check the message store.Scenario: Check the message store9 ms2
 Scenario: Check the message store.Scenario: Check the message store37 ms1
 Scenario: Check the message store.Scenario: Check the message store13 ms1
 Scenario: Check the message store.Scenario: Check the message store28 ms2
 Scenario: Check the message store.Scenario: Check the message store0 ms1
 Scenario: Check the message store.Scenario: Check the message store23 ms1
 Scenario: Check the message store.Scenario: Check the message store58 ms2
 Scenario: Check the message store.Scenario: Check the message store0 ms2
 Scenario: Check the message store.Scenario: Check the message store49 ms1
 Scenario: Check the message store.Scenario: Check the message store42 ms2
 Scenario: Child account expires after parent.Scenario: Child account expires after parent10 ms1
 Scenario: Child account expires after parent.Scenario: Child account expires after parent0 ms1
 Scenario: Child account expires before parent.Scenario: Child account expires before parent17 ms1
 Scenario: Child account expires before parent.Scenario: Child account expires before parent1 ms1
 Scenario: Child account has null expiration date.Scenario: Child account has null expiration date26 ms1
 Scenario: Child account has null expiration date.Scenario: Child account has null expiration date1 ms1
 Scenario: Client Id based ClientInfo data check.Scenario: Client Id based ClientInfo data check33 ms1
 Scenario: Client Id based ClientInfo data check.Scenario: Client Id based ClientInfo data check21 ms1
 Scenario: Client Id based ClientInfo data check.Scenario: Client Id based ClientInfo data check0 ms1
 Scenario: Client Id based ClientInfo data check.Scenario: Client Id based ClientInfo data check44 ms1
 Scenario: Client Id based ClientInfo data check.Scenario: Client Id based ClientInfo data check0 ms2
 Scenario: Client Id based ClientInfo data check.Scenario: Client Id based ClientInfo data check16 ms2
 Scenario: Client Id based ClientInfo data check.Scenario: Client Id based ClientInfo data check0.1 sec2
 Scenario: Client Id based ClientInfo data check.Scenario: Client Id based ClientInfo data check59 ms2
 Scenario: Client Id based ClientInfo data check.Scenario: Client Id based ClientInfo data check11 ms1
 Scenario: Client Id based ClientInfo data check.Scenario: Client Id based ClientInfo data check86 ms2
 Scenario: Connect to the system and publish some data.Scenario: Connect to the system and publish some data0 ms2
 Scenario: Connect to the system and publish some data.Scenario: Connect to the system and publish some data15 ms2
 Scenario: Connect to the system and publish some data.Scenario: Connect to the system and publish some data35 ms2
 Scenario: Create index with specific prefix.Scenario: Create index with specific prefix39 ms2
 Scenario: Create index with specific prefix.Scenario: Create index with specific prefix10 ms2
 Scenario: Create index with specific prefix.Scenario: Create index with specific prefix54 ms2
 Scenario: Create index with specific prefix.Scenario: Create index with specific prefix26 ms2
 Scenario: Create index with specific prefix.Scenario: Create index with specific prefix0 ms2
 Scenario: Creating index with regular user.Scenario: Creating index with regular user24 ms1
 Scenario: Creating index with regular user.Scenario: Creating index with regular user35 ms1
 Scenario: Creating index with regular user.Scenario: Creating index with regular user0 ms1
 Scenario: Creating index with regular user.Scenario: Creating index with regular user48 ms1
 Scenario: Creating index with regular user.Scenario: Creating index with regular user8 ms1
 Scenario: Creating new device and tagging it with specific Tag.Scenario: Creating new device and tagging it with specific Tag0 ms2
 Scenario: Creating new device and tagging it with specific Tag.Scenario: Creating new device and tagging it with specific Tag13 ms2
 Scenario: Creating new device and tagging it with specific Tag.Scenario: Creating new device and tagging it with specific Tag27 ms2
 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 Tag25 ms2
 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 Tag11 ms2
 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 Tag0 ms2
 Scenario: Creating tag.Scenario: Creating tag20 ms1
 Scenario: Creating tag.Scenario: Creating tag0 ms1
 Scenario: Creating two indexes with daily index.Scenario: Creating two indexes with daily index27 ms2
 Scenario: Creating two indexes with daily index.Scenario: Creating two indexes with daily index40 ms2
 Scenario: Creating two indexes with daily index.Scenario: Creating two indexes with daily index0 ms2
 Scenario: Creating two indexes with daily index.Scenario: Creating two indexes with daily index9 ms2
 Scenario: Creating two indexes with daily index.Scenario: Creating two indexes with daily index56 ms2
 Scenario: Creating two indexes with hourly index.Scenario: Creating two indexes with hourly index43 ms2
 Scenario: Creating two indexes with hourly index.Scenario: Creating two indexes with hourly index29 ms2
 Scenario: Creating two indexes with hourly index.Scenario: Creating two indexes with hourly index57 ms2
 Scenario: Creating two indexes with hourly index.Scenario: Creating two indexes with hourly index12 ms2
 Scenario: Creating two indexes with hourly index.Scenario: Creating two indexes with hourly index1 ms2
 Scenario: Creating two indexes with weekly index.Scenario: Creating two indexes with weekly index26 ms1
 Scenario: Creating two indexes with weekly index.Scenario: Creating two indexes with weekly index39 ms1
 Scenario: Creating two indexes with weekly index.Scenario: Creating two indexes with weekly index1 ms1
 Scenario: Creating two indexes with weekly index.Scenario: Creating two indexes with weekly index54 ms1
 Scenario: Creating two indexes with weekly index.Scenario: Creating two indexes with weekly index9 ms1
 Scenario: D1 Device publish to CTRL_ACC_REPLY.Scenario: D1 Device publish to CTRL_ACC_REPLY24 ms2
 Scenario: D1 Device publish to CTRL_ACC_REPLY.Scenario: D1 Device publish to CTRL_ACC_REPLY0 ms2
 Scenario: D1 Device publish to CTRL_ACC_REPLY.Scenario: D1 Device publish to CTRL_ACC_REPLY11 ms2
 Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI.Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI0 ms2
 Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI.Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI24 ms2
 Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI.Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI11 ms2
 Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed11 ms2
 Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed25 ms2
 Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed0 ms2
 Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed0 ms2
 Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed12 ms2
 Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed26 ms2
 Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY.Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY0 ms2
 Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY.Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY23 ms2
 Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY.Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY10 ms2
 Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY.Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY0 ms2
 Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY.Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY12 ms2
 Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY.Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY30 ms2
 Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account.Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account0 ms2
 Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account.Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account24 ms2
 Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account.Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account11 ms2
 Scenario: D5 Device subscribe - publish - admin on CTRL_ACC.Scenario: D5 Device subscribe - publish - admin on CTRL_ACC40 ms2
 Scenario: D5 Device subscribe - publish - admin on CTRL_ACC.Scenario: D5 Device subscribe - publish - admin on CTRL_ACC19 ms2
 Scenario: D5 Device subscribe - publish - admin on CTRL_ACC.Scenario: D5 Device subscribe - publish - admin on CTRL_ACC1 ms2
 Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI.Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI0 ms2
 Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI.Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI11 ms2
 Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI.Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI23 ms2
 Scenario: D7 Device publish to ACL_DATA_ACC is not allowed.Scenario: D7 Device publish to ACL_DATA_ACC is not allowed11 ms2
 Scenario: D7 Device publish to ACL_DATA_ACC is not allowed.Scenario: D7 Device publish to ACL_DATA_ACC is not allowed0 ms2
 Scenario: D7 Device publish to ACL_DATA_ACC is not allowed.Scenario: D7 Device publish to ACL_DATA_ACC is not allowed24 ms2
 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 allowed24 ms2
 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 allowed0 ms2
 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 allowed10 ms2
 Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed.Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed0 ms2
 Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed.Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed27 ms2
 Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed.Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed12 ms2
 Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed.Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed0 ms2
 Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed.Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed33 ms2
 Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed.Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed14 ms2
 Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI.Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI1 ms2
 Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI.Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI12 ms2
 Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI.Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI29 ms2
 Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed13 ms2
 Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed0 ms2
 Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed28 ms2
 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 allowed30 ms1
 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 allowed14 ms1
 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 allowed1 ms1
 Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY.Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY14 ms2
 Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY.Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY30 ms2
 Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY.Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY1 ms2
 Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY.Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY11 ms2
 Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY.Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY26 ms2
 Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY.Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY0 ms2
 Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account.Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account0 ms2
 Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account.Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account25 ms2
 Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account.Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account11 ms2
 Scenario: DM5 Data manage publish to CTRL_ACC is not allowed.Scenario: DM5 Data manage publish to CTRL_ACC is not allowed0 ms2
 Scenario: DM5 Data manage publish to CTRL_ACC is not allowed.Scenario: DM5 Data manage publish to CTRL_ACC is not allowed11 ms2
 Scenario: DM5 Data manage publish to CTRL_ACC is not allowed.Scenario: DM5 Data manage publish to CTRL_ACC is not allowed24 ms2
 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 allowed23 ms2
 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 allowed10 ms2
 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 allowed0 ms2
 Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed.Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed10 ms2
 Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed.Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed0 ms2
 Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed.Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed23 ms2
 Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI.Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI33 ms2
 Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI.Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI12 ms2
 Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI.Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI0 ms2
 Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC.Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC0 ms2
 Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC.Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC10 ms2
 Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC.Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC24 ms2
 Scenario: DV1 Data view publish to CTRL_ACC_REPLY.Scenario: DV1 Data view publish to CTRL_ACC_REPLY0 ms1
 Scenario: DV1 Data view publish to CTRL_ACC_REPLY.Scenario: DV1 Data view publish to CTRL_ACC_REPLY11 ms1
 Scenario: DV1 Data view publish to CTRL_ACC_REPLY.Scenario: DV1 Data view publish to CTRL_ACC_REPLY24 ms1
 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 allowed21 ms2
 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 allowed9 ms2
 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 allowed0 ms2
 Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed.Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed21 ms2
 Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed.Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed0 ms2
 Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed.Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed9 ms2
 Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed.Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed0 ms2
 Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed.Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed9 ms2
 Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed.Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed24 ms2
 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 allowed0 ms2
 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 allowed20 ms2
 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 allowed9 ms2
 Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed0 ms2
 Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed9 ms2
 Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed20 ms2
 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 allowed0 ms2
 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 allowed10 ms2
 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 allowed25 ms2
 Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY.Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY10 ms2
 Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY.Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY0 ms2
 Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY.Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY22 ms2
 Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY.Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY19 ms2
 Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY.Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY0 ms2
 Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY.Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY9 ms2
 Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account.Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account1 ms1
 Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account.Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account21 ms1
 Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account.Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account9 ms1
 Scenario: DV5 Data view publish to CTRL_ACC is not allowed.Scenario: DV5 Data view publish to CTRL_ACC is not allowed0 ms2
 Scenario: DV5 Data view publish to CTRL_ACC is not allowed.Scenario: DV5 Data view publish to CTRL_ACC is not allowed10 ms2
 Scenario: DV5 Data view publish to CTRL_ACC is not allowed.Scenario: DV5 Data view publish to CTRL_ACC is not allowed22 ms2
 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 allowed0 ms2
 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 allowed21 ms2
 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 allowed9 ms2
 Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed.Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed20 ms1
 Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed.Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed0 ms1
 Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed.Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed9 ms1
 Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI.Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI1 ms2
 Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI.Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI9 ms2
 Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI.Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI20 ms2
 Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed.Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed21 ms2
 Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed.Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed0 ms2
 Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed.Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed9 ms2
 Scenario: Delete items based on query results.Scenario: Delete items based on query results12 ms2
 Scenario: Delete items based on query results.Scenario: Delete items based on query results37 ms2
 Scenario: Delete items based on query results.Scenario: Delete items based on query results60 ms1
 Scenario: Delete items based on query results.Scenario: Delete items based on query results64 ms2
 Scenario: Delete items based on query results.Scenario: Delete items based on query results51 ms2
 Scenario: Delete items based on query results.Scenario: Delete items based on query results17 ms1
 Scenario: Delete items based on query results.Scenario: Delete items based on query results46 ms1
 Scenario: Delete items based on query results.Scenario: Delete items based on query results31 ms1
 Scenario: Delete items based on query results.Scenario: Delete items based on query results0 ms2
 Scenario: Delete items based on query results.Scenario: Delete items based on query results0 ms1
 Scenario: Delete items by the datastore ID.Scenario: Delete items by the datastore ID0 ms2
 Scenario: Delete items by the datastore ID.Scenario: Delete items by the datastore ID19 ms1
 Scenario: Delete items by the datastore ID.Scenario: Delete items by the datastore ID31 ms1
 Scenario: Delete items by the datastore ID.Scenario: Delete items by the datastore ID64 ms1
 Scenario: Delete items by the datastore ID.Scenario: Delete items by the datastore ID32 ms2
 Scenario: Delete items by the datastore ID.Scenario: Delete items by the datastore ID49 ms1
 Scenario: Delete items by the datastore ID.Scenario: Delete items by the datastore ID57 ms2
 Scenario: Delete items by the datastore ID.Scenario: Delete items by the datastore ID9 ms2
 Scenario: Delete items by the datastore ID.Scenario: Delete items by the datastore ID0 ms1
 Scenario: Delete items by the datastore ID.Scenario: Delete items by the datastore ID84 ms2
 Scenario: Delete middle child expiration.Scenario: Delete middle child expiration0 ms1
 Scenario: Delete middle child expiration.Scenario: Delete middle child expiration12 ms1
 Scenario: Delete parent expiration.Scenario: Delete parent expiration29 ms1
 Scenario: Delete parent expiration.Scenario: Delete parent expiration0 ms1
 Scenario: Deleting tag.Scenario: Deleting tag1 ms1
 Scenario: Deleting tag.Scenario: Deleting tag18 ms1
 Scenario: Deleting user in account that is higher in hierarchy.Scenario: Deleting user in account that is higher in hierarchy12 ms1
 Scenario: Deleting user in account that is higher in hierarchy.Scenario: Deleting user in account that is higher in hierarchy0 ms1
 Scenario: Deleting user in account that is lower in hierarchy.Scenario: Deleting user in account that is lower in hierarchy0 ms1
 Scenario: Deleting user in account that is lower in hierarchy.Scenario: Deleting user in account that is lower in hierarchy9 ms1
 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 mode33 ms1
 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 mode1 ms1
 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 mode20 ms1
 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 mode47 ms1
 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 mode0.1 sec1
 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 mode78 ms1
 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 mode1 ms1
 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 mode93 ms1
 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 devices0.11 sec1
 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 devices92 ms1
 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 devices0.14 sec1
 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 devices0 ms1
 Scenario: Handling of 2 birth messages.Scenario: Handling of 2 birth messages27 ms2
 Scenario: Handling of 2 birth messages.Scenario: Handling of 2 birth messages1 ms2
 Scenario: Handling of 2 birth messages.Scenario: Handling of 2 birth messages13 ms2
 Scenario: Handling of a disconnect message from a non existing device.Scenario: Handling of a disconnect message from a non existing device0 ms1
 Scenario: Handling of a disconnect message from a non existing device.Scenario: Handling of a disconnect message from a non existing device11 ms1
 Scenario: Handling of a disconnect message from a non existing device.Scenario: Handling of a disconnect message from a non existing device24 ms1
 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 login0 ms1
 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 login10 ms1
 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 inclusive0 ms1
 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 inclusive9 ms1
 Scenario: If user credential expiration date is tomorrow, user can login.Scenario: If user credential expiration date is tomorrow, user can login0 ms1
 Scenario: If user credential expiration date is tomorrow, user can login.Scenario: If user credential expiration date is tomorrow, user can login9 ms1
 Scenario: If user credential is in state disabled, user can not login.Scenario: If user credential is in state disabled, user can not login10 ms1
 Scenario: If user credential is in state disabled, user can not login.Scenario: If user credential is in state disabled, user can not login0 ms1
 Scenario: If user credential is in state enabled, user can login.Scenario: If user credential is in state enabled, user can login0 ms1
 Scenario: If user credential is in state enabled, user can login.Scenario: If user credential is in state enabled, user can login8 ms1
 Scenario: If user expiration date is before today, user can not login.Scenario: If user expiration date is before today, user can not login9 ms1
 Scenario: If user expiration date is before today, user can not login.Scenario: If user expiration date is before today, user can not login0 ms1
 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 reached0 ms1
 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 reached10 ms1
 Scenario: If user expiration date is tomorrow, user can login.Scenario: If user expiration date is tomorrow, user can login1 ms1
 Scenario: If user expiration date is tomorrow, user can login.Scenario: If user expiration date is tomorrow, user can login12 ms1
 Scenario: Installing a package.Scenario: Installing a package0 ms2
 Scenario: Installing a package.Scenario: Installing a package28 ms2
 Scenario: Installing a package.Scenario: Installing a package14 ms2
 Scenario: MetricsInfo client ID and topic data based on the client id.Scenario: MetricsInfo client ID and topic data based on the client id45 ms2
 Scenario: MetricsInfo client ID and topic data based on the client id.Scenario: MetricsInfo client ID and topic data based on the client id23 ms1
 Scenario: MetricsInfo client ID and topic data based on the client id.Scenario: MetricsInfo client ID and topic data based on the client id31 ms2
 Scenario: MetricsInfo client ID and topic data based on the client id.Scenario: MetricsInfo client ID and topic data based on the client id34 ms1
 Scenario: MetricsInfo client ID and topic data based on the client id.Scenario: MetricsInfo client ID and topic data based on the client id0 ms2
 Scenario: MetricsInfo client ID and topic data based on the client id.Scenario: MetricsInfo client ID and topic data based on the client id9 ms2
 Scenario: MetricsInfo client ID and topic data based on the client id.Scenario: MetricsInfo client ID and topic data based on the client id12 ms1
 Scenario: MetricsInfo client ID and topic data based on the client id.Scenario: MetricsInfo client ID and topic data based on the client id62 ms2
 Scenario: MetricsInfo client ID and topic data based on the client id.Scenario: MetricsInfo client ID and topic data based on the client id0 ms1
 Scenario: MetricsInfo client ID and topic data based on the client id.Scenario: MetricsInfo client ID and topic data based on the client id45 ms1
 Scenario: MetricsInfo last published date.Scenario: MetricsInfo last published date42 ms1
 Scenario: MetricsInfo last published date.Scenario: MetricsInfo last published date10 ms2
 Scenario: MetricsInfo last published date.Scenario: MetricsInfo last published date57 ms2
 Scenario: MetricsInfo last published date.Scenario: MetricsInfo last published date11 ms1
 Scenario: MetricsInfo last published date.Scenario: MetricsInfo last published date32 ms1
 Scenario: MetricsInfo last published date.Scenario: MetricsInfo last published date20 ms1
 Scenario: MetricsInfo last published date.Scenario: MetricsInfo last published date42 ms2
 Scenario: MetricsInfo last published date.Scenario: MetricsInfo last published date28 ms2
 Scenario: MetricsInfo last published date.Scenario: MetricsInfo last published date0 ms2
 Scenario: MetricsInfo last published date.Scenario: MetricsInfo last published date0 ms1
 Scenario: Modify last child expiration so that it still expires before parent.Scenario: Modify last child expiration so that it still expires before parent33 ms1
 Scenario: Modify last child expiration so that it still expires before parent.Scenario: Modify last child expiration so that it still expires before parent0 ms1
 Scenario: Modify middle child expiration so that it still expires before parent.Scenario: Modify middle child expiration so that it still expires before parent32 ms1
 Scenario: Modify middle child expiration so that it still expires before parent.Scenario: Modify middle child expiration so that it still expires before parent1 ms1
 Scenario: Modify middle child expiration to outlive parent.Scenario: Modify middle child expiration to outlive parent18 ms1
 Scenario: Modify middle child expiration to outlive parent.Scenario: Modify middle child expiration to outlive parent0 ms1
 Scenario: Modify parent expiration so that it still expires after child.Scenario: Modify parent expiration so that it still expires after child28 ms1
 Scenario: Modify parent expiration so that it still expires after child.Scenario: Modify parent expiration so that it still expires after child1 ms1
 Scenario: Modify parent expiration to before child expiration.Scenario: Modify parent expiration to before child expiration30 ms1
 Scenario: Modify parent expiration to before child expiration.Scenario: Modify parent expiration to before child expiration1 ms1
 Scenario: Negative scenario when client connects twice with same client id.Scenario: Negative scenario when client connects twice with same client id41 ms2
 Scenario: Negative scenario when client connects twice with same client id.Scenario: Negative scenario when client connects twice with same client id16 ms2
 Scenario: Negative scenario when client connects twice with same client id.Scenario: Negative scenario when client connects twice with same client id0 ms2
 Scenario: New connection with reserved ID.Scenario: New connection with reserved ID13 ms1
 Scenario: New connection with reserved ID.Scenario: New connection with reserved ID39 ms1
 Scenario: New connection with reserved ID.Scenario: New connection with reserved ID0 ms1
 Scenario: New connection with reserved ID.Scenario: New connection with reserved ID26 ms1
 Scenario: Positive scenario without stealing link.Scenario: Positive scenario without stealing link36 ms2
 Scenario: Positive scenario without stealing link.Scenario: Positive scenario without stealing link15 ms2
 Scenario: Positive scenario without stealing link.Scenario: Positive scenario without stealing link0 ms2
 Scenario: Query based on message ordering.Scenario: Query based on message ordering0 ms1
 Scenario: Query based on message ordering.Scenario: Query based on message ordering27 ms2
 Scenario: Query based on message ordering.Scenario: Query based on message ordering42 ms2
 Scenario: Query based on message ordering.Scenario: Query based on message ordering36 ms1
 Scenario: Query based on message ordering.Scenario: Query based on message ordering49 ms1
 Scenario: Query based on message ordering.Scenario: Query based on message ordering58 ms2
 Scenario: Query based on message ordering.Scenario: Query based on message ordering0 ms2
 Scenario: Query based on message ordering.Scenario: Query based on message ordering10 ms2
 Scenario: Query based on message ordering.Scenario: Query based on message ordering13 ms1
 Scenario: Query based on message ordering.Scenario: Query based on message ordering23 ms1
 Scenario: Query based on metrics ordering.Scenario: Query based on metrics ordering28 ms2
 Scenario: Query based on metrics ordering.Scenario: Query based on metrics ordering0 ms2
 Scenario: Query based on metrics ordering.Scenario: Query based on metrics ordering9 ms2
 Scenario: Query based on metrics ordering.Scenario: Query based on metrics ordering1 ms1
 Scenario: Query based on metrics ordering.Scenario: Query based on metrics ordering44 ms1
 Scenario: Query based on metrics ordering.Scenario: Query based on metrics ordering16 ms1
 Scenario: Query based on metrics ordering.Scenario: Query based on metrics ordering59 ms1
 Scenario: Query based on metrics ordering.Scenario: Query based on metrics ordering42 ms2
 Scenario: Query based on metrics ordering.Scenario: Query based on metrics ordering57 ms2
 Scenario: Query based on metrics ordering.Scenario: Query based on metrics ordering29 ms1
 Scenario: Query before schema search.Scenario: Query before schema search8 ms2
 Scenario: Query before schema search.Scenario: Query before schema search15 ms1
 Scenario: Query before schema search.Scenario: Query before schema search0 ms1
 Scenario: Query before schema search.Scenario: Query before schema search23 ms2
 Scenario: Query before schema search.Scenario: Query before schema search40 ms1
 Scenario: Query before schema search.Scenario: Query before schema search0 ms2
 Scenario: Query before schema search.Scenario: Query before schema search51 ms2
 Scenario: Query before schema search.Scenario: Query before schema search54 ms1
 Scenario: Query before schema search.Scenario: Query before schema search26 ms1
 Scenario: Query before schema search.Scenario: Query before schema search35 ms2
 Scenario: Send BIRTH message and then DC message.Scenario: Send BIRTH message and then DC message1 ms2
 Scenario: Send BIRTH message and then DC message.Scenario: Send BIRTH message and then DC message14 ms2
 Scenario: Send BIRTH message and then DC message.Scenario: Send BIRTH message and then DC message41 ms2
 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 set14 ms2
 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 set35 ms2
 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 set0 ms2
 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 System14 ms1
 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 System34 ms1
 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 System1 ms1
 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 file20 ms2
 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 file47 ms2
 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 file1 ms2
 Scenario: Simple positive scenario for creating daily index.Scenario: Simple positive scenario for creating daily index9 ms2
 Scenario: Simple positive scenario for creating daily index.Scenario: Simple positive scenario for creating daily index25 ms2
 Scenario: Simple positive scenario for creating daily index.Scenario: Simple positive scenario for creating daily index39 ms2
 Scenario: Simple positive scenario for creating daily index.Scenario: Simple positive scenario for creating daily index54 ms2
 Scenario: Simple positive scenario for creating daily index.Scenario: Simple positive scenario for creating daily index0 ms2
 Scenario: Simple positive scenario for creating default - weekly index.Scenario: Simple positive scenario for creating default - weekly index60 ms1
 Scenario: Simple positive scenario for creating default - weekly index.Scenario: Simple positive scenario for creating default - weekly index29 ms1
 Scenario: Simple positive scenario for creating default - weekly index.Scenario: Simple positive scenario for creating default - weekly index0 ms1
 Scenario: Simple positive scenario for creating default - weekly index.Scenario: Simple positive scenario for creating default - weekly index11 ms1
 Scenario: Simple positive scenario for creating default - weekly index.Scenario: Simple positive scenario for creating default - weekly index44 ms1
 Scenario: Simple positive scenario for creating hourly index.Scenario: Simple positive scenario for creating hourly index54 ms2
 Scenario: Simple positive scenario for creating hourly index.Scenario: Simple positive scenario for creating hourly index39 ms2
 Scenario: Simple positive scenario for creating hourly index.Scenario: Simple positive scenario for creating hourly index25 ms2
 Scenario: Simple positive scenario for creating hourly index.Scenario: Simple positive scenario for creating hourly index0 ms2
 Scenario: Simple positive scenario for creating hourly index.Scenario: Simple positive scenario for creating hourly index8 ms2
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios0.1 sec2
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios0.27 sec2
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios12 ms2
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios15 ms2
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios61 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios0.46 sec2
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios0.54 sec2
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios0.19 sec1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios9 ms2
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios0.51 sec2
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios0.59 sec2
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios0.56 sec2
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios34 ms2
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios73 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios48 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios18 ms2
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios25 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios31 ms2
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios0.19 sec2
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios0.3 sec2
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios13 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios42 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios0.56 sec2
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios10 sec2
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios11 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios49 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios0.21 sec1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios83 ms2
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios30 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios34 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios57 ms2
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios0 ms2
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios23 ms2
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios41 ms2
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios10 sec2
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios55 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios10 ms2
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios0.34 sec2
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios0.26 sec2
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios0.18 sec1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios0.24 sec2
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios11 ms2
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios0.22 sec2
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios0.2 sec2
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios0.21 sec2
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios0.23 sec1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios35 ms2
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios16 ms2
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios79 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios0 ms2
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios25 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios10 sec2
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios0.52 sec2
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios0.25 sec1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios0.1 sec1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios0.32 sec2
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios92 ms2
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios22 ms2
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios21 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios9 ms2
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios16 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios0.57 sec2
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios27 ms2
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios10 ms2
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios10 sec2
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios14 ms2
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios77 ms2
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios93 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios9 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios14 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios39 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios9 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios21 ms2
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios23 ms2
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios2.8 sec2
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios3.2 sec2
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios3.1 sec1
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios3.2 sec2
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios1.9 sec1
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios3.1 sec2
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios2.8 sec2
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios2.8 sec1
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios3 sec2
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios3.1 sec1
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios2.6 sec1
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios2.2 sec2
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios2.8 sec2
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios7.7 sec2
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios3 sec2
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios2.1 sec2
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios2.2 sec2
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios2.7 sec1
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios3 sec2
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios3 sec2
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios2.8 sec1
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios2.6 sec1
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios1.9 sec1
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios3.1 sec2
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios2.2 sec2
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios2.6 sec1
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios3 sec2
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios2.8 sec2
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios2.9 sec1
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios3.2 sec2
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios2.9 sec1
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios3 sec2
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios2.1 sec2
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios3.1 sec2
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios3 sec2
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios2.8 sec2
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios3.1 sec2
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios2 sec2
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios2.1 sec2
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios3.1 sec1
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios2.8 sec1
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios2.6 sec1
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios7.7 sec2
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios2.1 sec2
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios3.2 sec2
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios3 sec2
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios3.1 sec2
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios7.7 sec2
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios3.1 sec2
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios3.1 sec2
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios2.8 sec2
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios3 sec2
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios0.27 sec2
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios50 ms2
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios9 ms2
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios27 ms1
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios21 ms2
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios0 ms1
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios0 ms2
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios7 ms1
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios0 ms2
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios0.23 sec2
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios0 ms1
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios19 ms1
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios0 ms2
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios0 ms1
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios8 ms1
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios44 ms1
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios9 ms2
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios7 ms1
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios1 ms1
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios25 ms2
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios38 ms1
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios0.21 sec2
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios70 ms1
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios0 ms1
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios38 ms2
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios8 ms2
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios9 ms2
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios1 ms1
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios0.25 sec2
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios10 ms1
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios48 ms2
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios21 ms1
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios20 ms2
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios0 ms2
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios11 ms1
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios8 ms1
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios35 ms2
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios0 ms1
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios9 ms2
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios27 ms1
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios8 ms1
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios0 ms1
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios24 ms1
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios28 ms2
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios55 ms1
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios8 ms1
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios0 ms2
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios23 ms2
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios32 ms1
 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 status32 ms2
 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 status14 ms2
 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 status0 ms2
 Scenario: Stealing link scenario.Scenario: Stealing link scenario1 ms2
 Scenario: Stealing link scenario.Scenario: Stealing link scenario33 ms2
 Scenario: Stealing link scenario.Scenario: Stealing link scenario16 ms2
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios1 ms2
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios93 ms1
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios0.74 sec1
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios45 ms1
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios0 ms2
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios71 ms2
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios48 ms2
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios34 ms2
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios80 ms1
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios0.19 sec1
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios96 ms2
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios0.13 sec2
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios58 ms2
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios0 ms1
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios0 ms1
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios12 ms1
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios39 ms1
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios87 ms2
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios64 ms2
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios9 ms2
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios43 ms1
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios0.16 sec1
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios0 ms1
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios0.1 sec1
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios0.16 sec2
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios0 ms1
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios20 ms2
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios29 ms1
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios55 ms1
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios10 ms2
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios0 ms1
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios32 ms1
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios0 ms1
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios1 ms2
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios75 ms2
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios0.15 sec1
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios0 ms2
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios35 ms2
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios56 ms1
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios0.11 sec1
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios0.13 sec1
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios1 ms2
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios0 ms2
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios0.11 sec1
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios0 ms1
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios0 ms1
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios78 ms2
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios0.1 sec2
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios0.32 sec1
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios8 ms1
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios74 ms2
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios0.71 sec1
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios1 ms1
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios0.29 sec1
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios0 ms2
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios52 ms2
 Scenario: Stop datastore after all scenario.Scenario: Stop datastore after all scenario1 ms1
 Scenario: Stop datastore after all scenario.Scenario: Stop datastore after all scenario25 ms1
 Scenario: Stop datastore after all scenario.Scenario: Stop datastore after all scenario11 ms1
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios14 ms2
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios0 ms1
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios14 ms1
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios0 ms2
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios38 ms2
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios9 ms2
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios0 ms1
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios14 ms2
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios12 ms1
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios10 ms1
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios39 ms1
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios1 ms1
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios17 ms1
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios0 ms2
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios31 ms2
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios1 ms1
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios34 ms2
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios0 ms2
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios0 ms2
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios20 ms1
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios0 ms1
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios1 ms2
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios1 ms1
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios22 ms2
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios1 ms2
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios19 ms1
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios12 ms2
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios0 ms2
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios9 ms2
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios26 ms2
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios32 ms1
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios8 ms2
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios52 ms2
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios29 ms2
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios32 ms1
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios34 ms2
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios28 ms1
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios33 ms1
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios50 ms2
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios8 ms1
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios0 ms1
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios23 ms2
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios34 ms2
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios44 ms1
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios11 ms1
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios17 ms1
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios45 ms1
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios10 ms2
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios43 ms1
 Scenario: Stop event broker after all scenarios.Scenario: Stop event broker after all scenarios10 ms1
 Scenario: Stop event broker after all scenarios.Scenario: Stop event broker after all scenarios0 ms1
 Scenario: Stop event broker after all scenarios.Scenario: Stop event broker after all scenarios0 ms2
 Scenario: Stop event broker after all scenarios.Scenario: Stop event broker after all scenarios12 ms2
 Scenario: Stop event broker after all scenarios.Scenario: Stop event broker after all scenarios24 ms1
 Scenario: Stop event broker after all scenarios.Scenario: Stop event broker after all scenarios33 ms2
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios0 ms2
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios11 ms2
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios9 ms1
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios11 ms1
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios78 ms1
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios9 ms1
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios35 ms1
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios0 ms1
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios18 ms1
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios30 ms2
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios12 ms1
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios43 ms1
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios7 ms1
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios12 ms2
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios1 ms1
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios17 ms1
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios37 ms2
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios11 ms1
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios52 ms2
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios42 ms1
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios49 ms1
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios9 ms2
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios1 ms2
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios0 ms2
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios0 ms1
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios10 ms2
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios1 ms1
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios24 ms2
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios0 ms1
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios0 ms1
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios49 ms1
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios9 ms1
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios23 ms1
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios0 ms2
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios0 ms1
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios1 ms1
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios43 ms1
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios0 ms1
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios22 ms1
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios24 ms2
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios31 ms1
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios19 ms1
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios28 ms2
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios35 ms1
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios20 ms1
 Scenario: Test LOOSE user coupling on single connection.Scenario: Test LOOSE user coupling on single connection12 ms1
 Scenario: Test LOOSE user coupling on single connection.Scenario: Test LOOSE user coupling on single connection1 ms1
 Scenario: Test LOOSE user coupling on single connection.Scenario: Test LOOSE user coupling on single connection44 ms1
 Scenario: Test LOOSE user coupling on single connection.Scenario: Test LOOSE user coupling on single connection29 ms1
 Scenario: Test LOOSE user coupling with 3 connections.Scenario: Test LOOSE user coupling with 3 connections30 ms1
 Scenario: Test LOOSE user coupling with 3 connections.Scenario: Test LOOSE user coupling with 3 connections44 ms1
 Scenario: Test LOOSE user coupling with 3 connections.Scenario: Test LOOSE user coupling with 3 connections0 ms1
 Scenario: Test LOOSE user coupling with 3 connections.Scenario: Test LOOSE user coupling with 3 connections16 ms1
 Scenario: Test STRICT user coupling on single connection.Scenario: Test STRICT user coupling on single connection29 ms1
 Scenario: Test STRICT user coupling on single connection.Scenario: Test STRICT user coupling on single connection43 ms1
 Scenario: Test STRICT user coupling on single connection.Scenario: Test STRICT user coupling on single connection15 ms1
 Scenario: Test STRICT user coupling on single connection.Scenario: Test STRICT user coupling on single connection0 ms1
 Scenario: Test STRICT user coupling with 3 connections and a reserved user.Scenario: Test STRICT user coupling with 3 connections and a reserved user28 ms1
 Scenario: Test STRICT user coupling with 3 connections and a reserved user.Scenario: Test STRICT user coupling with 3 connections and a reserved user43 ms1
 Scenario: Test STRICT user coupling with 3 connections and a reserved user.Scenario: Test STRICT user coupling with 3 connections and a reserved user0 ms1
 Scenario: Test STRICT user coupling with 3 connections and a reserved user.Scenario: Test STRICT user coupling with 3 connections and a reserved user14 ms1
 Scenario: Test STRICT user coupling with user change allowed on single connection.Scenario: Test STRICT user coupling with user change allowed on single connection13 ms1
 Scenario: Test STRICT user coupling with user change allowed on single connection.Scenario: Test STRICT user coupling with user change allowed on single connection26 ms1
 Scenario: Test STRICT user coupling with user change allowed on single connection.Scenario: Test STRICT user coupling with user change allowed on single connection40 ms1
 Scenario: Test STRICT user coupling with user change allowed on single connection.Scenario: Test STRICT user coupling with user change allowed on single connection0 ms1
 Scenario: Test the message store with server timestamp indexing.Scenario: Test the message store with server timestamp indexing0 ms1
 Scenario: Test the message store with server timestamp indexing.Scenario: Test the message store with server timestamp indexing0 ms2
 Scenario: Test the message store with server timestamp indexing.Scenario: Test the message store with server timestamp indexing42 ms2
 Scenario: Test the message store with server timestamp indexing.Scenario: Test the message store with server timestamp indexing24 ms1
 Scenario: Test the message store with server timestamp indexing.Scenario: Test the message store with server timestamp indexing51 ms1
 Scenario: Test the message store with server timestamp indexing.Scenario: Test the message store with server timestamp indexing27 ms2
 Scenario: Test the message store with server timestamp indexing.Scenario: Test the message store with server timestamp indexing9 ms2
 Scenario: Test the message store with server timestamp indexing.Scenario: Test the message store with server timestamp indexing14 ms1
 Scenario: Test the message store with server timestamp indexing.Scenario: Test the message store with server timestamp indexing38 ms1
 Scenario: Test the message store with server timestamp indexing.Scenario: Test the message store with server timestamp indexing57 ms2
 Scenario: Test the message store with timestamp indexing.Scenario: Test the message store with timestamp indexing50 ms1
 Scenario: Test the message store with timestamp indexing.Scenario: Test the message store with timestamp indexing0 ms2
 Scenario: Test the message store with timestamp indexing.Scenario: Test the message store with timestamp indexing14 ms1
 Scenario: Test the message store with timestamp indexing.Scenario: Test the message store with timestamp indexing24 ms1
 Scenario: Test the message store with timestamp indexing.Scenario: Test the message store with timestamp indexing41 ms2
 Scenario: Test the message store with timestamp indexing.Scenario: Test the message store with timestamp indexing0 ms1
 Scenario: Test the message store with timestamp indexing.Scenario: Test the message store with timestamp indexing9 ms2
 Scenario: Test the message store with timestamp indexing.Scenario: Test the message store with timestamp indexing27 ms2
 Scenario: Test the message store with timestamp indexing.Scenario: Test the message store with timestamp indexing37 ms1
 Scenario: Test the message store with timestamp indexing.Scenario: Test the message store with timestamp indexing56 ms2
 Scenario: To be defined.Scenario: To be defined8 ms1
 Scenario: To be defined.Scenario: To be defined0 ms1
 Scenario: User locking itself out by using out login attempts.Scenario: User locking itself out by using out login attempts10 ms1
 Scenario: User locking itself out by using out login attempts.Scenario: User locking itself out by using out login attempts0 ms1
 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 unlock21 ms1
 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 unlock1 ms1
 Scenario: User locking itself out with failed attempts and waiting to unlock.Scenario: User locking itself out with failed attempts and waiting to unlock1 ms1
 Scenario: User locking itself out with failed attempts and waiting to unlock.Scenario: User locking itself out with failed attempts and waiting to unlock22 ms1
 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 failures0 ms1
 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 failures21 ms1
 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 attempts1 ms1
 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 attempts21 ms1

All Tests

ClassDurationFail(diff)Skip(diff)Pass(diff)Total(diff)
Scenario: A fresh database must contain 1 default role in the root scope0 ms0-10-23+33
Scenario: A mock test scenario0.45 sec0-50-23+33-4
Scenario: A newly created account must have some metadata6 ms0-10-23+33
Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic47 ms3+17+20-110+2
Scenario: Access info service sanity checks0 ms0-40-34+44-3
Scenario: Access service comparison sanity checks0 ms0-40-23+33-3
Scenario: Account based ClientInfo data check0.29 sec10+922+110-1232+8
Scenario: Account exactly on its expiration date9 ms2+213+130-1415+1
Scenario: Account expiration date test - Parent and child expiration set, then parent expiration date changed to before child expiration date3 ms0-10-56+66
Scenario: Account expiration date test - Parent expiration set, child expiration after father expiration3 ms0-10-56+66
Scenario: Account expiration date test - Parent expiration set, child expiration before father expiration4 ms0-20-35+55
Scenario: Account expiration date test - Parent expiration set, child expiration null4 ms0-10-56+66
Scenario: Account name must not be mutable3 ms0-10-56+66
Scenario: Account past its expiration date9 ms2+213+130-1415+1
Scenario: Account service metadata3 ms0-10-12+22
Scenario: Account wide metrics check0.24 sec10+926+130-1436+8
Scenario: Account with future expiration date8 ms2+212+120-1314+1
Scenario: Account with no expiration date9 ms2+212+120-1314+1
Scenario: All device parameters must match the device creator8 ms0033
Scenario: B1 Broker publish to CTRL_ACC_REPLY40 ms3+18+30-211+2
Scenario: B10 Broker create sub-topic on ACL_DATA_ACC is not allowed36 ms3+28011+2
Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed36 ms3+27010+2
Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI33 ms3+28011+2
Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed36 ms3+28011+2
Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed37 ms3+37+70-810+2
Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY44 ms3+18+30-211+2
Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY39 ms3+18+30-211+2
Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account40 ms3+38+80-911+2
Scenario: B5 Broker publish to CTRL_ACC is not allowed35 ms3+28011+2
Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed36 ms3+28011+2
Scenario: B7 Broker subscribe on CTRL_ACC is not allowed37 ms3+17+40-310+2
Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI38 ms3+28011+2
Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed40 ms3+28011+2
Scenario: Basic Device Event queries12 ms001414
Scenario: Birth and applications event handling35 ms3+211014+2
Scenario: Birth and death message handling36 ms3+311+110-1214+2
Scenario: Birth and missing event handling39 ms3+311+110-1214+2
Scenario: Birth message handling from a new device47 ms3+212015+2
Scenario: Birth message handling from an existing device45 ms3+211014+2
Scenario: Both the parent and child accounts do not expire10 ms2+210+100-1112+1
Scenario: Both the parent and child accounts have the same expiration date9 ms2+210+100-1112+1
Scenario: Captured date based ClientInfo data check0.23 sec10+1028+280-3038+8
Scenario: Case sensitivness of named device searches10 ms0033
Scenario: Change an existing step name11 ms0-50-78+88-4
Scenario: Change the account parent Id6 ms0-10-45+55
Scenario: Change the account parent path4 ms0-10-45+55
Scenario: Channel info queries based on datastore channel filters0.26 sec10+948+240-2558+8
Scenario: ChannelInfo client ID and topic data based on the client id0.26 sec10+926+130-1436+8
Scenario: ChannelInfo client ID based on the account id0.26 sec10+924+120-1334+8
Scenario: ChannelInfo last published date0.3 sec10+928+140-1538+8
Scenario: ChannelInfo topic data based on the account id0.27 sec10+924+120-1334+8
Scenario: Check account properties5 ms0-10-34+44
Scenario: Check the Device Connection Domain data seetting9 ms0-30-12+22-2
Scenario: Check the database cache coherency0.29 sec10+1028+280-3038+8
Scenario: Check the mapping for message semantic topics0.27 sec10+928+140-1538+8
Scenario: Check the message store0.25 sec10+918+90-1028+8
Scenario: Check the sanity of the Device Connection Domain data initialization6 ms0-20-12+22-1
Scenario: Child account expires after parent10 ms2+28+80-910+1
Scenario: Child account expires before parent18 ms2+210+100-1112+1
Scenario: Child account has null expiration date27 ms2+28+80-910+1
Scenario: Client Id based ClientInfo data check0.37 sec10+926+130-1436+8
Scenario: Compare domain entries0 ms0-50-12+22-4
Scenario: Connect to the system and publish some data50 ms3+119+60-522+2
Scenario: Connection Service factory sanity checks11 ms0-30-12+22-2
Scenario: Count access info entities in a specific scope0 ms0-40-1819+1919-3
Scenario: Count access role entities by scope1 ms0-40-3233+3333-3
Scenario: Count connections in empty scope8 ms0044
Scenario: Count connections in scope12 ms0055
Scenario: Count devices in a specific scope6 ms001111
Scenario: Count devices with a specific BIOS version4 ms0066
Scenario: Count domains in a blank database0 ms0-40-23+33-3
Scenario: Count domains in the database0 ms0-40-56+66-3
Scenario: Count events in empty scope9 ms001010
Scenario: Count events in scope14 ms001414
Scenario: Count groups0 ms0-40-1112+1212-3
Scenario: Count groups in a blank database0 ms0-40-23+33-3
Scenario: Count job items10 ms0-50-34+44-4
Scenario: Count job items in wrong (empty) scope16 ms0-501+11-4
Scenario: Count role permissions in specific scopes0 ms0-30-1415+1515-2
Scenario: Count roles in specific scopes0 ms0-40-1213+1313-3
Scenario: Count step definition items9 ms0-50-34+44-4
Scenario: Count step definitions in wrong (empty) scope16 ms0-501+11-4
Scenario: Count steps in the database10 ms0-50-1011+1111-4
Scenario: Count user4 ms0-10-56+66
Scenario: Create a regular event15 ms0-20-910+1010-1
Scenario: Create a single device11 ms0044
Scenario: Create an event with a null action10 ms0-20-1011+1111-1
Scenario: Create an event with a null scope ID12 ms001010
Scenario: Create and count multiple job targets8 ms0-50-78+88-4
Scenario: Create and count several execution items for a job14 ms0-50-89+99-4
Scenario: Create index with specific prefix0.12 sec5+312+110-1017+4
Scenario: Create multiple users10 ms0-10-45+55
Scenario: Create regular access permissions1 ms0-40-1415+1515-3
Scenario: Create some regular role permissions0 ms0066
Scenario: Create user that already exist3 ms0-10-67+77
Scenario: Create user that has more than DB allowed length5 ms0-10-45+55
Scenario: Create user with short name8 ms0-10-45+55
Scenario: Create user with special characters in his name5 ms0-10-45+55
Scenario: Create with permissions2 ms0-10-910+1010
Scenario: Create with permissions and a role0 ms001313
Scenario: Create with permissions and a role in the wrong scope1 ms0-40-910+1010-3
Scenario: Creating index with regular user0.11 sec5+524+240-2529+4
Scenario: Creating new device and tagging it with specific Tag40 ms3+213016+2
Scenario: Creating new device, tagging it with specific Tag and then deleting this Tag36 ms3+215018+2
Scenario: Creating tag20 ms2+26+60-78+1
Scenario: Creating two indexes with daily index0.13 sec5+316+140-1321+4
Scenario: Creating two indexes with hourly index0.14 sec5+316+140-1321+4
Scenario: Creating two indexes with weekly index0.12 sec5+516+160-1721+4
Scenario: Creating user44 ms0-10-45+55
Scenario: Creation of access role with neither acess info and role entities0 ms0-50-78+88-4
Scenario: Creation of access role without an acess info entity0 ms0-40-78+88-3
Scenario: D1 Device publish to CTRL_ACC_REPLY35 ms3+28011+2
Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI35 ms3+18+30-211+2
Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed36 ms3+18+30-211+2
Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed38 ms3+14+40-37+2
Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY33 ms3+18+30-211+2
Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY42 ms3+18+30-211+2
Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account35 ms3+18+50-411+2
Scenario: D5 Device subscribe - publish - admin on CTRL_ACC60 ms3+18+30-211+2
Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI34 ms3+18+30-211+2
Scenario: D7 Device publish to ACL_DATA_ACC is not allowed35 ms3+18+30-211+2
Scenario: D8 Device create sub-topic on ACL_DATA_ACC is not allowed34 ms3+18+60-511+2
Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed39 ms3+17+50-410+2
Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed47 ms3+28011+2
Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI42 ms3+28011+2
Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed41 ms3+18+30-211+2
Scenario: DM13 Data manage subscribe on ACL_CTRL_ACC_NOTIFY is not allowed45 ms3+37+70-810+2
Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY45 ms3+28011+2
Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY37 ms3+28011+2
Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account36 ms3+28011+2
Scenario: DM5 Data manage publish to CTRL_ACC is not allowed35 ms3+28011+2
Scenario: DM6 Data manage create sub-topic on CTRL_ACC is not allowed33 ms3+18+30-211+2
Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed33 ms3+17+40-310+2
Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI45 ms3+18+30-211+2
Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC34 ms3+28011+2
Scenario: DV1 Data view publish to CTRL_ACC_REPLY35 ms3+38+80-911+2
Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed30 ms3+28011+2
Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed30 ms3+29012+2
Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed33 ms3+28011+2
Scenario: DV13 Data view create sub-topic on ACL_CTRL_ACC_CLI is not allowed29 ms3+28011+2
Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed29 ms3+18+30-211+2
Scenario: DV17 Data view subscribe on ACL_CTRL_ACC_NOTIFY is not allowed35 ms3+27010+2
Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY31 ms3+18+30-211+2
Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY27 ms3+18+30-211+2
Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account31 ms3+38+80-911+2
Scenario: DV5 Data view publish to CTRL_ACC is not allowed31 ms3+18+30-211+2
Scenario: DV6 Data view create sub-topic on CTRL_ACC is not allowed30 ms3+18+30-211+2
Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed29 ms3+37+70-810+2
Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI30 ms3+18+30-211+2
Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed30 ms3+18+30-211+2
Scenario: Delete Kapua system user16 ms0-10-45+55
Scenario: Delete a access info entity with permissions and roles0 ms0099
Scenario: Delete a connection from the database12 ms0-30-67+77-2
Scenario: Delete a group from the database0 ms0-30-56+66-2
Scenario: Delete a group from the database - Unknown group ID0 ms0-30-34+44-2
Scenario: Delete a job19 ms0-50-78+88-4
Scenario: Delete a job execution item17 ms0-50-56+66-4
Scenario: Delete a job execution item twice18 ms0-50-67+77-4
Scenario: Delete a job target6 ms0-50-56+66-4
Scenario: Delete a job target twice9 ms0-50-67+77-4
Scenario: Delete a job twice14 ms0-50-67+77-4
Scenario: Delete a non existent event11 ms0-10-1011+1111
Scenario: Delete a non existing connection4 ms0-30-56+66-2
Scenario: Delete a non existing permission entity0 ms0-40-1112+1212-3
Scenario: Delete a non existing role entry0 ms0-50-78+88-4
Scenario: Delete a non-existing step11 ms0-50-89+99-4
Scenario: Delete a nonexistent domain0 ms0-30-34+44-2
Scenario: Delete a step definition12 ms0-50-78+88-4
Scenario: Delete a step definition twice8 ms0-50-67+77-4
Scenario: Delete an access info entity twice0 ms0-10-78+88
Scenario: Delete an access info entity using the wrong scope ID0 ms0088
Scenario: Delete an existing access info entity0 ms0099
Scenario: Delete an existing access permission entity1 ms0-40-1011+1111-3
Scenario: Delete an existing access role entry0 ms0-30-1718+1818-2
Scenario: Delete an existing account3 ms0-10-45+55
Scenario: Delete an existing device from the registry8 ms0044
Scenario: Delete an existing event14 ms0-10-1213+1313
Scenario: Delete an existing role0 ms0-50-45+55-4
Scenario: Delete an existing role twice1 ms0-40-1011+1111-3
Scenario: Delete an existing step8 ms0-50-78+88-4
Scenario: Delete items based on query results0.31 sec10+982+410-4292+8
Scenario: Delete items by the datastore ID0.34 sec10+964+320-3374+8
Scenario: Delete middle child expiration12 ms2+214+140-1516+1
Scenario: Delete nonexisting account3 ms0-10-34+44
Scenario: Delete nonexisting role permission0 ms001010
Scenario: Delete parent expiration29 ms2+213+130-1415+1
Scenario: Delete role permissions1 ms0-10-67+77
Scenario: Delete the Kapua system account3 ms0-10-45+55
Scenario: Delete the last created domain entry0 ms0-50-67+77-4
Scenario: Delete user6 ms0-10-56+66
Scenario: Delete user that doesn't exist3 ms0-10-45+55
Scenario: Deleting tag19 ms2+26+60-78+1
Scenario: Deleting user in account that is higher in hierarchy12 ms2+222+220-2324+1
Scenario: Deleting user in account that is lower in hierarchy9 ms2+223+230-2425+1
Scenario: Device connection update9 ms0066
Scenario: Device factory sanity checks5 ms0022
Scenario: Device queries8 ms001313
Scenario: Device query - find by BIOS version7 ms0077
Scenario: Domain entry query1 ms0-30-34+44-2
Scenario: Domain with null actions1 ms0-40-34+44-3
Scenario: Domain with null name0 ms0-50-34+44-4
Scenario: Domains with duplicate names0 ms0-40-67+77-3
Scenario: Duplicate group name in root scope0 ms0-40-78+88-3
Scenario: Duplicate role names0 ms0-40-34+44-3
Scenario: Empty query results are supported0 ms0055
Scenario: Event factory sanity checks8 ms0066
Scenario: Event service domain check9 ms0066
Scenario: Every account must have the default configuration items3 ms0-10-23+33
Scenario: Extra long continuous test with multiple subscenarios with LOOSE default connection mode0.1 sec4+4417+4170-418421+3
Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode0.27 sec4+4395+3950-396399+3
Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode and no previously defined devices0.35 sec4+4303+3030-304307+3
Scenario: Find a connection by its IDs9 ms0055
Scenario: Find a connection by its client ID8 ms0-10-45+55
Scenario: Find a group entry in the database1 ms0-40-67+77-3
Scenario: Find a non existing event13 ms0-10-910+1010
Scenario: Find account by Id5 ms0-20-24+44
Scenario: Find account by Ids5 ms0-10-34+44
Scenario: Find account by name4 ms0-10-34+44
Scenario: Find account by random Id6 ms0-10-23+33
Scenario: Find all child accounts10 ms0-10-23+33
Scenario: Find an access info entity0 ms0088
Scenario: Find an access info entity by user ID0 ms0077
Scenario: Find an event by its ID12 ms0-20-710+910
Scenario: Find an existing access role entity0 ms0-50-89+99-4
Scenario: Find by name nonexisting account5 ms0-10-23+33
Scenario: Find device by client ID11 ms0033
Scenario: Find device by registry ID11 ms0044
Scenario: Find last created permision1 ms0-50-78+88-4
Scenario: Find multiple users4 ms0-10-45+55
Scenario: Find role by ID0 ms0-40-34+44-3
Scenario: Find the last created domain entry0 ms0-40-34+44-3
Scenario: Find user by id11 ms0-10-45+55
Scenario: Find user by name4 ms0-10-45+55
Scenario: Find user by name that doesn't exist8 ms0-10-23+33
Scenario: Find user with id and scope id that doesn't exist7 ms0-10-23+33
Scenario: Generic connection query9 ms0-30-67+77-2
Scenario: Get metadata3 ms0-10-23+33
Scenario: Group with a null name0 ms0-40-45+55-3
Scenario: Handle account creation50 ms0-10-23+33
Scenario: Handle duplicate account names6 ms0-10-45+55
Scenario: Handle null account name7 ms0-10-34+44
Scenario: Handling of 2 birth messages41 ms3+211014+2
Scenario: Handling of a disconnect message from a non existing device35 ms3+39+90-1012+2
Scenario: I try to find a non-existing connection7 ms0055
Scenario: If user credential expiration date is before today, user can not login10 ms2+213+130-1415+1
Scenario: If user credential expiration date is today, user can not login it is day inclusive9 ms2+213+130-1415+1
Scenario: If user credential expiration date is tomorrow, user can login9 ms2+212+120-1314+1
Scenario: If user credential is in state disabled, user can not login10 ms2+213+130-1415+1
Scenario: If user credential is in state enabled, user can login8 ms2+212+120-1314+1
Scenario: If user expiration date is before today, user can not login9 ms2+212+120-1314+1
Scenario: If user expiration date is today, user can not login because expiration date was reached10 ms2+212+120-1314+1
Scenario: If user expiration date is tomorrow, user can login13 ms2+211+110-1213+1
Scenario: Installing a package42 ms3+212015+2
Scenario: It is possible to change the configuration items3 ms0-10-34+44
Scenario: It must be possible to query for specific entries in the role database0 ms0055
Scenario: Job execution factory sanity checks12 ms0-50-12+22-4
Scenario: Job factory sanity checks8 ms0-50-23+33-4
Scenario: Job target factory sanity checks10 ms0-50-12+22-4
Scenario: Job with a duplicate name13 ms0-40-56+66-3
Scenario: Job with a null name11 ms0-30-45+55-2
Scenario: Job with a null scope ID17 ms0-50-56+66-4
Scenario: Job with an empty name14 ms0-50-56+66-4
Scenario: MetricsInfo client ID and topic data based on the client id0.26 sec10+932+160-1742+8
Scenario: MetricsInfo last published date0.24 sec10+946+230-2456+8
Scenario: Modify a role that was deleted0 ms0-50-56+66-4
Scenario: Modify an existing account3 ms0-10-34+44
Scenario: Modify last child expiration so that it still expires before parent33 ms2+213+130-1415+1
Scenario: Modify middle child expiration so that it still expires before parent33 ms2+213+130-1415+1
Scenario: Modify middle child expiration to outlive parent18 ms2+214+140-1516+1
Scenario: Modify nonexisting account3 ms0-10-56+66
Scenario: Modify parent expiration so that it still expires after child29 ms2+213+130-1415+1
Scenario: Modify parent expiration to before child expiration31 ms2+214+140-1516+1
Scenario: Nameless role entry0 ms0-50-34+44-4
Scenario: Negative scenario when client connects twice with same client id57 ms3+110+20-113+2
Scenario: New connection with reserved ID78 ms4+432+320-3336+3
Scenario: Permission factory sanity checks0 ms0-50-23+33-4
Scenario: Positive scenario without stealing link51 ms3+211014+2
Scenario: Query based on message ordering0.25 sec10+918+90-1028+8
Scenario: Query based on metrics ordering0.28 sec10+918+90-1028+8
Scenario: Query before schema search0.25 sec10+980+400-4190+8
Scenario: Query for a specific group by name1 ms0-30-1314+1414-2
Scenario: Query for all the access info entities of a specific user0 ms0-50-1415+1515-4
Scenario: Query for all the access info entities of an invalid user0 ms0-40-67+77-3
Scenario: Query for executions of a specific job15 ms0-50-1516+1616-4
Scenario: Query for jobs with specified name12 ms0-50-56+66-4
Scenario: Query for step definitions15 ms0-50-67+77-4
Scenario: Query for the targets of a specific job15 ms0-50-1819+1919-4
Scenario: Query user4 ms0-10-56+66
Scenario: Regular connection8 ms0066
Scenario: Regular creation of Access Role entity1 ms0-40-910+1010-3
Scenario: Regular domain0 ms0-40-34+44-3
Scenario: Regular group in random scope0 ms0-50-45+55-4
Scenario: Regular group in root scope1 ms0-40-45+55-3
Scenario: Regular job creation15 ms0-50-67+77-4
Scenario: Regular job execution creation27 ms0-50-45+55-4
Scenario: Regular role creation0 ms0-40-56+66-3
Scenario: Regular step creation12 ms0-50-78+88-4
Scenario: Regular step definition creation14 ms0-50-67+77-4
Scenario: Regular step definition with a property list12 ms0-50-34+44-4
Scenario: Regular target creation15 ms0-50-45+55-4
Scenario: Role creator sanity checks0 ms0022
Scenario: Role entry with no actions0 ms0-30-34+44-2
Scenario: Role object equality check0 ms0022
Scenario: Role service related objects sanity checks0 ms0044
Scenario: Search for a non existent client ID13 ms0-10-45+55
Scenario: Search for an access info entity by an incorrect user ID0 ms0088
Scenario: Search the role database for a random ID0 ms0-40-34+44-3
Scenario: Send BIRTH message and then DC message56 ms3+214017+2
Scenario: Send BIRTH message and then DC message while broker ip is NOT set49 ms3+15+50-48+2
Scenario: Send BIRTH message and then DC message while broker ip is set by System49 ms3+37+70-810+2
Scenario: Send BIRTH message and then DC message while broker ip is set by config file68 ms3+27010+2
Scenario: Setting configuration without mandatory items must raise an error4 ms0-10-45+55
Scenario: Simple create1 ms0-50-67+77-4
Scenario: Simple positive scenario for creating daily index0.12 sec5+313+120-1118+4
Scenario: Simple positive scenario for creating default - weekly index0.14 sec5+511+110-1216+4
Scenario: Simple positive scenario for creating hourly index0.12 sec5+313+120-1118+4
Scenario: Start broker for all scenarios51 sec74+582+20-776+53
Scenario: Start datastore for all scenarios2 min 41 sec52+342+20-654+30
Scenario: Start event broker for all scenarios1.7 sec49+422+20-1051+34
Scenario: Starting and stopping the simulator should create a device entry and properly set its status46 ms3+119+50-422+2
Scenario: Stealing link scenario50 ms3+127+30-230+2
Scenario: Step definition factory sanity checks25 ms0-50-12+22-4
Scenario: Step definition with a duplicate name21 ms0-50-56+66-4
Scenario: Step definition with a null name9 ms0-50-56+66-4
Scenario: Step definition with a null scope ID9 ms0-50-56+66-4
Scenario: Step definition with an empty name8 ms0-50-45+55-4
Scenario: Step factory sanity checks8 ms0-50-12+22-4
Scenario: Step with a null scope ID9 ms0-50-78+88-4
Scenario: Stop broker after all scenarios4.7 sec56+492+20-1158+40
Scenario: Stop datastore after all scenario37 ms3+300-13+2
Scenario: Stop datastore after all scenarios0.87 sec49+422+20-951+35
Scenario: Stop event broker after all scenarios79 ms6+500-16+4
Scenario: Stop event broker for all scenarios0.83 sec45+412+20-1147+32
Scenario: Target with a null scope ID9 ms0-50-45+55-4
Scenario: Test LOOSE user coupling on single connection85 ms4+426+260-2730+3
Scenario: Test LOOSE user coupling with 3 connections90 ms4+436+360-3740+3
Scenario: Test STRICT user coupling on single connection87 ms4+423+230-2427+3
Scenario: Test STRICT user coupling with 3 connections and a reserved user85 ms4+461+610-6265+3
Scenario: Test STRICT user coupling with user change allowed on single connection79 ms4+434+340-3538+3
Scenario: Test account query2 ms0-10-34+44
Scenario: Test the message store with server timestamp indexing0.26 sec10+924+120-1334+8
Scenario: Test the message store with timestamp indexing0.25 sec10+924+120-1334+8
Scenario: The Client ID is case sensitive5 ms0-20-67+77-1
Scenario: To be defined8 ms2+2150-117+1
Scenario: Try to change an existing connection ID9 ms0066
Scenario: Try to create an access into entity with an invalid role id0 ms0088
Scenario: Try to delete a non existing device from the registry7 ms0044
Scenario: Try to find a device with an invalid client ID7 ms0033
Scenario: Try to find a device with an invalid registry ID9 ms0033
Scenario: Try to modify the connection client ID10 ms0066
Scenario: Try to update the device client ID9 ms0044
Scenario: Unknown configuiration items are silently ignored3 ms0-10-34+44
Scenario: Update a group entry in the database0 ms0-40-67+77-3
Scenario: Update a group entry with a false ID0 ms0-40-78+88-3
Scenario: Update a job XML definition12 ms0-50-67+77-4
Scenario: Update a job description21 ms0-50-67+77-4
Scenario: Update a job name12 ms0-50-67+77-4
Scenario: Update a job target TargetId9 ms0-50-56+66-4
Scenario: Update a job target status8 ms0-50-67+77-4
Scenario: Update a job target step index8 ms0-50-45+55-4
Scenario: Update a non existing device11 ms0055
Scenario: Update a nonexistent job11 ms0-40-67+77-3
Scenario: Update a nonexistent step definition14 ms0-50-67+77-4
Scenario: Update a step definition name8 ms0-50-67+77-4
Scenario: Update a step definition processor name7 ms0-50-78+88-4
Scenario: Update a step definition target type9 ms0-50-78+88-4
Scenario: Update an existing device10 ms0044
Scenario: Update existing role name0 ms0-30-45+55-2
Scenario: Update job id of an existing execution item33 ms0066
Scenario: Update the end time of an existing execution item22 ms0-50-67+77-4
Scenario: Update user4 ms0-10-67+77
Scenario: Update user that doesn't exist2 ms0-10-45+55
Scenario: User locking itself out by using out login attempts10 ms2+215+150-1617+1
Scenario: User locking itself out with failed attempts and not waiting to unlock22 ms2+216+160-1718+1
Scenario: User locking itself out with failed attempts and waiting to unlock23 ms2+216+160-1718+1
Scenario: User login with wrong pass, but with enough time between login failures21 ms2+218+180-1920+1
Scenario: User not locking itself out by using less than max failed login attempts22 ms2+216+160-1718+1
Scenario: Validate a device client based search with a null client ID9 ms0-20-34+44-1
Scenario: Validate a device client based search with an empty client ID6 ms0-20-34+44-1
Scenario: Validate a device client search with null scope8 ms0-10-34+44
Scenario: Validate a device count with a null Scope ID7 ms0-30-45+55-2
Scenario: Validate a device creator with a null client ID9 ms0-30-56+66-2
Scenario: Validate a device creator with a null scope ID6 ms0-30-56+66-2
Scenario: Validate a device query with a null Scope ID6 ms0-20-45+55-1
Scenario: Validate a device search with a null device ID7 ms0-30-34+44-2
Scenario: Validate a device search with a null scope ID8 ms0-20-34+44-1
Scenario: Validate a null creator7 ms0-20-45+55-1
Scenario: Validate a null device13 ms0-10-45+55
Scenario: Validate a null device count4 ms0-30-45+55-2
Scenario: Validate a null device query15 ms0-20-45+55-1
Scenario: Validate a regular creator7 ms0-30-34+44-2
Scenario: Validate a regular device8 ms0-30-34+44-2
Scenario: Validate a regular device client search8 ms0-30-23+33-2
Scenario: Validate a regular device count9 ms0-30-34+44-2
Scenario: Validate a regular device deletion8 ms0-20-23+33-1
Scenario: Validate a regular device query3 ms0-30-34+44-2
Scenario: Validate a regular device search7 ms0-30-23+33-2
Scenario: Validate deleting a device with a null device ID10 ms0-20-34+44-1
Scenario: Validate deleting a device with a null scope ID8 ms0-20-34+44-1
empty) scope0 ms00-88+88