Test Result : (root)

122 failures (±0) , 1,349 skipped (±0)
4,824 tests (±0)
Took 4.3 sec.

All Failed Tests

Test NameDurationAge
 Scenario: B1 Broker publish to CTRL_ACC_REPLY.Scenario: B1 Broker publish to CTRL_ACC_REPLY5 ms22
 Scenario: B1 Broker publish to CTRL_ACC_REPLY.Then Broker receives string "Hello broker" on topic "$EDC/acme/client-1/CONF-V1/REPLY"5 ms22
 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 allowed3 ms22
 Scenario: B10 Broker create sub-topic on ACL_DATA_ACC is not allowed.Then Broker doesn't receive string "Hello broker" on topic "acme/foo"2 ms22
 Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed.Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed4 ms22
 Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed.Then An exception was thrown2 ms22
 Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed2 ms22
 Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed.Then Broker receives string "Hello broker" on topic "$EDC/acme/foo/bar/NOTIFY/client-1"1 ms22
 Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed2 ms22
 Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Then An exception was thrown1 ms22
 Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY.Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY4 ms22
 Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY.Then Broker receives string "Hello broker" on topic "$EDC/acme/client-1/CONF-V1/REPLY/foo"2 ms22
 Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account.Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account2 ms22
 Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account.Then An exception was thrown2 ms22
 Scenario: B7 Broker subscribe on CTRL_ACC is not allowed.Scenario: B7 Broker subscribe on CTRL_ACC is not allowed4 ms22
 Scenario: B7 Broker subscribe on CTRL_ACC is not allowed.Then An exception was thrown3 ms22
 Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed.Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed2 ms22
 Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed.Then Broker doesn't receive string "Hello broker" on topic "acme"2 ms22
 Scenario: Connect to the system and publish some data.Scenario: Connect to the system and publish some data8 ms22
 Scenario: Connect to the system and publish some data.Then Device sim-1 for account kapua-sys is registered after 5 seconds6 ms22
 Scenario: D1 Device publish to CTRL_ACC_REPLY.Scenario: D1 Device publish to CTRL_ACC_REPLY3 ms22
 Scenario: D1 Device publish to CTRL_ACC_REPLY.Then Broker receives string "Hello broker" on topic "$EDC/acme/client-1/CONF-V1/REPLY"2 ms22
 Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed3 ms22
 Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed.Then Broker receives string "Hello broker" on topic "$EDC/acme/foo/bar/NOTIFY/client-1"2 ms22
 Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY.Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY3 ms22
 Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY.Then Broker receives string "Hello broker" on topic "$EDC/acme/client-1/CONF-V1/REPLY/foo"2 ms22
 Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account.Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account2 ms22
 Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account.Then An exception was thrown1 ms22
 Scenario: D7 Device publish to ACL_DATA_ACC is not allowed.Scenario: D7 Device publish to ACL_DATA_ACC is not allowed3 ms22
 Scenario: D7 Device publish to ACL_DATA_ACC is not allowed.Then Broker doesn't receive string "Hello broker" on topic "acme"2 ms22
 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 allowed4 ms22
 Scenario: D8 Device create sub-topic on ACL_DATA_ACC is not allowed.Then Broker doesn't receive string "Hello broker" on topic "acme/foo"2 ms22
 Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed.Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed1 ms22
 Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed.Then An exception was thrown1 ms22
 Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed.Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed7 ms22
 Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed.Then Broker receives string "Hello broker" on topic "$EDC/acme/client-1/CONF-V1/REPLY"5 ms22
 Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed4 ms22
 Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed.Then Broker receives string "Hello broker" on topic "$EDC/acme/foo/bar/NOTIFY/client-1"3 ms22
 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 allowed2 ms22
 Scenario: DM13 Data manage subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Then An exception was thrown1 ms22
 Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY.Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY6 ms22
 Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY.Then Broker receives string "Hello broker" on topic "$EDC/acme/client-1/CONF-V1/REPLY/foo"4 ms22
 Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account.Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account4 ms22
 Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account.Then An exception was thrown3 ms22
 Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed.Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed3 ms22
 Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed.Then An exception was thrown2 ms22
 Scenario: DV1 Data view publish to CTRL_ACC_REPLY.Scenario: DV1 Data view publish to CTRL_ACC_REPLY3 ms22
 Scenario: DV1 Data view publish to CTRL_ACC_REPLY.Then Broker receives string "Hello broker" on topic "$EDC/acme/client-1/CONF-V1/REPLY"2 ms22
 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 allowed2 ms22
 Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed.Then Broker doesn't receive string "Hello broker" on topic "acme/foo"1 ms22
 Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed4 ms22
 Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed.Then Broker receives string "Hello broker" on topic "$EDC/acme/foo/bar/NOTIFY/client-1"3 ms22
 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 allowed1 ms22
 Scenario: DV17 Data view subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Then An exception was thrown0 ms22
 Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY.Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY2 ms22
 Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY.Then Broker receives string "Hello broker" on topic "$EDC/acme/client-1/CONF-V1/REPLY/foo"1 ms22
 Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account.Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account3 ms22
 Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account.Then An exception was thrown2 ms22
 Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed.Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed2 ms22
 Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed.Then An exception was thrown1 ms22
 Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed.Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed3 ms22
 Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed.Then Broker doesn't receive string "Hello broker" on topic "acme"2 ms22
 Scenario: Extra long continuous test with multiple subscenarios with LOOSE default connection mode.And The connection status is "CONNECTED"2 ms22
 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 mode3 ms22
 Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode.And The connection status is "CONNECTED"2 ms22
 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 mode3 ms22
 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 devices3 ms22
 Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode and no previously defined devices.Then I find 1 connection2 ms22
 Scenario: Installing a package.Scenario: Installing a package4 ms22
 Scenario: Installing a package.Then Device sim-1 for account kapua-sys is registered after 5 seconds2 ms22
 Scenario: New connection with reserved ID.And The connection status is "CONNECTED"2 ms22
 Scenario: New connection with reserved ID.Scenario: New connection with reserved ID4 ms22
 Scenario: Send BIRTH message and then DC message.And Bundles are requested1 ms22
 Scenario: Send BIRTH message and then DC message.Scenario: Send BIRTH message and then DC message2 ms22
 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 System7 ms22
 Scenario: Send BIRTH message and then DC message while broker ip is set by System.Then Device is connected with "localhost" server ip4 ms22
 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 file2 ms22
 Scenario: Send BIRTH message and then DC message while broker ip is set by config file.Then Device is connected with "localhost" server ip1 ms22
 Scenario: Start broker for all scenarios.Given Start Broker2 ms22
 Scenario: Start broker for all scenarios.Given Start Broker16 ms22
 Scenario: Start broker for all scenarios.Given Start Broker2 ms22
 Scenario: Start broker for all scenarios.Given Start Broker1 ms22
 Scenario: Start broker for all scenarios.Given Start Broker2 ms22
 Scenario: Start broker for all scenarios.Given Start Broker0 ms22
 Scenario: Start broker for all scenarios.Given Start Broker2 ms22
 Scenario: Start broker for all scenarios.Given Start Broker3 ms22
 Scenario: Start broker for all scenarios.Given Start Broker2 ms22
 Scenario: Start broker for all scenarios.Given Start Broker2 ms22
 Scenario: Start broker for all scenarios.Given Start Broker2 ms22
 Scenario: Start broker for all scenarios.Given Start Broker2 ms22
 Scenario: Start broker for all scenarios.Given Start Broker3 ms22
 Scenario: Start broker for all scenarios.Given Start Broker3 ms22
 Scenario: Start broker for all scenarios.Given Start Broker2 ms22
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios3 ms22
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios17 ms22
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios4 ms22
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios4 ms22
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios3 ms22
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios3 ms22
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios4 ms22
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms22
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios3 ms22
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios4 ms22
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios3 ms22
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios3 ms22
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios0 ms22
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios3 ms22
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios3 ms22
 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 status4 ms22
 Scenario: Starting and stopping the simulator should create a device entry and properly set its status.Then Device sim-1 for account kapua-sys is registered after 5 seconds3 ms22
 Scenario: Stealing link scenario.And Client named "client-2" is not connected4 ms22
 Scenario: Stealing link scenario.Scenario: Stealing link scenario5 ms22
 Scenario: Test LOOSE user coupling on single connection.And The connection status is "CONNECTED"3 ms22
 Scenario: Test LOOSE user coupling on single connection.Scenario: Test LOOSE user coupling on single connection5 ms22
 Scenario: Test LOOSE user coupling with 3 connections.And The connection status is "CONNECTED"2 ms22
 Scenario: Test LOOSE user coupling with 3 connections.Scenario: Test LOOSE user coupling with 3 connections4 ms22
 Scenario: Test STRICT user coupling on single connection.And The connection status is "CONNECTED"2 ms22
 Scenario: Test STRICT user coupling on single connection.Scenario: Test STRICT user coupling on single connection4 ms22
 Scenario: Test STRICT user coupling with 3 connections and a reserved user.And The connection status is "CONNECTED"3 ms22
 Scenario: Test STRICT user coupling with 3 connections and a reserved user.Scenario: Test STRICT user coupling with 3 connections and a reserved user4 ms22
 Scenario: Test STRICT user coupling with user change allowed on single connection.And The connection status is "CONNECTED"3 ms22
 Scenario: Test STRICT user coupling with user change allowed on single connection.Scenario: Test STRICT user coupling with user change allowed on single connection4 ms22

All Tests

ClassDurationFail(diff)Skip(diff)Pass(diff)Total(diff)
Scenario: A fresh database must contain 1 default role in the root scope1 ms0033
Scenario: A mock test scenario0.51 sec0033
Scenario: A newly created account must have some metadata2 ms0033
Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic3 ms0088
Scenario: Access info service sanity checks1 ms0044
Scenario: Access service comparison sanity checks0 ms0033
Scenario: Account based ClientInfo data check9 ms001212
Scenario: Account exactly on its expiration date8 ms001414
Scenario: Account expiration date test - Parent and child expiration set, then parent expiration date changed to before child expiration date2 ms0066
Scenario: Account expiration date test - Parent expiration set, child expiration after father expiration3 ms0066
Scenario: Account expiration date test - Parent expiration set, child expiration before father expiration2 ms0055
Scenario: Account expiration date test - Parent expiration set, child expiration null3 ms0066
Scenario: Account name must not be mutable3 ms0066
Scenario: Account past its expiration date6 ms001414
Scenario: Account wide metrics check8 ms001414
Scenario: Account with future expiration date4 ms001313
Scenario: Account with no expiration date1 ms001313
Scenario: All device parameters must match the device creator7 ms0033
Scenario: B1 Broker publish to CTRL_ACC_REPLY10 ms2259
Scenario: B10 Broker create sub-topic on ACL_DATA_ACC is not allowed5 ms2259
Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed6 ms2248
Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI1 ms0099
Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed4 ms2259
Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed3 ms2248
Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY8 ms2259
Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY3 ms0099
Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account4 ms2259
Scenario: B5 Broker publish to CTRL_ACC is not allowed3 ms0099
Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed1 ms0099
Scenario: B7 Broker subscribe on CTRL_ACC is not allowed7 ms2248
Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI2 ms0099
Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed4 ms2259
Scenario: Basic Device Event queries8 ms001414
Scenario: Birth and applications event handling4 ms001212
Scenario: Birth and death message handling9 ms001212
Scenario: Birth and missing event handling8 ms001212
Scenario: Birth message handling from a new device5 ms001313
Scenario: Birth message handling from an existing device5 ms001212
Scenario: Both the parent and child accounts do not expire4 ms001111
Scenario: Both the parent and child accounts have the same expiration date2 ms001111
Scenario: Captured date based ClientInfo data check12 ms001515
Scenario: Case sensitivness of named device searches10 ms0033
Scenario: Change an existing step name14 ms0088
Scenario: Change the account parent Id3 ms0055
Scenario: Change the account parent path4 ms0055
Scenario: Channel info queries based on datastore channel filters8 ms002525
Scenario: ChannelInfo client ID and topic data based on the client id12 ms001414
Scenario: ChannelInfo client ID based on the account id16 ms001313
Scenario: ChannelInfo last published date15 ms001515
Scenario: ChannelInfo topic data based on the account id8 ms001313
Scenario: Check account properties3 ms0044
Scenario: Check the Device Connection Domain data seetting6 ms0022
Scenario: Check the database cache coherency11 ms001515
Scenario: Check the mapping for message semantic topics10 ms001515
Scenario: Check the message store10 ms001010
Scenario: Check the sanity of the Device Connection Domain data initialization7 ms0022
Scenario: Child account expires after parent6 ms0099
Scenario: Child account expires before parent3 ms001111
Scenario: Child account has null expiration date2 ms0099
Scenario: Client Id based ClientInfo data check10 ms001414
Scenario: Compare domain entries0 ms0022
Scenario: Connect to the system and publish some data14 ms215522
Scenario: Connection Service factory sanity checks3 ms0022
Scenario: Count access info entities in a specific scope0 ms001919
Scenario: Count access role entities by scope1 ms003333
Scenario: Count connections in empty scope6 ms0044
Scenario: Count connections in scope8 ms0055
Scenario: Count devices in a specific scope8 ms001111
Scenario: Count devices with a specific BIOS version9 ms0066
Scenario: Count domains in a blank database0 ms0033
Scenario: Count domains in the database0 ms0066
Scenario: Count events in empty scope9 ms001010
Scenario: Count events in scope16 ms001414
Scenario: Count groups0 ms001212
Scenario: Count groups in a blank database1 ms0033
Scenario: Count job items14 ms0044
Scenario: Count job items in wrong (empty) scope11 ms0011
Scenario: Count role permissions in specific scopes0 ms001515
Scenario: Count roles in specific scopes0 ms001313
Scenario: Count step definition items10 ms0044
Scenario: Count step definitions in wrong (empty) scope11 ms0011
Scenario: Count steps in the database12 ms001111
Scenario: Count user5 ms0066
Scenario: Create a regular event21 ms001010
Scenario: Create a single device16 ms0044
Scenario: Create an event with a null action19 ms001111
Scenario: Create an event with a null scope ID14 ms001010
Scenario: Create and count multiple job targets13 ms0088
Scenario: Create and count several execution items for a job19 ms0099
Scenario: Create index with specific prefix9 ms001313
Scenario: Create multiple users2 ms0055
Scenario: Create regular access permissions0 ms001515
Scenario: Create some regular role permissions0 ms0066
Scenario: Create user that already exist2 ms0077
Scenario: Create user that has more than DB allowed length4 ms0055
Scenario: Create user with short name9 ms0055
Scenario: Create user with special characters in his name7 ms0055
Scenario: Create with permissions0 ms001010
Scenario: Create with permissions and a role0 ms001313
Scenario: Create with permissions and a role in the wrong scope0 ms001010
Scenario: Creating index with regular user14 ms002525
Scenario: Creating new device and tagging it with specific Tag8 ms001414
Scenario: Creating new device, tagging it with specific Tag and then deleting this Tag5 ms001616
Scenario: Creating tag5 ms0077
Scenario: Creating two indexes with daily index19 ms001717
Scenario: Creating two indexes with hourly index12 ms001717
Scenario: Creating two indexes with weekly index12 ms001717
Scenario: Creating user68 ms0055
Scenario: Creation of access role with neither acess info and role entities0 ms0088
Scenario: Creation of access role without an acess info entity0 ms0088
Scenario: D1 Device publish to CTRL_ACC_REPLY5 ms2259
Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI5 ms0099
Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed5 ms2259
Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed3 ms0077
Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY5 ms2259
Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY2 ms0099
Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account3 ms2259
Scenario: D5 Device subscribe - publish - admin on CTRL_ACC3 ms0099
Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI5 ms0099
Scenario: D7 Device publish to ACL_DATA_ACC is not allowed5 ms2259
Scenario: D8 Device create sub-topic on ACL_DATA_ACC is not allowed6 ms2259
Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed2 ms2248
Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed12 ms2259
Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI3 ms0099
Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed7 ms2259
Scenario: DM13 Data manage subscribe on ACL_CTRL_ACC_NOTIFY is not allowed4 ms2248
Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY10 ms2259
Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY7 ms0099
Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account7 ms2259
Scenario: DM5 Data manage publish to CTRL_ACC is not allowed6 ms0099
Scenario: DM6 Data manage create sub-topic on CTRL_ACC is not allowed4 ms0099
Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed5 ms2248
Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI6 ms0099
Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC3 ms0099
Scenario: DV1 Data view publish to CTRL_ACC_REPLY5 ms2259
Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed3 ms2259
Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed3 ms001010
Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed3 ms0099
Scenario: DV13 Data view create sub-topic on ACL_CTRL_ACC_CLI is not allowed4 ms0099
Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed7 ms2259
Scenario: DV17 Data view subscribe on ACL_CTRL_ACC_NOTIFY is not allowed3 ms2248
Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY3 ms2259
Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY4 ms0099
Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account5 ms2259
Scenario: DV5 Data view publish to CTRL_ACC is not allowed2 ms0099
Scenario: DV6 Data view create sub-topic on CTRL_ACC is not allowed3 ms0099
Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed3 ms2248
Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI4 ms0099
Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed5 ms2259
Scenario: Delete Kapua system user4 ms0055
Scenario: Delete a access info entity with permissions and roles2 ms0099
Scenario: Delete a connection from the database4 ms0077
Scenario: Delete a group from the database0 ms0066
Scenario: Delete a group from the database - Unknown group ID0 ms0044
Scenario: Delete a job21 ms0088
Scenario: Delete a job execution item21 ms0066
Scenario: Delete a job execution item twice22 ms0077
Scenario: Delete a job target11 ms0066
Scenario: Delete a job target twice8 ms0077
Scenario: Delete a job twice18 ms0077
Scenario: Delete a non existent event10 ms001111
Scenario: Delete a non existing connection9 ms0066
Scenario: Delete a non existing permission entity0 ms001212
Scenario: Delete a non existing role entry0 ms0088
Scenario: Delete a non-existing step10 ms0099
Scenario: Delete a nonexistent domain0 ms0044
Scenario: Delete a step definition11 ms0088
Scenario: Delete a step definition twice9 ms0077
Scenario: Delete an access info entity twice2 ms0088
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 ms001111
Scenario: Delete an existing access role entry0 ms001818
Scenario: Delete an existing account3 ms0055
Scenario: Delete an existing device from the registry8 ms0044
Scenario: Delete an existing event11 ms001313
Scenario: Delete an existing role0 ms0055
Scenario: Delete an existing role twice0 ms001111
Scenario: Delete an existing step12 ms0088
Scenario: Delete items based on query results10 ms004242
Scenario: Delete items by the datastore ID11 ms003333
Scenario: Delete middle child expiration1 ms001515
Scenario: Delete nonexisting account4 ms0044
Scenario: Delete nonexisting role permission1 ms001010
Scenario: Delete parent expiration2 ms001414
Scenario: Delete role permissions1 ms0077
Scenario: Delete the Kapua system account1 ms0055
Scenario: Delete the last created domain entry0 ms0077
Scenario: Delete user5 ms0066
Scenario: Delete user that doesn't exist6 ms0055
Scenario: Deleting tag3 ms0077
Scenario: Deleting user in account that is higher in hierarchy3 ms002323
Scenario: Deleting user in account that is lower in hierarchy4 ms002424
Scenario: Device connection update7 ms0066
Scenario: Device factory sanity checks17 ms0022
Scenario: Device queries7 ms001313
Scenario: Device query - find by BIOS version6 ms0077
Scenario: Domain entry query0 ms0044
Scenario: Domain with null actions0 ms0044
Scenario: Domain with null name0 ms0044
Scenario: Domains with duplicate names1 ms0077
Scenario: Duplicate group name in root scope1 ms0088
Scenario: Duplicate role names0 ms0044
Scenario: Empty query results are supported0 ms0055
Scenario: Event factory sanity checks10 ms0066
Scenario: Event service domain check10 ms0066
Scenario: Every account must have the default configuration items2 ms0033
Scenario: Extra long continuous test with multiple subscenarios with LOOSE default connection mode6 ms240412418
Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode6 ms238212396
Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode and no previously defined devices5 ms22939304
Scenario: Find a connection by its IDs5 ms0055
Scenario: Find a connection by its client ID7 ms0055
Scenario: Find a group entry in the database0 ms0077
Scenario: Find a non existing event9 ms001010
Scenario: Find account by Id4 ms0044
Scenario: Find account by Ids5 ms0044
Scenario: Find account by name4 ms0044
Scenario: Find account by random Id6 ms0033
Scenario: Find all child accounts5 ms0033
Scenario: Find an access info entity0 ms0088
Scenario: Find an access info entity by user ID0 ms0077
Scenario: Find an event by its ID10 ms001010
Scenario: Find an existing access role entity0 ms0099
Scenario: Find by name nonexisting account3 ms0033
Scenario: Find device by client ID10 ms0033
Scenario: Find device by registry ID13 ms0044
Scenario: Find last created permision0 ms0088
Scenario: Find multiple users2 ms0055
Scenario: Find role by ID0 ms0044
Scenario: Find the last created domain entry0 ms0044
Scenario: Find user by id3 ms0055
Scenario: Find user by name3 ms0055
Scenario: Find user by name that doesn't exist4 ms0033
Scenario: Find user with id and scope id that doesn't exist3 ms0033
Scenario: Generic connection query8 ms0077
Scenario: Get metadata2 ms0033
Scenario: Group with a null name0 ms0055
Scenario: Handle account creation58 ms0033
Scenario: Handle duplicate account names5 ms0055
Scenario: Handle null account name5 ms0044
Scenario: Handling of 2 birth messages9 ms001212
Scenario: Handling of a disconnect message from a non existing device5 ms001010
Scenario: I try to find a non-existing connection7 ms0055
Scenario: If user credential expiration date is before today, user can not login5 ms001414
Scenario: If user credential expiration date is today, user can not login it is day inclusive6 ms001414
Scenario: If user credential expiration date is tomorrow, user can login2 ms001313
Scenario: If user credential is in state disabled, user can not login4 ms001414
Scenario: If user credential is in state enabled, user can login4 ms001313
Scenario: If user expiration date is before today, user can not login9 ms001313
Scenario: If user expiration date is today, user can not login because expiration date was reached5 ms001313
Scenario: If user expiration date is tomorrow, user can login7 ms001212
Scenario: Installing a package6 ms27413
Scenario: It is possible to change the configuration items3 ms0044
Scenario: It must be possible to query for specific entries in the role database0 ms0055
Scenario: Job execution factory sanity checks16 ms0022
Scenario: Job factory sanity checks11 ms0033
Scenario: Job target factory sanity checks9 ms0022
Scenario: Job with a duplicate name11 ms0066
Scenario: Job with a null name14 ms0055
Scenario: Job with a null scope ID17 ms0066
Scenario: Job with an empty name17 ms0066
Scenario: MetricsInfo client ID and topic data based on the client id8 ms001717
Scenario: MetricsInfo last published date14 ms002424
Scenario: Modify a role that was deleted0 ms0066
Scenario: Modify an existing account3 ms0044
Scenario: Modify last child expiration so that it still expires before parent2 ms001414
Scenario: Modify middle child expiration so that it still expires before parent2 ms001414
Scenario: Modify middle child expiration to outlive parent2 ms001515
Scenario: Modify nonexisting account3 ms0066
Scenario: Modify parent expiration so that it still expires after child4 ms001414
Scenario: Modify parent expiration to before child expiration2 ms001515
Scenario: Nameless role entry0 ms0044
Scenario: Negative scenario when client connects twice with same client id7 ms001111
Scenario: New connection with reserved ID6 ms2191233
Scenario: Permission factory sanity checks0 ms0033
Scenario: Positive scenario without stealing link5 ms001212
Scenario: Query based on message ordering14 ms001010
Scenario: Query based on metrics ordering10 ms001010
Scenario: Query before schema search11 ms004141
Scenario: Query for a specific group by name0 ms001414
Scenario: Query for all the access info entities of a specific user0 ms001515
Scenario: Query for all the access info entities of an invalid user0 ms0077
Scenario: Query for executions of a specific job16 ms001616
Scenario: Query for jobs with specified name12 ms0066
Scenario: Query for step definitions9 ms0077
Scenario: Query for the targets of a specific job11 ms001919
Scenario: Query user3 ms0066
Scenario: Regular connection7 ms0066
Scenario: Regular creation of Access Role entity0 ms001010
Scenario: Regular domain0 ms0044
Scenario: Regular group in random scope0 ms0055
Scenario: Regular group in root scope0 ms0055
Scenario: Regular job creation23 ms0077
Scenario: Regular job execution creation40 ms0055
Scenario: Regular role creation1 ms0066
Scenario: Regular step creation11 ms0088
Scenario: Regular step definition creation16 ms0077
Scenario: Regular step definition with a property list11 ms0044
Scenario: Regular target creation12 ms0055
Scenario: Role creator sanity checks0 ms0022
Scenario: Role entry with no actions0 ms0044
Scenario: Role object equality check0 ms0022
Scenario: Role service related objects sanity checks0 ms0044
Scenario: Search for a non existent client ID4 ms0055
Scenario: Search for an access info entity by an incorrect user ID2 ms0088
Scenario: Search the role database for a random ID0 ms0044
Scenario: Send BIRTH message and then DC message3 ms27615
Scenario: Send BIRTH message and then DC message while broker ip is NOT set15 ms0066
Scenario: Send BIRTH message and then DC message while broker ip is set by System11 ms2248
Scenario: Send BIRTH message and then DC message while broker ip is set by config file3 ms2248
Scenario: Set environment variables0.13 sec004343
Scenario: Setting configuration without mandatory items must raise an error3 ms0055
Scenario: Simple create0 ms0077
Scenario: Simple positive scenario for creating daily index14 ms001414
Scenario: Simple positive scenario for creating default - weekly index25 ms001212
Scenario: Simple positive scenario for creating hourly index11 ms001414
Scenario: Start broker for all scenarios0.1 sec300232
Scenario: Start datastore for all scenarios0.42 sec003030
Scenario: Start event broker for all scenarios0.18 sec003636
Scenario: Starting and stopping the simulator should create a device entry and properly set its status7 ms214420
Scenario: Stealing link scenario9 ms2141228
Scenario: Step definition factory sanity checks7 ms0022
Scenario: Step definition with a duplicate name7 ms0066
Scenario: Step definition with a null name12 ms0066
Scenario: Step definition with a null scope ID13 ms0066
Scenario: Step definition with an empty name9 ms0055
Scenario: Step factory sanity checks6 ms0022
Scenario: Step with a null scope ID9 ms0088
Scenario: Stop broker after all scenarios0.14 sec003232
Scenario: Stop datastore after all scenarios0.13 sec003030
Scenario: Stop event broker for all scenarios0.14 sec003636
Scenario: Target with a null scope ID11 ms0055
Scenario: Test LOOSE user coupling on single connection7 ms2131227
Scenario: Test LOOSE user coupling with 3 connections6 ms2231237
Scenario: Test STRICT user coupling on single connection6 ms2101224
Scenario: Test STRICT user coupling with 3 connections and a reserved user8 ms2481262
Scenario: Test STRICT user coupling with user change allowed on single connection8 ms2211235
Scenario: Test account query3 ms0044
Scenario: Test the message store with server timestamp indexing10 ms001313
Scenario: Test the message store with timestamp indexing10 ms001313
Scenario: The Client ID is case sensitive8 ms0077
Scenario: To be defined14 ms015116
Scenario: Try to change an existing connection ID6 ms0066
Scenario: Try to create an access into entity with an invalid role id1 ms0088
Scenario: Try to delete a non existing device from the registry10 ms0044
Scenario: Try to find a device with an invalid client ID8 ms0033
Scenario: Try to find a device with an invalid registry ID8 ms0033
Scenario: Try to modify the connection client ID16 ms0066
Scenario: Try to update the device client ID10 ms0044
Scenario: Unknown configuiration items are silently ignored4 ms0044
Scenario: Update a group entry in the database0 ms0077
Scenario: Update a group entry with a false ID0 ms0088
Scenario: Update a job XML definition13 ms0077
Scenario: Update a job description13 ms0077
Scenario: Update a job name18 ms0077
Scenario: Update a job target TargetId8 ms0066
Scenario: Update a job target status10 ms0077
Scenario: Update a job target step index9 ms0055
Scenario: Update a non existing device9 ms0055
Scenario: Update a nonexistent job11 ms0077
Scenario: Update a nonexistent step definition9 ms0077
Scenario: Update a step definition name10 ms0077
Scenario: Update a step definition processor name11 ms0088
Scenario: Update a step definition target type10 ms0088
Scenario: Update an existing device9 ms0044
Scenario: Update existing role name0 ms0055
Scenario: Update job id of an existing execution item27 ms0066
Scenario: Update the end time of an existing execution item23 ms0077
Scenario: Update user20 ms0077
Scenario: Update user that doesn't exist4 ms0055
Scenario: User locking itself out by using out login attempts6 ms001616
Scenario: User locking itself out with failed attempts and not waiting to unlock9 ms001717
Scenario: User locking itself out with failed attempts and waiting to unlock2 ms001717
Scenario: User login with wrong pass, but with enough time between login failures3 ms001919
Scenario: User not locking itself out by using less than max failed login attempts2 ms001717
Scenario: Validate a device client based search with a null client ID6 ms0044
Scenario: Validate a device client based search with an empty client ID6 ms0044
Scenario: Validate a device client search with null scope6 ms0044
Scenario: Validate a device count with a null Scope ID7 ms0055
Scenario: Validate a device creator with a null client ID4 ms0066
Scenario: Validate a device creator with a null scope ID7 ms0066
Scenario: Validate a device query with a null Scope ID5 ms0055
Scenario: Validate a device search with a null device ID6 ms0044
Scenario: Validate a device search with a null scope ID7 ms0044
Scenario: Validate a null creator8 ms0055
Scenario: Validate a null device6 ms0055
Scenario: Validate a null device count9 ms0055
Scenario: Validate a null device query6 ms0055
Scenario: Validate a regular creator5 ms0044
Scenario: Validate a regular device7 ms0044
Scenario: Validate a regular device client search7 ms0033
Scenario: Validate a regular device count3 ms0044
Scenario: Validate a regular device deletion8 ms0033
Scenario: Validate a regular device query6 ms0044
Scenario: Validate a regular device search6 ms0033
Scenario: Validate deleting a device with a null device ID8 ms0044
Scenario: Validate deleting a device with a null scope ID5 ms0044
empty) scope0 ms0088