| 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.47 sec | 0 | | 0 | | 3 | | 3 | |
| Scenario: A newly created account must have some metadata | 3 ms | 0 | | 0 | | 3 | | 3 | |
| Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic | 0 ms | 2 | -1 | 6 | -1 | 0 | | 8 | -2 |
| Scenario: Access info service sanity checks | 0 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Access service comparison sanity checks | 0 ms | 0 | | 0 | | 3 | | 3 | |
| Scenario: Account expiration date test - Parent and child expiration set, then parent expiration date changed to before child expiration date | 2 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Account expiration date test - Parent expiration set, child expiration after father expiration | 5 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Account expiration date test - Parent expiration set, child expiration before father expiration | 3 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Account expiration date test - Parent expiration set, child expiration null | 4 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Account name must not be mutable | 2 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Account service metadata | 3 ms | 0 | | 0 | | 2 | | 2 | |
| Scenario: All device parameters must match the device creator | 12 ms | 0 | | 0 | | 3 | | 3 | |
| Scenario: B1 Broker publish to CTRL_ACC_REPLY | 7 ms | 2 | -1 | 7 | -1 | 0 | | 9 | -2 |
| Scenario: B10 Broker create sub-topic on ACL_DATA_ACC is not allowed | 2 ms | 2 | -1 | 7 | -1 | 0 | | 9 | -2 |
| Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed | 7 ms | 2 | -1 | 6 | -1 | 0 | | 8 | -2 |
| Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI | 7 ms | 2 | -1 | 7 | -1 | 0 | | 9 | -2 |
| Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed | 11 ms | 2 | -1 | 7 | -1 | 0 | | 9 | -2 |
| Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed | 10 ms | 2 | -1 | 6 | -1 | 0 | | 8 | -2 |
| Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY | 10 ms | 2 | -1 | 7 | -1 | 0 | | 9 | -2 |
| Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY | 7 ms | 2 | -1 | 7 | -1 | 0 | | 9 | -2 |
| Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account | 7 ms | 2 | -1 | 7 | -1 | 0 | | 9 | -2 |
| Scenario: B5 Broker publish to CTRL_ACC is not allowed | 0 ms | 2 | -1 | 7 | -1 | 0 | | 9 | -2 |
| Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed | 7 ms | 2 | -1 | 7 | -1 | 0 | | 9 | -2 |
| Scenario: B7 Broker subscribe on CTRL_ACC is not allowed | 15 ms | 2 | -1 | 6 | -1 | 0 | | 8 | -2 |
| Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI | 11 ms | 2 | -1 | 7 | -1 | 0 | | 9 | -2 |
| Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed | 6 ms | 2 | -1 | 7 | -1 | 0 | | 9 | -2 |
| Scenario: Basic Device Event queries | 11 ms | 0 | | 0 | | 14 | | 14 | |
| Scenario: Birth and applications event handling | 0 ms | 2 | -1 | 10 | -1 | 0 | | 12 | -2 |
| Scenario: Birth and death message handling | 0 ms | 2 | -1 | 10 | -1 | 0 | | 12 | -2 |
| Scenario: Birth and missing event handling | 0 ms | 2 | -1 | 10 | -1 | 0 | | 12 | -2 |
| Scenario: Birth message handling from a new device | 5 ms | 2 | -1 | 11 | -1 | 0 | | 13 | -2 |
| Scenario: Birth message handling from an existing device | 0 ms | 2 | -1 | 10 | -1 | 0 | | 12 | -2 |
| Scenario: Case sensitivness of named device searches | 8 ms | 0 | | 0 | | 3 | | 3 | |
| Scenario: Change an existing step name | 8 ms | 0 | | 0 | | 8 | | 8 | |
| Scenario: Change the account parent Id | 5 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Change the account parent path | 4 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Check account properties | 3 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Check the Device Connection Domain data seetting | 7 ms | 0 | | 0 | | 2 | | 2 | |
| Scenario: Check the sanity of the Device Connection Domain data initialization | 8 ms | 0 | | 0 | | 2 | | 2 | |
| Scenario: Compare domain entries | 0 ms | 0 | | 0 | | 2 | | 2 | |
| Scenario: Connect to the system and publish some data | 40 ms | 2 | -1 | 13 | -6 | 5 | +5 | 20 | -2 |
| Scenario: Connection Service factory sanity checks | 9 ms | 0 | | 0 | | 2 | | 2 | |
| Scenario: Count access info entities in a specific scope | 2 ms | 0 | | 0 | | 19 | | 19 | |
| Scenario: Count access role entities by scope | 1 ms | 0 | | 0 | | 33 | | 33 | |
| Scenario: Count connections in empty scope | 11 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Count connections in scope | 10 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Count devices in a specific scope | 6 ms | 0 | | 0 | | 11 | | 11 | |
| Scenario: Count devices with a specific BIOS version | 4 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 | 10 ms | 0 | | 0 | | 10 | | 10 | |
| Scenario: Count events in scope | 10 ms | 0 | | 0 | | 14 | | 14 | |
| Scenario: Count groups | 0 ms | 0 | | 0 | | 12 | | 12 | |
| Scenario: Count groups in a blank database | 1 ms | 0 | | 0 | | 3 | | 3 | |
| Scenario: Count job items | 12 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Count job items in wrong (empty) scope | 10 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 | 10 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Count step definitions in wrong (empty) scope | 8 ms | 0 | | 0 | | 1 | | 1 | |
| Scenario: Count steps in the database | 9 ms | 0 | | 0 | | 11 | | 11 | |
| Scenario: Count user | 3 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 | 11 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 | 11 ms | 0 | | 0 | | 8 | | 8 | |
| Scenario: Create and count several execution items for a job | 21 ms | 0 | | 0 | | 9 | | 9 | |
| Scenario: Create multiple users | 3 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 | 2 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Create user that has more than DB allowed length | 6 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Create user with short name | 6 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Create user with special characters in his name | 5 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Create with permissions | 0 ms | 0 | | 0 | | 10 | | 10 | |
| Scenario: Create with permissions and a role | 0 ms | 0 | | 0 | | 13 | | 13 | |
| Scenario: Create with permissions and a role in the wrong scope | 0 ms | 0 | | 0 | | 10 | | 10 | |
| Scenario: Creating new device and tagging it with specific Tag | 0 ms | 2 | -1 | 12 | -1 | 0 | | 14 | -2 |
| Scenario: Creating new device, tagging it with specific Tag and then deleting this Tag | 0 ms | 2 | -1 | 14 | -1 | 0 | | 16 | -2 |
| Scenario: Creating user | 49 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Creation of access role with neither acess info and role entities | 0 ms | 0 | | 0 | | 8 | | 8 | |
| Scenario: Creation of access role without an acess info entity | 1 ms | 0 | | 0 | | 8 | | 8 | |
| Scenario: D1 Device publish to CTRL_ACC_REPLY | 7 ms | 2 | -1 | 7 | -1 | 0 | | 9 | -2 |
| Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI | 7 ms | 2 | -1 | 7 | -1 | 0 | | 9 | -2 |
| Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed | 14 ms | 2 | -1 | 7 | -1 | 0 | | 9 | -2 |
| Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed | 1 ms | 2 | -1 | 3 | -1 | 0 | | 5 | -2 |
| Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY | 6 ms | 2 | -1 | 7 | -1 | 0 | | 9 | -2 |
| Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY | 6 ms | 2 | -1 | 7 | -1 | 0 | | 9 | -2 |
| Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account | 7 ms | 2 | -1 | 7 | -1 | 0 | | 9 | -2 |
| Scenario: D5 Device subscribe - publish - admin on CTRL_ACC | 7 ms | 2 | -1 | 7 | -1 | 0 | | 9 | -2 |
| Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI | 6 ms | 2 | -1 | 7 | -1 | 0 | | 9 | -2 |
| Scenario: D7 Device publish to ACL_DATA_ACC is not allowed | 12 ms | 2 | -1 | 7 | -1 | 0 | | 9 | -2 |
| Scenario: D8 Device create sub-topic on ACL_DATA_ACC is not allowed | 6 ms | 2 | -1 | 7 | -1 | 0 | | 9 | -2 |
| Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed | 6 ms | 2 | -1 | 6 | -1 | 0 | | 8 | -2 |
| Scenario: DV1 Data view publish to CTRL_ACC_REPLY | 9 ms | 2 | -1 | 7 | -1 | 0 | | 9 | -2 |
| Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed | 0 ms | 2 | -1 | 7 | -1 | 0 | | 9 | -2 |
| Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed | 5 ms | 2 | -1 | 8 | -1 | 0 | | 10 | -2 |
| Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed | 1 ms | 2 | -1 | 7 | -1 | 0 | | 9 | -2 |
| Scenario: DV13 Data view create sub-topic on ACL_CTRL_ACC_CLI is not allowed | 6 ms | 2 | -1 | 7 | -1 | 0 | | 9 | -2 |
| Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed | 9 ms | 2 | -1 | 7 | -1 | 0 | | 9 | -2 |
| Scenario: DV17 Data view subscribe on ACL_CTRL_ACC_NOTIFY is not allowed | 5 ms | 2 | -1 | 6 | -1 | 0 | | 8 | -2 |
| Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY | 7 ms | 2 | -1 | 7 | -1 | 0 | | 9 | -2 |
| Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY | 7 ms | 2 | -1 | 7 | -1 | 0 | | 9 | -2 |
| Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account | 6 ms | 2 | -1 | 7 | -1 | 0 | | 9 | -2 |
| Scenario: DV5 Data view publish to CTRL_ACC is not allowed | 10 ms | 2 | -1 | 7 | -1 | 0 | | 9 | -2 |
| Scenario: DV6 Data view create sub-topic on CTRL_ACC is not allowed | 6 ms | 2 | -1 | 7 | -1 | 0 | | 9 | -2 |
| Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed | 7 ms | 2 | -1 | 6 | -1 | 0 | | 8 | -2 |
| Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI | 7 ms | 2 | -1 | 7 | -1 | 0 | | 9 | -2 |
| Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed | 9 ms | 2 | -1 | 7 | -1 | 0 | | 9 | -2 |
| Scenario: Delete Kapua system user | 3 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Delete a access info entity with permissions and roles | 2 ms | 0 | | 0 | | 9 | | 9 | |
| Scenario: Delete a connection from the database | 8 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Delete a group from the database | 0 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 | 25 ms | 0 | | 0 | | 8 | | 8 | |
| Scenario: Delete a job execution item | 18 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Delete a job execution item twice | 19 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Delete a job target | 9 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Delete a job target twice | 10 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Delete a job twice | 22 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Delete a non existent event | 10 ms | 0 | | 0 | | 11 | | 11 | |
| Scenario: Delete a non existing connection | 7 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Delete a non existing permission entity | 1 ms | 0 | | 0 | | 12 | | 12 | |
| Scenario: Delete a non existing role entry | 0 ms | 0 | | 0 | | 8 | | 8 | |
| Scenario: Delete a non-existing step | 10 ms | 0 | | 0 | | 9 | | 9 | |
| Scenario: Delete a nonexistent domain | 0 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Delete a step definition | 13 ms | 0 | | 0 | | 8 | | 8 | |
| Scenario: Delete a step definition twice | 8 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 | 2 ms | 0 | | 0 | | 9 | | 9 | |
| Scenario: Delete an existing access permission entity | 0 ms | 0 | | 0 | | 11 | | 11 | |
| Scenario: Delete an existing access role entry | 1 ms | 0 | | 0 | | 18 | | 18 | |
| Scenario: Delete an existing account | 3 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Delete an existing device from the registry | 15 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Delete an existing event | 9 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 | 7 ms | 0 | | 0 | | 8 | | 8 | |
| Scenario: Delete nonexisting account | 4 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Delete nonexisting role permission | 5 ms | 0 | | 0 | | 10 | | 10 | |
| Scenario: Delete role permissions | 0 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Delete the Kapua system account | 3 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: Device connection update | 13 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Device factory sanity checks | 10 ms | 0 | | 0 | | 2 | | 2 | |
| Scenario: Device queries | 10 ms | 0 | | 0 | | 13 | | 13 | |
| Scenario: Device query - find by BIOS version | 8 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 | 1 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 | 13 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Event service domain check | 12 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Every account must have the default configuration items | 3 ms | 0 | | 0 | | 3 | | 3 | |
| Scenario: Find a connection by its IDs | 8 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Find a connection by its client ID | 13 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Find a group entry in the database | 1 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Find a non existing event | 14 ms | 0 | | 0 | | 10 | | 10 | |
| Scenario: Find account by Id | 4 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Find account by Ids | 8 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Find account by name | 4 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Find account by random Id | 6 ms | 0 | | 0 | | 3 | | 3 | |
| Scenario: Find all child accounts | 6 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 | 0 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 | 5 ms | 0 | | 0 | | 3 | | 3 | |
| Scenario: Find device by client ID | 12 ms | 0 | | 0 | | 3 | | 3 | |
| Scenario: Find device by registry ID | 10 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Find last created permision | 0 ms | 0 | | 0 | | 8 | | 8 | |
| Scenario: Find multiple users | 3 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 | 3 ms | 0 | | 0 | | 3 | | 3 | |
| Scenario: Find user with id and scope id that doesn't exist | 3 ms | 0 | | 0 | | 3 | | 3 | |
| Scenario: Generic connection query | 6 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Get metadata | 3 ms | 0 | | 0 | | 3 | | 3 | |
| Scenario: Group with a null name | 0 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Handle account creation | 46 ms | 0 | | 0 | | 3 | | 3 | |
| Scenario: Handle duplicate account names | 7 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Handle null account name | 5 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Handling of 2 birth messages | 0 ms | 2 | -1 | 10 | -1 | 0 | | 12 | -2 |
| Scenario: Handling of a disconnect message from a non existing device | 0 ms | 2 | -1 | 8 | -1 | 0 | | 10 | -2 |
| Scenario: I try to find a non-existing connection | 5 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: It is possible to change the configuration items | 3 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: It must be possible to query for specific entries in the role database | 2 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Job execution factory sanity checks | 22 ms | 0 | | 0 | | 2 | | 2 | |
| Scenario: Job factory sanity checks | 7 ms | 0 | | 0 | | 3 | | 3 | |
| Scenario: Job target factory sanity checks | 7 ms | 0 | | 0 | | 2 | | 2 | |
| Scenario: Job with a duplicate name | 14 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Job with a null name | 14 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Job with a null scope ID | 13 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Job with an empty name | 16 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Modify a role that was deleted | 1 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Modify an existing account | 3 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Modify nonexisting account | 4 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Nameless role entry | 0 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Negative scenario when client connects twice with same client id | 0 ms | 2 | -1 | 8 | -2 | 1 | +1 | 11 | -2 |
| Scenario: Permission factory sanity checks | 0 ms | 0 | | 0 | | 3 | | 3 | |
| Scenario: Positive scenario without stealing link | 0 ms | 2 | -1 | 9 | -2 | 1 | +1 | 12 | -2 |
| 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 | 19 ms | 0 | | 0 | | 16 | | 16 | |
| Scenario: Query for jobs with specified name | 16 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 | 3 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Regular connection | 17 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 | 2 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Regular job creation | 21 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Regular job execution creation | 53 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Regular role creation | 0 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Regular step creation | 7 ms | 0 | | 0 | | 8 | | 8 | |
| Scenario: Regular step definition creation | 13 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Regular step definition with a property list | 9 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Regular target creation | 10 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 | 8 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 | 0 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Send BIRTH message and then DC message while broker ip is NOT set | 0 ms | 2 | -1 | 3 | -2 | 1 | +1 | 6 | -2 |
| Scenario: Setting configuration without mandatory items must raise an error | 4 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Simple create | 1 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Start broker for all scenarios | 16 sec | 6 | -68 | 0 | -2 | 0 | | 6 | -70 |
| Scenario: Start datastore for all scenarios | 23 sec | 0 | -52 | 0 | -2 | 5 | +5 | 5 | -49 |
| Scenario: Start event broker for all scenarios | 9.4 sec | 3 | -46 | 0 | -2 | 0 | | 3 | -48 |
| Scenario: Stealing link scenario | 0 ms | 2 | -1 | 24 | -3 | 2 | +2 | 28 | -2 |
| Scenario: Step definition factory sanity checks | 8 ms | 0 | | 0 | | 2 | | 2 | |
| Scenario: Step definition with a duplicate name | 8 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Step definition with a null name | 21 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Step definition with a null scope ID | 26 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Step definition with an empty name | 11 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Step factory sanity checks | 7 ms | 0 | | 0 | | 2 | | 2 | |
| Scenario: Step with a null scope ID | 12 ms | 0 | | 0 | | 8 | | 8 | |
| Scenario: Stop broker after all scenarios | 7 sec | 0 | -56 | 0 | -2 | 5 | +5 | 5 | -53 |
| Scenario: Stop datastore after all scenario | 0.6 sec | 0 | -3 | 0 | | 1 | +1 | 1 | -2 |
| Scenario: Stop datastore after all scenarios | 2.4 sec | 0 | -49 | 0 | -2 | 4 | +4 | 4 | -47 |
| Scenario: Stop event broker after all scenarios | 0.52 sec | 0 | -6 | 0 | | 1 | +1 | 1 | -5 |
| Scenario: Stop event broker for all scenarios | 1.5 sec | 0 | -45 | 0 | -2 | 3 | +3 | 3 | -44 |
| Scenario: Target with a null scope ID | 10 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Test account query | 3 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: The Client ID is case sensitive | 7 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Try to change an existing connection ID | 6 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Try to create an access into entity with an invalid role id | 1 ms | 0 | | 0 | | 8 | | 8 | |
| Scenario: Try to delete a non existing device from the registry | 9 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Try to find a device with an invalid client ID | 8 ms | 0 | | 0 | | 3 | | 3 | |
| Scenario: Try to find a device with an invalid registry ID | 11 ms | 0 | | 0 | | 3 | | 3 | |
| Scenario: Try to modify the connection client ID | 12 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Try to update the device client ID | 8 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Unknown configuiration items are silently ignored | 4 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Update a group entry in the database | 2 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 | 10 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Update a job description | 11 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Update a job name | 21 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Update a job target TargetId | 14 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Update a job target status | 9 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Update a job target step index | 15 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Update a non existing device | 14 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Update a nonexistent job | 16 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Update a nonexistent step definition | 18 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Update a step definition name | 13 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Update a step definition processor name | 23 ms | 0 | | 0 | | 8 | | 8 | |
| Scenario: Update a step definition target type | 20 ms | 0 | | 0 | | 8 | | 8 | |
| Scenario: Update an existing device | 12 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 | 27 ms | 0 | | 0 | | 6 | | 6 | |
| Scenario: Update the end time of an existing execution item | 22 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Update user | 5 ms | 0 | | 0 | | 7 | | 7 | |
| Scenario: Update user that doesn't exist | 4 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Validate a device client based search with a null client ID | 10 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Validate a device client based search with an empty client ID | 8 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Validate a device client search with null scope | 12 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Validate a device count with a null Scope ID | 9 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 | 7 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Validate a device search with a null device ID | 9 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Validate a device search with a null scope ID | 9 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Validate a null creator | 12 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Validate a null device | 9 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Validate a null device count | 8 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Validate a null device query | 13 ms | 0 | | 0 | | 5 | | 5 | |
| Scenario: Validate a regular creator | 8 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Validate a regular device | 6 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Validate a regular device client search | 7 ms | 0 | | 0 | | 3 | | 3 | |
| Scenario: Validate a regular device count | 8 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Validate a regular device deletion | 11 ms | 0 | | 0 | | 3 | | 3 | |
| Scenario: Validate a regular device query | 11 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Validate a regular device search | 7 ms | 0 | | 0 | | 3 | | 3 | |
| Scenario: Validate deleting a device with a null device ID | 9 ms | 0 | | 0 | | 4 | | 4 | |
| Scenario: Validate deleting a device with a null scope ID | 7 ms | 0 | | 0 | | 4 | | 4 | |
| empty) scope | 0 ms | 0 | | 0 | | 8 | | 8 | |
![[Jenkins]](/kapua/static/eb5811dc/images/svgs/logo.svg){kind=logo}
