| Scenario: A fresh database must contain 1 default role in the root scope | 0 ms | 0 | | 0 | | 3 | | 3 | |
| Scenario: A mock test scenario | 0.6 sec | 0 | | 0 | | 3 | | 3 | |
| Scenario: A newly created account must have some metadata | 7 ms | 0 | | 0 | | 3 | | 3 | |
| Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic | 5 ms | 0 | | 0 | | 8 | | 8 | |
| Scenario: Access info service sanity checks | 0 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Access service comparison sanity checks | 1 ms | 0 | | 0 | | 3 | | 3 | |
| Scenario: Account based ClientInfo data check | 11 ms | 0 | | 0 | | 12 | | 12 | |
| Scenario: Account exactly on its expiration date | 3 ms | 0 | | 0 | | 14 | | 14 | |
| Scenario: Account expiration date test - Parent and child expiration set, then parent expiration date changed to before child expiration date | 3 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Account expiration date test - Parent expiration set, child expiration after father expiration | 3 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Account expiration date test - Parent expiration set, child expiration before father expiration | 2 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Account expiration date test - Parent expiration set, child expiration null | 3 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Account name must not be mutable | 2 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Account past its expiration date | 2 ms | 0 | | 0 | | 14 | | 14 | |
| Scenario: Account wide metrics check | 15 ms | 0 | | 0 | | 14 | | 14 | |
| Scenario: Account with future expiration date | 2 ms | 0 | | 0 | | 13 | | 13 | |
| Scenario: Account with no expiration date | 2 ms | 0 | | 0 | | 13 | | 13 | |
| Scenario: All device parameters must match the device creator | 8 ms | 0 | | 0 | | 3 | | 3 | |
| Scenario: B1 Broker publish to CTRL_ACC_REPLY | 7 ms | 2 | +2 | 2 | +2 | 5 | -4 | 9 | |
| Scenario: B10 Broker create sub-topic on ACL_DATA_ACC is not allowed | 6 ms | 2 | +2 | 2 | +2 | 5 | -4 | 9 | |
| Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed | 5 ms | 2 | +2 | 2 | +2 | 4 | -4 | 8 | |
| Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI | 3 ms | 0 | | 0 | | 9 | | 9 | |
| Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed | 7 ms | 2 | +2 | 2 | +2 | 5 | -4 | 9 | |
| Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed | 4 ms | 2 | +2 | 2 | +2 | 4 | -4 | 8 | |
| Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY | 7 ms | 2 | +2 | 2 | +2 | 5 | -4 | 9 | |
| Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY | 3 ms | 0 | | 0 | | 9 | | 9 | |
| Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account | 3 ms | 2 | +2 | 2 | +2 | 5 | -4 | 9 | |
| Scenario: B5 Broker publish to CTRL_ACC is not allowed | 5 ms | 0 | | 0 | | 9 | | 9 | |
| Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed | 3 ms | 0 | | 0 | | 9 | | 9 | |
| Scenario: B7 Broker subscribe on CTRL_ACC is not allowed | 4 ms | 2 | +2 | 2 | +2 | 4 | -4 | 8 | |
| Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI | 3 ms | 0 | | 0 | | 9 | | 9 | |
| Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed | 6 ms | 2 | +2 | 2 | +2 | 5 | -4 | 9 | |
| Scenario: Basic Device Event queries | 11 ms | 0 | | 0 | | 14 | | 14 | |
| Scenario: Birth and applications event handling | 3 ms | 0 | | 0 | | 12 | | 12 | |
| Scenario: Birth and death message handling | 5 ms | 0 | | 0 | | 12 | | 12 | |
| Scenario: Birth and missing event handling | 4 ms | 0 | | 0 | | 12 | | 12 | |
| Scenario: Birth message handling from a new device | 18 ms | 0 | | 0 | | 13 | | 13 | |
| Scenario: Birth message handling from an existing device | 4 ms | 0 | | 0 | | 12 | | 12 | |
| Scenario: Both the parent and child accounts do not expire | 5 ms | 0 | | 0 | | 11 | | 11 | |
| Scenario: Both the parent and child accounts have the same expiration date | 2 ms | 0 | | 0 | | 11 | | 11 | |
| Scenario: Captured date based ClientInfo data check | 12 ms | 0 | | 0 | | 15 | | 15 | |
| Scenario: Case sensitivness of named device searches | 8 ms | 0 | | 0 | | 3 | | 3 | |
| Scenario: Change an existing step name | 10 ms | 0 | | 0 | | 8 | | 8 | |
| Scenario: Change the account parent Id | 4 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Change the account parent path | 5 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Channel info queries based on datastore channel filters | 6 ms | 0 | | 0 | | 25 | | 25 | |
| Scenario: ChannelInfo client ID and topic data based on the client id | 19 ms | 0 | | 0 | | 14 | | 14 | |
| Scenario: ChannelInfo client ID based on the account id | 10 ms | 0 | | 0 | | 13 | | 13 | |
| Scenario: ChannelInfo last published date | 11 ms | 0 | | 0 | | 15 | | 15 | |
| Scenario: ChannelInfo topic data based on the account id | 15 ms | 0 | | 0 | | 13 | | 13 | |
| Scenario: Check account properties | 2 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Check the Device Connection Domain data seetting | 6 ms | 0 | | 0 | | 2 | | 2 | |
| Scenario: Check the database cache coherency | 8 ms | 0 | | 0 | | 15 | | 15 | |
| Scenario: Check the mapping for message semantic topics | 13 ms | 0 | | 0 | | 15 | | 15 | |
| Scenario: Check the message store | 9 ms | 0 | | 0 | | 10 | | 10 | |
| Scenario: Check the sanity of the Device Connection Domain data initialization | 5 ms | 0 | | 0 | | 2 | | 2 | |
| Scenario: Child account expires after parent | 2 ms | 0 | | 0 | | 9 | | 9 | |
| Scenario: Child account expires before parent | 2 ms | 0 | | 0 | | 11 | | 11 | |
| Scenario: Child account has null expiration date | 2 ms | 0 | | 0 | | 9 | | 9 | |
| Scenario: Client Id based ClientInfo data check | 10 ms | 0 | | 0 | | 14 | | 14 | |
| Scenario: Compare domain entries | 0 ms | 0 | | 0 | | 2 | | 2 | |
| Scenario: Connect to the system and publish some data | 3 ms | 2 | +2 | 15 | +15 | 5 | -17 | 22 | |
| Scenario: Connection Service factory sanity checks | 5 ms | 0 | | 0 | | 2 | | 2 | |
| Scenario: Count access info entities in a specific scope | 0 ms | 0 | | 0 | | 19 | | 19 | |
| Scenario: Count access role entities by scope | 3 ms | 0 | | 0 | | 33 | | 33 | |
| Scenario: Count connections in empty scope | 10 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Count connections in scope | 7 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Count devices in a specific scope | 8 ms | 0 | | 0 | | 11 | | 11 | |
| Scenario: Count devices with a specific BIOS version | 8 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Count domains in a blank database | 0 ms | 0 | | 0 | | 3 | | 3 | |
| Scenario: Count domains in the database | 1 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Count events in empty scope | 11 ms | 0 | | 0 | | 10 | | 10 | |
| Scenario: Count events in scope | 11 ms | 0 | | 0 | | 14 | | 14 | |
| Scenario: Count groups | 0 ms | 0 | | 0 | | 12 | | 12 | |
| Scenario: Count groups in a blank database | 0 ms | 0 | | 0 | | 3 | | 3 | |
| Scenario: Count job items | 9 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Count job items in wrong (empty) scope | 8 ms | 0 | | 0 | | 1 | | 1 | |
| Scenario: Count role permissions in specific scopes | 0 ms | 0 | | 0 | | 15 | | 15 | |
| Scenario: Count roles in specific scopes | 0 ms | 0 | | 0 | | 13 | | 13 | |
| Scenario: Count step definition items | 9 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Count step definitions in wrong (empty) scope | 7 ms | 0 | | 0 | | 1 | | 1 | |
| Scenario: Count steps in the database | 9 ms | 0 | | 0 | | 11 | | 11 | |
| Scenario: Count user | 5 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Create a regular event | 17 ms | 0 | | 0 | | 10 | | 10 | |
| Scenario: Create a single device | 12 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Create an event with a null action | 12 ms | 0 | | 0 | | 11 | | 11 | |
| Scenario: Create an event with a null scope ID | 12 ms | 0 | | 0 | | 10 | | 10 | |
| Scenario: Create and count multiple job targets | 6 ms | 0 | | 0 | | 8 | | 8 | |
| Scenario: Create and count several execution items for a job | 15 ms | 0 | | 0 | | 9 | | 9 | |
| Scenario: Create index with specific prefix | 7 ms | 0 | | 0 | | 13 | | 13 | |
| Scenario: Create multiple users | 4 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Create regular access permissions | 0 ms | 0 | | 0 | | 15 | | 15 | |
| Scenario: Create some regular role permissions | 0 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Create user that already exist | 6 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Create user that has more than DB allowed length | 5 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Create user with short name | 7 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Create user with special characters in his name | 8 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Create with permissions | 0 ms | 0 | | 0 | | 10 | | 10 | |
| Scenario: Create with permissions and a role | 4 ms | 0 | | 0 | | 13 | | 13 | |
| Scenario: Create with permissions and a role in the wrong scope | 0 ms | 0 | | 0 | | 10 | | 10 | |
| Scenario: Creating index with regular user | 17 ms | 0 | | 0 | | 25 | | 25 | |
| Scenario: Creating new device and tagging it with specific Tag | 8 ms | 0 | | 0 | | 14 | | 14 | |
| Scenario: Creating new device, tagging it with specific Tag and then deleting this Tag | 5 ms | 0 | | 0 | | 16 | | 16 | |
| Scenario: Creating tag | 2 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Creating two indexes with daily index | 15 ms | 0 | | 0 | | 17 | | 17 | |
| Scenario: Creating two indexes with hourly index | 15 ms | 0 | | 0 | | 17 | | 17 | |
| Scenario: Creating two indexes with weekly index | 13 ms | 0 | | 0 | | 17 | | 17 | |
| Scenario: Creating user | 59 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Creation of access role with neither acess info and role entities | 1 ms | 0 | | 0 | | 8 | | 8 | |
| Scenario: Creation of access role without an acess info entity | 0 ms | 0 | | 0 | | 8 | | 8 | |
| Scenario: D1 Device publish to CTRL_ACC_REPLY | 6 ms | 2 | +2 | 2 | +2 | 5 | -4 | 9 | |
| Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI | 3 ms | 0 | | 0 | | 9 | | 9 | |
| Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed | 3 ms | 2 | +2 | 2 | +2 | 5 | -4 | 9 | |
| Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed | 1 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY | 7 ms | 2 | +2 | 2 | +2 | 5 | -4 | 9 | |
| Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY | 6 ms | 0 | | 0 | | 9 | | 9 | |
| Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account | 2 ms | 2 | +2 | 2 | +2 | 5 | -4 | 9 | |
| Scenario: D5 Device subscribe - publish - admin on CTRL_ACC | 8 ms | 0 | | 0 | | 9 | | 9 | |
| Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI | 5 ms | 0 | | 0 | | 9 | | 9 | |
| Scenario: D7 Device publish to ACL_DATA_ACC is not allowed | 11 ms | 2 | +2 | 2 | +2 | 5 | -4 | 9 | |
| Scenario: D8 Device create sub-topic on ACL_DATA_ACC is not allowed | 3 ms | 2 | +2 | 2 | +2 | 5 | -4 | 9 | |
| Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed | 3 ms | 2 | +2 | 2 | +2 | 4 | -4 | 8 | |
| Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed | 8 ms | 2 | +2 | 2 | +2 | 5 | -4 | 9 | |
| Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI | 3 ms | 0 | | 0 | | 9 | | 9 | |
| Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed | 4 ms | 2 | +2 | 2 | +2 | 5 | -4 | 9 | |
| Scenario: DM13 Data manage subscribe on ACL_CTRL_ACC_NOTIFY is not allowed | 3 ms | 2 | +2 | 2 | +2 | 4 | -4 | 8 | |
| Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY | 5 ms | 2 | +2 | 2 | +2 | 5 | -4 | 9 | |
| Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY | 3 ms | 0 | | 0 | | 9 | | 9 | |
| Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account | 3 ms | 2 | +2 | 2 | +2 | 5 | -4 | 9 | |
| Scenario: DM5 Data manage publish to CTRL_ACC is not allowed | 5 ms | 0 | | 0 | | 9 | | 9 | |
| Scenario: DM6 Data manage create sub-topic on CTRL_ACC is not allowed | 4 ms | 0 | | 0 | | 9 | | 9 | |
| Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed | 4 ms | 2 | +2 | 2 | +2 | 4 | -4 | 8 | |
| Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI | 6 ms | 0 | | 0 | | 9 | | 9 | |
| Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC | 8 ms | 0 | | 0 | | 9 | | 9 | |
| Scenario: DV1 Data view publish to CTRL_ACC_REPLY | 5 ms | 2 | +2 | 2 | +2 | 5 | -4 | 9 | |
| Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed | 6 ms | 2 | +2 | 2 | +2 | 5 | -4 | 9 | |
| Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed | 6 ms | 0 | | 0 | | 10 | | 10 | |
| Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed | 9 ms | 0 | | 0 | | 9 | | 9 | |
| Scenario: DV13 Data view create sub-topic on ACL_CTRL_ACC_CLI is not allowed | 3 ms | 0 | | 0 | | 9 | | 9 | |
| Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed | 8 ms | 2 | +2 | 2 | +2 | 5 | -4 | 9 | |
| Scenario: DV17 Data view subscribe on ACL_CTRL_ACC_NOTIFY is not allowed | 3 ms | 2 | +2 | 2 | +2 | 4 | -4 | 8 | |
| Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY | 6 ms | 2 | +2 | 2 | +2 | 5 | -4 | 9 | |
| Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY | 2 ms | 0 | | 0 | | 9 | | 9 | |
| Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account | 3 ms | 2 | +2 | 2 | +2 | 5 | -4 | 9 | |
| Scenario: DV5 Data view publish to CTRL_ACC is not allowed | 2 ms | 0 | | 0 | | 9 | | 9 | |
| Scenario: DV6 Data view create sub-topic on CTRL_ACC is not allowed | 2 ms | 0 | | 0 | | 9 | | 9 | |
| Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed | 4 ms | 2 | +2 | 2 | +2 | 4 | -4 | 8 | |
| Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI | 7 ms | 0 | | 0 | | 9 | | 9 | |
| Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed | 9 ms | 2 | +2 | 2 | +2 | 5 | -4 | 9 | |
| Scenario: Delete Kapua system user | 4 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Delete a access info entity with permissions and roles | 1 ms | 0 | | 0 | | 9 | | 9 | |
| Scenario: Delete a connection from the database | 11 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Delete a group from the database | 1 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Delete a group from the database - Unknown group ID | 0 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Delete a job | 17 ms | 0 | | 0 | | 8 | | 8 | |
| Scenario: Delete a job execution item | 14 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Delete a job execution item twice | 14 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Delete a job target | 7 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Delete a job target twice | 11 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Delete a job twice | 13 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Delete a non existent event | 9 ms | 0 | | 0 | | 11 | | 11 | |
| Scenario: Delete a non existing connection | 6 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Delete a non existing permission entity | 0 ms | 0 | | 0 | | 12 | | 12 | |
| Scenario: Delete a non existing role entry | 0 ms | 0 | | 0 | | 8 | | 8 | |
| Scenario: Delete a non-existing step | 6 ms | 0 | | 0 | | 9 | | 9 | |
| Scenario: Delete a nonexistent domain | 0 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Delete a step definition | 10 ms | 0 | | 0 | | 8 | | 8 | |
| Scenario: Delete a step definition twice | 11 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Delete an access info entity twice | 0 ms | 0 | | 0 | | 8 | | 8 | |
| Scenario: Delete an access info entity using the wrong scope ID | 0 ms | 0 | | 0 | | 8 | | 8 | |
| Scenario: Delete an existing access info entity | 4 ms | 0 | | 0 | | 9 | | 9 | |
| Scenario: Delete an existing access permission entity | 1 ms | 0 | | 0 | | 11 | | 11 | |
| Scenario: Delete an existing access role entry | 0 ms | 0 | | 0 | | 18 | | 18 | |
| Scenario: Delete an existing account | 4 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Delete an existing device from the registry | 7 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Delete an existing event | 14 ms | 0 | | 0 | | 13 | | 13 | |
| Scenario: Delete an existing role | 0 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Delete an existing role twice | 0 ms | 0 | | 0 | | 11 | | 11 | |
| Scenario: Delete an existing step | 8 ms | 0 | | 0 | | 8 | | 8 | |
| Scenario: Delete items based on query results | 10 ms | 0 | | 0 | | 42 | | 42 | |
| Scenario: Delete items by the datastore ID | 17 ms | 0 | | 0 | | 33 | | 33 | |
| Scenario: Delete middle child expiration | 4 ms | 0 | | 0 | | 15 | | 15 | |
| Scenario: Delete nonexisting account | 4 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Delete nonexisting role permission | 0 ms | 0 | | 0 | | 10 | | 10 | |
| Scenario: Delete parent expiration | 2 ms | 0 | | 0 | | 14 | | 14 | |
| Scenario: Delete role permissions | 1 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Delete the Kapua system account | 4 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Delete the last created domain entry | 0 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Delete user | 4 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Delete user that doesn't exist | 4 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Deleting tag | 3 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Deleting user in account that is higher in hierarchy | 2 ms | 0 | | 0 | | 23 | | 23 | |
| Scenario: Deleting user in account that is lower in hierarchy | 2 ms | 0 | | 0 | | 24 | | 24 | |
| Scenario: Device connection update | 9 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Device factory sanity checks | 8 ms | 0 | | 0 | | 2 | | 2 | |
| Scenario: Device queries | 7 ms | 0 | | 0 | | 13 | | 13 | |
| Scenario: Device query - find by BIOS version | 7 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Domain entry query | 0 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Domain with null actions | 0 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Domain with null name | 0 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Domains with duplicate names | 0 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Duplicate group name in root scope | 0 ms | 0 | | 0 | | 8 | | 8 | |
| Scenario: Duplicate role names | 0 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Empty query results are supported | 0 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Event factory sanity checks | 7 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Event service domain check | 11 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Every account must have the default configuration items | 3 ms | 0 | | 0 | | 3 | | 3 | |
| Scenario: Extra long continuous test with multiple subscenarios with LOOSE default connection mode | 1 ms | 2 | +2 | 404 | +404 | 12 | -406 | 418 | |
| Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode | 2 ms | 2 | +2 | 382 | +382 | 12 | -384 | 396 | |
| Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode and no previously defined devices | 5 ms | 2 | +2 | 293 | +293 | 9 | -295 | 304 | |
| Scenario: Find a connection by its IDs | 8 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Find a connection by its client ID | 11 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Find a group entry in the database | 0 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Find a non existing event | 9 ms | 0 | | 0 | | 10 | | 10 | |
| Scenario: Find account by Id | 5 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Find account by Ids | 6 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Find account by name | 4 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Find account by random Id | 3 ms | 0 | | 0 | | 3 | | 3 | |
| Scenario: Find all child accounts | 5 ms | 0 | | 0 | | 3 | | 3 | |
| Scenario: Find an access info entity | 0 ms | 0 | | 0 | | 8 | | 8 | |
| Scenario: Find an access info entity by user ID | 2 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Find an event by its ID | 9 ms | 0 | | 0 | | 10 | | 10 | |
| Scenario: Find an existing access role entity | 0 ms | 0 | | 0 | | 9 | | 9 | |
| Scenario: Find by name nonexisting account | 4 ms | 0 | | 0 | | 3 | | 3 | |
| Scenario: Find device by client ID | 13 ms | 0 | | 0 | | 3 | | 3 | |
| Scenario: Find device by registry ID | 13 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Find last created permision | 0 ms | 0 | | 0 | | 8 | | 8 | |
| Scenario: Find multiple users | 4 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Find role by ID | 0 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Find the last created domain entry | 0 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Find user by id | 3 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Find user by name | 3 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Find user by name that doesn't exist | 5 ms | 0 | | 0 | | 3 | | 3 | |
| Scenario: Find user with id and scope id that doesn't exist | 4 ms | 0 | | 0 | | 3 | | 3 | |
| Scenario: Generic connection query | 13 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Get metadata | 4 ms | 0 | | 0 | | 3 | | 3 | |
| Scenario: Group with a null name | 1 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Handle account creation | 84 ms | 0 | | 0 | | 3 | | 3 | |
| Scenario: Handle duplicate account names | 5 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Handle null account name | 4 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Handling of 2 birth messages | 3 ms | 0 | | 0 | | 12 | | 12 | |
| Scenario: Handling of a disconnect message from a non existing device | 3 ms | 0 | | 0 | | 10 | | 10 | |
| Scenario: I try to find a non-existing connection | 13 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: If user credential expiration date is before today, user can not login | 5 ms | 0 | | 0 | | 14 | | 14 | |
| Scenario: If user credential expiration date is today, user can not login it is day inclusive | 4 ms | 0 | | 0 | | 14 | | 14 | |
| Scenario: If user credential expiration date is tomorrow, user can login | 3 ms | 0 | | 0 | | 13 | | 13 | |
| Scenario: If user credential is in state disabled, user can not login | 5 ms | 0 | | 0 | | 14 | | 14 | |
| Scenario: If user credential is in state enabled, user can login | 2 ms | 0 | | 0 | | 13 | | 13 | |
| Scenario: If user expiration date is before today, user can not login | 2 ms | 0 | | 0 | | 13 | | 13 | |
| Scenario: If user expiration date is today, user can not login because expiration date was reached | 4 ms | 0 | | 0 | | 13 | | 13 | |
| Scenario: If user expiration date is tomorrow, user can login | 2 ms | 0 | | 0 | | 12 | | 12 | |
| Scenario: Installing a package | 12 ms | 2 | +2 | 7 | +7 | 4 | -9 | 13 | |
| Scenario: It is possible to change the configuration items | 4 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: It must be possible to query for specific entries in the role database | 1 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Job execution factory sanity checks | 10 ms | 0 | | 0 | | 2 | | 2 | |
| Scenario: Job factory sanity checks | 17 ms | 0 | | 0 | | 3 | | 3 | |
| Scenario: Job target factory sanity checks | 7 ms | 0 | | 0 | | 2 | | 2 | |
| Scenario: Job with a duplicate name | 21 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Job with a null name | 11 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Job with a null scope ID | 10 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Job with an empty name | 21 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: MetricsInfo client ID and topic data based on the client id | 18 ms | 0 | | 0 | | 17 | | 17 | |
| Scenario: MetricsInfo last published date | 11 ms | 0 | | 0 | | 24 | | 24 | |
| Scenario: Modify a role that was deleted | 0 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Modify an existing account | 6 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Modify last child expiration so that it still expires before parent | 4 ms | 0 | | 0 | | 14 | | 14 | |
| Scenario: Modify middle child expiration so that it still expires before parent | 2 ms | 0 | | 0 | | 14 | | 14 | |
| Scenario: Modify middle child expiration to outlive parent | 1 ms | 0 | | 0 | | 15 | | 15 | |
| Scenario: Modify nonexisting account | 5 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Modify parent expiration so that it still expires after child | 1 ms | 0 | | 0 | | 14 | | 14 | |
| Scenario: Modify parent expiration to before child expiration | 2 ms | 0 | | 0 | | 15 | | 15 | |
| Scenario: Nameless role entry | 0 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Negative scenario when client connects twice with same client id | 6 ms | 0 | | 0 | | 11 | | 11 | |
| Scenario: New connection with reserved ID | 6 ms | 2 | +2 | 19 | +19 | 12 | -21 | 33 | |
| Scenario: Permission factory sanity checks | 0 ms | 0 | | 0 | | 3 | | 3 | |
| Scenario: Positive scenario without stealing link | 5 ms | 0 | | 0 | | 12 | | 12 | |
| Scenario: Query based on message ordering | 8 ms | 0 | | 0 | | 10 | | 10 | |
| Scenario: Query based on metrics ordering | 10 ms | 0 | | 0 | | 10 | | 10 | |
| Scenario: Query before schema search | 8 ms | 0 | | 0 | | 41 | | 41 | |
| Scenario: Query for a specific group by name | 0 ms | 0 | | 0 | | 14 | | 14 | |
| Scenario: Query for all the access info entities of a specific user | 0 ms | 0 | | 0 | | 15 | | 15 | |
| Scenario: Query for all the access info entities of an invalid user | 0 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Query for executions of a specific job | 18 ms | 0 | | 0 | | 16 | | 16 | |
| Scenario: Query for jobs with specified name | 12 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Query for step definitions | 12 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Query for the targets of a specific job | 10 ms | 0 | | 0 | | 19 | | 19 | |
| Scenario: Query user | 4 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Regular connection | 11 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Regular creation of Access Role entity | 0 ms | 0 | | 0 | | 10 | | 10 | |
| Scenario: Regular domain | 0 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Regular group in random scope | 0 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Regular group in root scope | 0 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Regular job creation | 12 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Regular job execution creation | 26 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Regular role creation | 0 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Regular step creation | 10 ms | 0 | | 0 | | 8 | | 8 | |
| Scenario: Regular step definition creation | 12 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Regular step definition with a property list | 11 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Regular target creation | 11 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Role creator sanity checks | 0 ms | 0 | | 0 | | 2 | | 2 | |
| Scenario: Role entry with no actions | 0 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Role object equality check | 0 ms | 0 | | 0 | | 2 | | 2 | |
| Scenario: Role service related objects sanity checks | 0 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Search for a non existent client ID | 6 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Search for an access info entity by an incorrect user ID | 0 ms | 0 | | 0 | | 8 | | 8 | |
| Scenario: Search the role database for a random ID | 1 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Send BIRTH message and then DC message | 8 ms | 2 | +2 | 7 | +7 | 6 | -9 | 15 | |
| Scenario: Send BIRTH message and then DC message while broker ip is NOT set | 13 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Send BIRTH message and then DC message while broker ip is set by System | 5 ms | 2 | +2 | 2 | +2 | 4 | -4 | 8 | |
| Scenario: Send BIRTH message and then DC message while broker ip is set by config file | 6 ms | 2 | +2 | 2 | +2 | 4 | -4 | 8 | |
| Scenario: Set environment variables | 0.15 sec | 0 | | 0 | | 43 | | 43 | |
| Scenario: Setting configuration without mandatory items must raise an error | 3 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Simple create | 1 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Simple positive scenario for creating daily index | 21 ms | 0 | | 0 | | 14 | | 14 | |
| Scenario: Simple positive scenario for creating default - weekly index | 20 ms | 0 | | 0 | | 12 | | 12 | |
| Scenario: Simple positive scenario for creating hourly index | 10 ms | 0 | | 0 | | 14 | | 14 | |
| Scenario: Start broker for all scenarios | 99 ms | 30 | +30 | 0 | | 2 | -30 | 32 | |
| Scenario: Start datastore for all scenarios | 0.35 sec | 0 | | 0 | | 30 | | 30 | |
| Scenario: Start event broker for all scenarios | 0.16 sec | 0 | | 0 | | 36 | | 36 | |
| Scenario: Starting and stopping the simulator should create a device entry and properly set its status | 7 ms | 2 | +2 | 14 | +14 | 4 | -16 | 20 | |
| Scenario: Stealing link scenario | 7 ms | 2 | +2 | 14 | +14 | 12 | -16 | 28 | |
| Scenario: Step definition factory sanity checks | 6 ms | 0 | | 0 | | 2 | | 2 | |
| Scenario: Step definition with a duplicate name | 6 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Step definition with a null name | 6 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Step definition with a null scope ID | 12 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Step definition with an empty name | 7 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Step factory sanity checks | 10 ms | 0 | | 0 | | 2 | | 2 | |
| Scenario: Step with a null scope ID | 7 ms | 0 | | 0 | | 8 | | 8 | |
| Scenario: Stop broker after all scenarios | 0.11 sec | 0 | | 0 | | 32 | | 32 | |
| Scenario: Stop datastore after all scenarios | 99 ms | 0 | | 0 | | 30 | | 30 | |
| Scenario: Stop event broker for all scenarios | 0.13 sec | 0 | | 0 | | 36 | | 36 | |
| Scenario: Target with a null scope ID | 7 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Test LOOSE user coupling on single connection | 3 ms | 2 | +2 | 13 | +13 | 12 | -15 | 27 | |
| Scenario: Test LOOSE user coupling with 3 connections | 1 ms | 2 | +2 | 23 | +23 | 12 | -25 | 37 | |
| Scenario: Test STRICT user coupling on single connection | 3 ms | 2 | +2 | 10 | +10 | 12 | -12 | 24 | |
| Scenario: Test STRICT user coupling with 3 connections and a reserved user | 3 ms | 2 | +2 | 48 | +48 | 12 | -50 | 62 | |
| Scenario: Test STRICT user coupling with user change allowed on single connection | 4 ms | 2 | +2 | 21 | +21 | 12 | -23 | 35 | |
| Scenario: Test account query | 3 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Test the message store with server timestamp indexing | 11 ms | 0 | | 0 | | 13 | | 13 | |
| Scenario: Test the message store with timestamp indexing | 22 ms | 0 | | 0 | | 13 | | 13 | |
| Scenario: The Client ID is case sensitive | 6 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: To be defined | 10 ms | 0 | | 15 | | 1 | | 16 | |
| Scenario: Try to change an existing connection ID | 8 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Try to create an access into entity with an invalid role id | 0 ms | 0 | | 0 | | 8 | | 8 | |
| Scenario: Try to delete a non existing device from the registry | 8 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Try to find a device with an invalid client ID | 14 ms | 0 | | 0 | | 3 | | 3 | |
| Scenario: Try to find a device with an invalid registry ID | 7 ms | 0 | | 0 | | 3 | | 3 | |
| Scenario: Try to modify the connection client ID | 6 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Try to update the device client ID | 9 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Unknown configuiration items are silently ignored | 3 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Update a group entry in the database | 0 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Update a group entry with a false ID | 0 ms | 0 | | 0 | | 8 | | 8 | |
| Scenario: Update a job XML definition | 9 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Update a job description | 11 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Update a job name | 9 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Update a job target TargetId | 6 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Update a job target status | 10 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Update a job target step index | 8 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Update a non existing device | 7 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Update a nonexistent job | 14 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Update a nonexistent step definition | 7 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Update a step definition name | 8 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Update a step definition processor name | 9 ms | 0 | | 0 | | 8 | | 8 | |
| Scenario: Update a step definition target type | 12 ms | 0 | | 0 | | 8 | | 8 | |
| Scenario: Update an existing device | 11 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Update existing role name | 0 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Update job id of an existing execution item | 21 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Update the end time of an existing execution item | 14 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Update user | 28 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Update user that doesn't exist | 3 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: User locking itself out by using out login attempts | 4 ms | 0 | | 0 | | 16 | | 16 | |
| Scenario: User locking itself out with failed attempts and not waiting to unlock | 3 ms | 0 | | 0 | | 17 | | 17 | |
| Scenario: User locking itself out with failed attempts and waiting to unlock | 2 ms | 0 | | 0 | | 17 | | 17 | |
| Scenario: User login with wrong pass, but with enough time between login failures | 2 ms | 0 | | 0 | | 19 | | 19 | |
| Scenario: User not locking itself out by using less than max failed login attempts | 2 ms | 0 | | 0 | | 17 | | 17 | |
| Scenario: Validate a device client based search with a null client ID | 7 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Validate a device client based search with an empty client ID | 6 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Validate a device client search with null scope | 6 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Validate a device count with a null Scope ID | 6 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Validate a device creator with a null client ID | 7 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Validate a device creator with a null scope ID | 6 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Validate a device query with a null Scope ID | 6 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Validate a device search with a null device ID | 10 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Validate a device search with a null scope ID | 6 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Validate a null creator | 9 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Validate a null device | 10 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Validate a null device count | 9 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Validate a null device query | 6 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Validate a regular creator | 6 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Validate a regular device | 10 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Validate a regular device client search | 4 ms | 0 | | 0 | | 3 | | 3 | |
| Scenario: Validate a regular device count | 6 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Validate a regular device deletion | 6 ms | 0 | | 0 | | 3 | | 3 | |
| Scenario: Validate a regular device query | 4 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Validate a regular device search | 8 ms | 0 | | 0 | | 3 | | 3 | |
| Scenario: Validate deleting a device with a null device ID | 7 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Validate deleting a device with a null scope ID | 5 ms | 0 | | 0 | | 4 | | 4 | |
| empty) scope | 0 ms | 0 | | 0 | | 8 | | 8 | |
![[Jenkins]](/kapua/static/1186cfd0/images/jenkins-header-logo-v2.svg){kind=logo}
