Skip to content
[Jenkins]Jenkins
log in

Test Result : (root)

818 failures , 1,850 skipped
5,509 tests
Took 6 min 50 sec.

All Failed Tests

Test NameDurationAge
 Scenario: A fresh database must contain 1 default role in the root scope.Scenario: A fresh database must contain 1 default role in the root scope3 ms1
 Scenario: A mock test scenario.Scenario: A mock test scenario0.89 sec1
 Scenario: A mock test scenario.Scenario: A mock test scenario0.92 sec1
 Scenario: A mock test scenario.Scenario: A mock test scenario4.6 sec1
 Scenario: A mock test scenario.Scenario: A mock test scenario2.8 sec1
 Scenario: A mock test scenario.Scenario: A mock test scenario1.9 sec1
 Scenario: A newly created account must have some metadata.Scenario: A newly created account must have some metadata4 ms1
 Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic.Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic2 ms1
 Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic.When broker with clientId "client-1" and user "kapua-sys" and password "kapua-password" is listening on topic "#"1 ms1
 Scenario: Access info service sanity checks.Scenario: Access info service sanity checks0.88 sec1
 Scenario: Access info service sanity checks.Scenario: Access info service sanity checks1.6 sec1
 Scenario: Access info service sanity checks.Scenario: Access info service sanity checks0.17 sec1
 Scenario: Access info service sanity checks.Scenario: Access info service sanity checks1.5 sec1
 Scenario: Access service comparison sanity checks.Scenario: Access service comparison sanity checks4 ms1
 Scenario: Access service comparison sanity checks.Scenario: Access service comparison sanity checks16 ms1
 Scenario: Access service comparison sanity checks.Scenario: Access service comparison sanity checks76 ms1
 Scenario: Access service comparison sanity checks.Scenario: Access service comparison sanity checks30 ms1
 Scenario: Account based ClientInfo data check.Scenario: Account based ClientInfo data check0.14 sec1
 Scenario: Account expiration date test - Parent and child expiration set, then parent expiration date changed to before child expiration date.Scenario: Account expiration date test - Parent and child expiration set, then parent expiration date changed to before child expiration date3 ms1
 Scenario: Account expiration date test - Parent expiration set, child expiration after father expiration.Scenario: Account expiration date test - Parent expiration set, child expiration after father expiration5 ms1
 Scenario: Account expiration date test - Parent expiration set, child expiration before father expiration.Given An existing account that expires on "2018-07-11" with the name "exp-acc"0 ms1
 Scenario: Account expiration date test - Parent expiration set, child expiration before father expiration.Scenario: Account expiration date test - Parent expiration set, child expiration before father expiration0 ms1
 Scenario: Account expiration date test - Parent expiration set, child expiration null.Scenario: Account expiration date test - Parent expiration set, child expiration null0.26 sec1
 Scenario: Account name must not be mutable.Scenario: Account name must not be mutable0.23 sec1
 Scenario: Account service metadata.Scenario: Account service metadata3 ms1
 Scenario: Account wide metrics check.Scenario: Account wide metrics check3 ms1
 Scenario: B1 Broker publish to CTRL_ACC_REPLY.Scenario: B1 Broker publish to CTRL_ACC_REPLY5 ms1
 Scenario: B1 Broker publish to CTRL_ACC_REPLY.When broker with clientId "client-1" and user "luise" and password "kapua-password" is listening on topic ""4 ms1
 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 ms1
 Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed.Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed3 ms1
 Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI.Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI3 ms1
 Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed4 ms1
 Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY.Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY4 ms1
 Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY.When broker with clientId "client-1" and user "luise" and password "kapua-password" is listening on topic ""2 ms1
 Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY.Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY4 ms1
 Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY.When broker with clientId "client-1" and user "luise" and password "kapua-password" is listening on topic "$EDC/acme/client-1/CONF-V1/REPLY"3 ms1
 Scenario: B5 Broker publish to CTRL_ACC is not allowed.Scenario: B5 Broker publish to CTRL_ACC is not allowed0.45 sec1
 Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed.Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed4 ms1
 Scenario: B7 Broker subscribe on CTRL_ACC is not allowed.Scenario: B7 Broker subscribe on CTRL_ACC is not allowed2 ms1
 Scenario: B7 Broker subscribe on CTRL_ACC is not allowed.When broker with clientId "client-1" and user "luise" and password "kapua-password" is listening on topic "$EDC/acme"1 ms1
 Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI.Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI0.33 sec1
 Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed.Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed24 ms1
 Scenario: Birth and applications event handling.Scenario: Birth and applications event handling0.35 sec1
 Scenario: Birth message handling from a new device.Scenario: Birth message handling from a new device4 ms1
 Scenario: Birth message handling from an existing device.Scenario: Birth message handling from an existing device4 ms1
 Scenario: Change an existing step name.Scenario: Change an existing step name0.26 sec1
 Scenario: Change an existing step name.Scenario: Change an existing step name0.46 sec1
 Scenario: Change an existing step name.Scenario: Change an existing step name0.92 sec1
 Scenario: Change an existing step name.Scenario: Change an existing step name0.65 sec1
 Scenario: Change an existing step name.Scenario: Change an existing step name1.2 sec1
 Scenario: Change the account parent Id.Scenario: Change the account parent Id0.32 sec1
 Scenario: Change the account parent path.Scenario: Change the account parent path0.15 sec1
 Scenario: Channel info queries based on datastore channel filters.Scenario: Channel info queries based on datastore channel filters11 ms1
 Scenario: ChannelInfo client ID and topic data based on the client id.Scenario: ChannelInfo client ID and topic data based on the client id0.19 sec1
 Scenario: ChannelInfo client ID based on the account id.Scenario: ChannelInfo client ID based on the account id3 ms1
 Scenario: ChannelInfo last published date.Scenario: ChannelInfo last published date3 ms1
 Scenario: ChannelInfo topic data based on the account id.Scenario: ChannelInfo topic data based on the account id4 ms1
 Scenario: Check account properties.Scenario: Check account properties68 ms1
 Scenario: Check the Device Connection Domain data seetting.Scenario: Check the Device Connection Domain data seetting0.47 sec1
 Scenario: Check the Device Connection Domain data seetting.Scenario: Check the Device Connection Domain data seetting0.38 sec1
 Scenario: Check the Device Connection Domain data seetting.Scenario: Check the Device Connection Domain data seetting4 ms1
 Scenario: Check the mapping for message semantic topics.Scenario: Check the mapping for message semantic topics5 ms1
 Scenario: Check the message store.Scenario: Check the message store0.52 sec1
 Scenario: Check the sanity of the Device Connection Domain data initialization.Scenario: Check the sanity of the Device Connection Domain data initialization0.62 sec1
 Scenario: Check the sanity of the Device Connection Domain data initialization.Scenario: Check the sanity of the Device Connection Domain data initialization0.17 sec1
 Scenario: Client Id based ClientInfo data check.Scenario: Client Id based ClientInfo data check96 ms1
 Scenario: Compare domain entries.Scenario: Compare domain entries0.15 sec1
 Scenario: Compare domain entries.Scenario: Compare domain entries0.13 sec1
 Scenario: Compare domain entries.Scenario: Compare domain entries0.16 sec1
 Scenario: Compare domain entries.Scenario: Compare domain entries0.11 sec1
 Scenario: Compare domain entries.Scenario: Compare domain entries0.93 sec1
 Scenario: Connect to the system and publish some data.Scenario: Connect to the system and publish some data4 ms1
 Scenario: Connect to the system and publish some data.Then Device sim-1 for account kapua-sys is registered after 5 seconds3 ms1
 Scenario: Connection Service factory sanity checks.Scenario: Connection Service factory sanity checks84 ms1
 Scenario: Connection Service factory sanity checks.Scenario: Connection Service factory sanity checks0.22 sec1
 Scenario: Connection Service factory sanity checks.Scenario: Connection Service factory sanity checks16 ms1
 Scenario: Count access info entities in a specific scope.Scenario: Count access info entities in a specific scope2.7 sec1
 Scenario: Count access info entities in a specific scope.Scenario: Count access info entities in a specific scope1.7 sec1
 Scenario: Count access info entities in a specific scope.Scenario: Count access info entities in a specific scope1.6 sec1
 Scenario: Count access info entities in a specific scope.Scenario: Count access info entities in a specific scope2.7 sec1
 Scenario: Count access role entities by scope.Scenario: Count access role entities by scope0.65 sec1
 Scenario: Count access role entities by scope.Scenario: Count access role entities by scope3 ms1
 Scenario: Count access role entities by scope.Scenario: Count access role entities by scope0.67 sec1
 Scenario: Count access role entities by scope.Scenario: Count access role entities by scope26 ms1
 Scenario: Count domains in a blank database.Scenario: Count domains in a blank database1.1 sec1
 Scenario: Count domains in a blank database.Scenario: Count domains in a blank database1 sec1
 Scenario: Count domains in a blank database.Scenario: Count domains in a blank database1.1 sec1
 Scenario: Count domains in a blank database.Scenario: Count domains in a blank database1 sec1
 Scenario: Count domains in the database.Scenario: Count domains in the database0.88 sec1
 Scenario: Count domains in the database.Scenario: Count domains in the database44 ms1
 Scenario: Count domains in the database.Scenario: Count domains in the database27 ms1
 Scenario: Count domains in the database.Scenario: Count domains in the database6 ms1
 Scenario: Count groups.Scenario: Count groups0.12 sec1
 Scenario: Count groups.Scenario: Count groups0.1 sec1
 Scenario: Count groups.Scenario: Count groups71 ms1
 Scenario: Count groups.Scenario: Count groups86 ms1
 Scenario: Count groups in a blank database.Scenario: Count groups in a blank database0.75 sec1
 Scenario: Count groups in a blank database.Scenario: Count groups in a blank database17 ms1
 Scenario: Count groups in a blank database.Scenario: Count groups in a blank database4 ms1
 Scenario: Count groups in a blank database.Scenario: Count groups in a blank database0.5 sec1
 Scenario: Count job items.Scenario: Count job items22 ms1
 Scenario: Count job items.Scenario: Count job items43 ms1
 Scenario: Count job items.Scenario: Count job items14 ms1
 Scenario: Count job items.Scenario: Count job items32 ms1
 Scenario: Count job items.Scenario: Count job items4 ms1
 Scenario: Count job items in wrong (empty) scope.Scenario: Count job items in wrong 3 ms1
 Scenario: Count job items in wrong (empty) scope.Scenario: Count job items in wrong 0.36 sec1
 Scenario: Count job items in wrong (empty) scope.Scenario: Count job items in wrong 0.1 sec1
 Scenario: Count job items in wrong (empty) scope.Scenario: Count job items in wrong 0.33 sec1
 Scenario: Count job items in wrong (empty) scope.Scenario: Count job items in wrong 0.11 sec1
 Scenario: Count role permissions in specific scopes.Scenario: Count role permissions in specific scopes1.1 sec1
 Scenario: Count role permissions in specific scopes.Scenario: Count role permissions in specific scopes0.1 sec1
 Scenario: Count role permissions in specific scopes.Scenario: Count role permissions in specific scopes76 ms1
 Scenario: Count roles in specific scopes.Scenario: Count roles in specific scopes1.3 sec1
 Scenario: Count roles in specific scopes.Scenario: Count roles in specific scopes1.5 sec1
 Scenario: Count roles in specific scopes.Scenario: Count roles in specific scopes1.5 sec1
 Scenario: Count roles in specific scopes.Scenario: Count roles in specific scopes6 ms1
 Scenario: Count step definition items.Scenario: Count step definition items0.3 sec1
 Scenario: Count step definition items.Scenario: Count step definition items0.1 sec1
 Scenario: Count step definition items.Scenario: Count step definition items90 ms1
 Scenario: Count step definition items.Scenario: Count step definition items3 ms1
 Scenario: Count step definition items.Scenario: Count step definition items72 ms1
 Scenario: Count step definitions in wrong (empty) scope.Scenario: Count step definitions in wrong 0.15 sec1
 Scenario: Count step definitions in wrong (empty) scope.Scenario: Count step definitions in wrong 0.41 sec1
 Scenario: Count step definitions in wrong (empty) scope.Scenario: Count step definitions in wrong 0.88 sec1
 Scenario: Count step definitions in wrong (empty) scope.Scenario: Count step definitions in wrong 0.68 sec1
 Scenario: Count step definitions in wrong (empty) scope.Scenario: Count step definitions in wrong 1 sec1
 Scenario: Count steps in the database.Scenario: Count steps in the database0.2 sec1
 Scenario: Count steps in the database.Scenario: Count steps in the database0.4 sec1
 Scenario: Count steps in the database.Scenario: Count steps in the database0.55 sec1
 Scenario: Count steps in the database.Scenario: Count steps in the database0.75 sec1
 Scenario: Count steps in the database.Scenario: Count steps in the database0.92 sec1
 Scenario: Count user.Scenario: Count user3 ms1
 Scenario: Create a regular event.Scenario: Create a regular event6 sec1
 Scenario: Create a regular event.Scenario: Create a regular event6 sec1
 Scenario: Create an event with a null action.Scenario: Create an event with a null action2 sec1
 Scenario: Create an event with a null action.Scenario: Create an event with a null action2 sec1
 Scenario: Create and count multiple job targets.Scenario: Create and count multiple job targets0.82 sec1
 Scenario: Create and count multiple job targets.Scenario: Create and count multiple job targets0.48 sec1
 Scenario: Create and count multiple job targets.Scenario: Create and count multiple job targets0.15 sec1
 Scenario: Create and count multiple job targets.Scenario: Create and count multiple job targets0.3 sec1
 Scenario: Create and count multiple job targets.Scenario: Create and count multiple job targets0.65 sec1
 Scenario: Create and count several execution items for a job.Scenario: Create and count several execution items for a job0.25 sec1
 Scenario: Create and count several execution items for a job.Scenario: Create and count several execution items for a job0.16 sec1
 Scenario: Create and count several execution items for a job.Scenario: Create and count several execution items for a job0.26 sec1
 Scenario: Create and count several execution items for a job.Scenario: Create and count several execution items for a job0.27 sec1
 Scenario: Create and count several execution items for a job.Scenario: Create and count several execution items for a job3 ms1
 Scenario: Create index with specific prefix.And REST response containing text "custom-prefix-1-2018-01"1 ms1
 Scenario: Create index with specific prefix.Scenario: Create index with specific prefix2 ms1
 Scenario: Create multiple users.Scenario: Create multiple users58 ms1
 Scenario: Create regular access permissions.Scenario: Create regular access permissions4 ms1
 Scenario: Create regular access permissions.Scenario: Create regular access permissions0.12 sec1
 Scenario: Create regular access permissions.Scenario: Create regular access permissions0.2 sec1
 Scenario: Create regular access permissions.Scenario: Create regular access permissions0.83 sec1
 Scenario: Create user that already exist.Scenario: Create user that already exist15 ms1
 Scenario: Create user that has more than DB allowed length.Scenario: Create user that has more than DB allowed length30 ms1
 Scenario: Create user with short name.Scenario: Create user with short name0.54 sec1
 Scenario: Create user with special characters in his name.Scenario: Create user with special characters in his name32 ms1
 Scenario: Create with permissions.Scenario: Create with permissions4 ms1
 Scenario: Create with permissions and a role in the wrong scope.Scenario: Create with permissions and a role in the wrong scope0.9 sec1
 Scenario: Create with permissions and a role in the wrong scope.Scenario: Create with permissions and a role in the wrong scope4.4 sec1
 Scenario: Create with permissions and a role in the wrong scope.Scenario: Create with permissions and a role in the wrong scope66 ms1
 Scenario: Create with permissions and a role in the wrong scope.Scenario: Create with permissions and a role in the wrong scope0.88 sec1
 Scenario: Creating new device and tagging it with specific Tag.Scenario: Creating new device and tagging it with specific Tag3 ms1
 Scenario: Creating new device, tagging it with specific Tag and then deleting this Tag.Scenario: Creating new device, tagging it with specific Tag and then deleting this Tag3 ms1
 Scenario: Creating two indexes with daily index.And REST response containing text "1-2018-01-02"2 ms1
 Scenario: Creating two indexes with daily index.Scenario: Creating two indexes with daily index3 ms1
 Scenario: Creating two indexes with hourly index.And REST response containing text "1-2018-01-02-10"2 ms1
 Scenario: Creating two indexes with hourly index.Scenario: Creating two indexes with hourly index2 ms1
 Scenario: Creating user.Scenario: Creating user4.6 sec1
 Scenario: Creation of access role with neither acess info and role entities.Scenario: Creation of access role with neither acess info and role entities33 ms1
 Scenario: Creation of access role with neither acess info and role entities.Scenario: Creation of access role with neither acess info and role entities13 ms1
 Scenario: Creation of access role with neither acess info and role entities.Scenario: Creation of access role with neither acess info and role entities4 ms1
 Scenario: Creation of access role with neither acess info and role entities.Scenario: Creation of access role with neither acess info and role entities23 ms1
 Scenario: Creation of access role with neither acess info and role entities.Scenario: Creation of access role with neither acess info and role entities42 ms1
 Scenario: Creation of access role without an acess info entity.Scenario: Creation of access role without an acess info entity0.74 sec1
 Scenario: Creation of access role without an acess info entity.Scenario: Creation of access role without an acess info entity0.75 sec1
 Scenario: Creation of access role without an acess info entity.Scenario: Creation of access role without an acess info entity61 ms1
 Scenario: Creation of access role without an acess info entity.Scenario: Creation of access role without an acess info entity0.76 sec1
 Scenario: D1 Device publish to CTRL_ACC_REPLY.Scenario: D1 Device publish to CTRL_ACC_REPLY0.25 sec1
 Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI.Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI6 ms1
 Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI.When broker with clientId "client-1" and user "luise" and password "kapua-password" is listening on topic "acme/client-1/foo"5 ms1
 Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed6 ms1
 Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed.When broker with clientId "client-1" and user "luise" and password "kapua-password" is listening on topic ""5 ms1
 Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed4 ms1
 Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.When broker with clientId "client-1" and user "luise" and password "kapua-password" is listening on topic "$EDC/acme/foo/bar/NOTIFY/client-1"3 ms1
 Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY.Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY6 ms1
 Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY.When broker with clientId "client-1" and user "luise" and password "kapua-password" is listening on topic ""4 ms1
 Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY.Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY3 ms1
 Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY.When broker with clientId "client-1" and user "luise" and password "kapua-password" is listening on topic "$EDC/acme/client-1/CONF-V1/REPLY"2 ms1
 Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account.Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account4 ms1
 Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account.When broker with clientId "client-1" and user "luise" and password "kapua-password" is listening on topic "$EDC/domino/client-1/CONF-V1/REPLY"2 ms1
 Scenario: D5 Device subscribe - publish - admin on CTRL_ACC.Scenario: D5 Device subscribe - publish - admin on CTRL_ACC5 ms1
 Scenario: D5 Device subscribe - publish - admin on CTRL_ACC.When broker with clientId "client-1" and user "luise" and password "kapua-password" is listening on topic "$EDC/acme/foo"2 ms1
 Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI.Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI5 ms1
 Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI.When broker with clientId "client-1" and user "luise" and password "kapua-password" is listening on topic "$EDC/acme/client-1/foo"4 ms1
 Scenario: D7 Device publish to ACL_DATA_ACC is not allowed.Scenario: D7 Device publish to ACL_DATA_ACC is not allowed5 ms1
 Scenario: D7 Device publish to ACL_DATA_ACC is not allowed.When broker with clientId "client-1" and user "luise" and password "kapua-password" is listening on topic ""3 ms1
 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 allowed6 ms1
 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"5 ms1
 Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed.Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed5 ms1
 Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed.Then An exception was thrown4 ms1
 Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed.Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed3 ms1
 Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI.Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI4 ms1
 Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed2 ms1
 Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed.When broker with clientId "client-1" and user "luise" and password "kapua-password" is listening on topic ""1 ms1
 Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY.Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY3 ms1
 Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY.Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY3 ms1
 Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account.Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account3 ms1
 Scenario: DM5 Data manage publish to CTRL_ACC is not allowed.Scenario: DM5 Data manage publish to CTRL_ACC is not allowed3 ms1
 Scenario: DM6 Data manage create sub-topic on CTRL_ACC is not allowed.Scenario: DM6 Data manage create sub-topic on CTRL_ACC is not allowed7 ms1
 Scenario: DM6 Data manage create sub-topic on CTRL_ACC is not allowed.When broker with clientId "client-1" and user "luise" and password "kapua-password" is listening on topic ""5 ms1
 Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed.Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed4 ms1
 Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed.When broker with clientId "client-1" and user "luise" and password "kapua-password" is listening on topic "$EDC/acme"3 ms1
 Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI.Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI4 ms1
 Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI.When broker with clientId "client-1" and user "luise" and password "kapua-password" is listening on topic "$EDC/acme/client-1/foo"3 ms1
 Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC.Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC0.16 sec1
 Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed.Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed0.37 sec1
 Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed.Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed0.42 sec1
 Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed.Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed3 ms1
 Scenario: DV13 Data view create sub-topic on ACL_CTRL_ACC_CLI is not allowed.Scenario: DV13 Data view create sub-topic on ACL_CTRL_ACC_CLI is not allowed3 ms1
 Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed5 ms1
 Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed.When broker with clientId "client-1" and user "luise" and password "kapua-password" is listening on topic ""4 ms1
 Scenario: DV17 Data view subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Scenario: DV17 Data view subscribe on ACL_CTRL_ACC_NOTIFY is not allowed0.32 sec1
 Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY.Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY4 ms1
 Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY.When broker with clientId "client-1" and user "luise" and password "kapua-password" is listening on topic ""2 ms1
 Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY.Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY4 ms1
 Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY.When broker with clientId "client-1" and user "luise" and password "kapua-password" is listening on topic "$EDC/acme/client-1/CONF-V1/REPLY"2 ms1
 Scenario: DV5 Data view publish to CTRL_ACC is not allowed.Scenario: DV5 Data view publish to CTRL_ACC is not allowed13 ms1
 Scenario: DV5 Data view publish to CTRL_ACC is not allowed.When broker with clientId "client-1" and user "luise" and password "kapua-password" is listening on topic ""2 ms1
 Scenario: DV6 Data view create sub-topic on CTRL_ACC is not allowed.Scenario: DV6 Data view create sub-topic on CTRL_ACC is not allowed6 ms1
 Scenario: DV6 Data view create sub-topic on CTRL_ACC is not allowed.When broker with clientId "client-1" and user "luise" and password "kapua-password" is listening on topic ""2 ms1
 Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI.Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI4 ms1
 Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI.When broker with clientId "client-1" and user "luise" and password "kapua-password" is listening on topic "$EDC/acme/client-1/foo"2 ms1
 Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed.Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed2 ms1
 Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed.When broker with clientId "client-1" and user "luise" and password "kapua-password" is listening on topic ""1 ms1
 Scenario: Delete Kapua system user.Scenario: Delete Kapua system user0.18 sec1
 Scenario: Delete a connection from the database.Scenario: Delete a connection from the database0.32 sec1
 Scenario: Delete a connection from the database.Scenario: Delete a connection from the database0.33 sec1
 Scenario: Delete a connection from the database.Scenario: Delete a connection from the database0.24 sec1
 Scenario: Delete a group from the database.Scenario: Delete a group from the database5 ms1
 Scenario: Delete a group from the database.Scenario: Delete a group from the database0.75 sec1
 Scenario: Delete a group from the database.Scenario: Delete a group from the database1.4 sec1
 Scenario: Delete a group from the database - Unknown group ID.Scenario: Delete a group from the database - Unknown group ID1.4 sec1
 Scenario: Delete a group from the database - Unknown group ID.Scenario: Delete a group from the database - Unknown group ID0.68 sec1
 Scenario: Delete a group from the database - Unknown group ID.Scenario: Delete a group from the database - Unknown group ID1.4 sec1
 Scenario: Delete a job.Scenario: Delete a job2 sec1
 Scenario: Delete a job.Scenario: Delete a job0.3 sec1
 Scenario: Delete a job.Scenario: Delete a job1.8 sec1
 Scenario: Delete a job.Scenario: Delete a job1.4 sec1
 Scenario: Delete a job.Scenario: Delete a job1.6 sec1
 Scenario: Delete a job execution item.Scenario: Delete a job execution item0.3 sec1
 Scenario: Delete a job execution item.Scenario: Delete a job execution item0.16 sec1
 Scenario: Delete a job execution item.Scenario: Delete a job execution item4 ms1
 Scenario: Delete a job execution item.Scenario: Delete a job execution item0.14 sec1
 Scenario: Delete a job execution item.Scenario: Delete a job execution item15 ms1
 Scenario: Delete a job execution item twice.Scenario: Delete a job execution item twice0.11 sec1
 Scenario: Delete a job execution item twice.Scenario: Delete a job execution item twice57 ms1
 Scenario: Delete a job execution item twice.Scenario: Delete a job execution item twice91 ms1
 Scenario: Delete a job execution item twice.Scenario: Delete a job execution item twice76 ms1
 Scenario: Delete a job execution item twice.Scenario: Delete a job execution item twice0.1 sec1
 Scenario: Delete a job target.Scenario: Delete a job target0.34 sec1
 Scenario: Delete a job target.Scenario: Delete a job target0.65 sec1
 Scenario: Delete a job target.Scenario: Delete a job target0.68 sec1
 Scenario: Delete a job target.Scenario: Delete a job target0.51 sec1
 Scenario: Delete a job target.Scenario: Delete a job target0.36 sec1
 Scenario: Delete a job target twice.Scenario: Delete a job target twice65 ms1
 Scenario: Delete a job target twice.Scenario: Delete a job target twice0.48 sec1
 Scenario: Delete a job target twice.Scenario: Delete a job target twice82 ms1
 Scenario: Delete a job target twice.Scenario: Delete a job target twice5 ms1
 Scenario: Delete a job target twice.Scenario: Delete a job target twice0.21 sec1
 Scenario: Delete a job twice.Scenario: Delete a job twice0.91 sec1
 Scenario: Delete a job twice.Scenario: Delete a job twice0.32 sec1
 Scenario: Delete a job twice.Scenario: Delete a job twice1.4 sec1
 Scenario: Delete a job twice.Scenario: Delete a job twice0.56 sec1
 Scenario: Delete a job twice.Scenario: Delete a job twice1.1 sec1
 Scenario: Delete a non existent event.Scenario: Delete a non existent event1 sec1
 Scenario: Delete a non existing connection.Scenario: Delete a non existing connection0.23 sec1
 Scenario: Delete a non existing connection.Scenario: Delete a non existing connection3 ms1
 Scenario: Delete a non existing connection.Scenario: Delete a non existing connection0.24 sec1
 Scenario: Delete a non existing permission entity.Scenario: Delete a non existing permission entity0.39 sec1
 Scenario: Delete a non existing permission entity.Scenario: Delete a non existing permission entity0.34 sec1
 Scenario: Delete a non existing permission entity.Scenario: Delete a non existing permission entity0.19 sec1
 Scenario: Delete a non existing permission entity.Scenario: Delete a non existing permission entity1.3 sec1
 Scenario: Delete a non existing role entry.Scenario: Delete a non existing role entry50 ms1
 Scenario: Delete a non existing role entry.Scenario: Delete a non existing role entry17 ms1
 Scenario: Delete a non existing role entry.Scenario: Delete a non existing role entry40 ms1
 Scenario: Delete a non existing role entry.Scenario: Delete a non existing role entry28 ms1
 Scenario: Delete a non existing role entry.Scenario: Delete a non existing role entry3 ms1
 Scenario: Delete a non-existing step.Scenario: Delete a non-existing step0.64 sec1
 Scenario: Delete a non-existing step.Scenario: Delete a non-existing step0.82 sec1
 Scenario: Delete a non-existing step.Scenario: Delete a non-existing step0.98 sec1
 Scenario: Delete a non-existing step.Scenario: Delete a non-existing step0.19 sec1
 Scenario: Delete a non-existing step.Scenario: Delete a non-existing step0.41 sec1
 Scenario: Delete a nonexistent domain.Scenario: Delete a nonexistent domain0.86 sec1
 Scenario: Delete a nonexistent domain.Scenario: Delete a nonexistent domain56 ms1
 Scenario: Delete a nonexistent domain.Scenario: Delete a nonexistent domain1.6 sec1
 Scenario: Delete a step definition.Scenario: Delete a step definition1.3 sec1
 Scenario: Delete a step definition.Scenario: Delete a step definition0.67 sec1
 Scenario: Delete a step definition.Scenario: Delete a step definition0.47 sec1
 Scenario: Delete a step definition.Scenario: Delete a step definition0.3 sec1
 Scenario: Delete a step definition.Scenario: Delete a step definition1.1 sec1
 Scenario: Delete a step definition twice.Scenario: Delete a step definition twice0.73 sec1
 Scenario: Delete a step definition twice.Scenario: Delete a step definition twice0.94 sec1
 Scenario: Delete a step definition twice.Scenario: Delete a step definition twice0.58 sec1
 Scenario: Delete a step definition twice.Scenario: Delete a step definition twice1.1 sec1
 Scenario: Delete a step definition twice.Scenario: Delete a step definition twice0.32 sec1
 Scenario: Delete an access info entity twice.Scenario: Delete an access info entity twice1.6 sec1
 Scenario: Delete an existing access permission entity.Scenario: Delete an existing access permission entity13 ms1
 Scenario: Delete an existing access permission entity.Scenario: Delete an existing access permission entity40 ms1
 Scenario: Delete an existing access permission entity.Scenario: Delete an existing access permission entity3 ms1
 Scenario: Delete an existing access permission entity.Scenario: Delete an existing access permission entity22 ms1
 Scenario: Delete an existing access role entry.Scenario: Delete an existing access role entry5 ms1
 Scenario: Delete an existing access role entry.Scenario: Delete an existing access role entry0.71 sec1
 Scenario: Delete an existing access role entry.Scenario: Delete an existing access role entry18 ms1
 Scenario: Delete an existing account.Scenario: Delete an existing account18 ms1
 Scenario: Delete an existing event.Scenario: Delete an existing event38 ms1
 Scenario: Delete an existing role.Scenario: Delete an existing role3 ms1
 Scenario: Delete an existing role.Scenario: Delete an existing role27 ms1
 Scenario: Delete an existing role.Scenario: Delete an existing role12 ms1
 Scenario: Delete an existing role.Scenario: Delete an existing role40 ms1
 Scenario: Delete an existing role.Scenario: Delete an existing role0.61 sec1
 Scenario: Delete an existing role twice.Scenario: Delete an existing role twice0.54 sec1
 Scenario: Delete an existing role twice.Scenario: Delete an existing role twice0.59 sec1
 Scenario: Delete an existing role twice.Scenario: Delete an existing role twice0.51 sec1
 Scenario: Delete an existing role twice.Scenario: Delete an existing role twice0.38 sec1
 Scenario: Delete an existing step.Scenario: Delete an existing step0.21 sec1
 Scenario: Delete an existing step.Scenario: Delete an existing step0.57 sec1
 Scenario: Delete an existing step.Scenario: Delete an existing step0.43 sec1
 Scenario: Delete an existing step.Scenario: Delete an existing step0.75 sec1
 Scenario: Delete an existing step.Scenario: Delete an existing step0.93 sec1
 Scenario: Delete items based on query results.Scenario: Delete items based on query results4 ms1
 Scenario: Delete items by the datastore ID.Scenario: Delete items by the datastore ID0.13 sec1
 Scenario: Delete nonexisting account.Scenario: Delete nonexisting account0.18 sec1
 Scenario: Delete role permissions.Scenario: Delete role permissions2 sec1
 Scenario: Delete the Kapua system account.Scenario: Delete the Kapua system account11 ms1
 Scenario: Delete the last created domain entry.Scenario: Delete the last created domain entry16 ms1
 Scenario: Delete the last created domain entry.Scenario: Delete the last created domain entry4 ms1
 Scenario: Delete the last created domain entry.Scenario: Delete the last created domain entry50 ms1
 Scenario: Delete the last created domain entry.Scenario: Delete the last created domain entry28 ms1
 Scenario: Delete the last created domain entry.Scenario: Delete the last created domain entry39 ms1
 Scenario: Delete user.Scenario: Delete user72 ms1
 Scenario: Delete user that doesn't exist.Scenario: Delete user that doesn't exist3 ms1
 Scenario: Domain entry query.Scenario: Domain entry query17 ms1
 Scenario: Domain entry query.Scenario: Domain entry query4 ms1
 Scenario: Domain entry query.Scenario: Domain entry query1.2 sec1
 Scenario: Domain with null actions.Scenario: Domain with null actions0.73 sec1
 Scenario: Domain with null actions.Scenario: Domain with null actions3 ms1
 Scenario: Domain with null actions.Scenario: Domain with null actions0.69 sec1
 Scenario: Domain with null actions.Scenario: Domain with null actions0.71 sec1
 Scenario: Domain with null name.Scenario: Domain with null name0.15 sec1
 Scenario: Domain with null name.Scenario: Domain with null name0.12 sec1
 Scenario: Domain with null name.Scenario: Domain with null name0.14 sec1
 Scenario: Domain with null name.Scenario: Domain with null name0.16 sec1
 Scenario: Domain with null name.Scenario: Domain with null name0.17 sec1
 Scenario: Domains with duplicate names.Scenario: Domains with duplicate names0.18 sec1
 Scenario: Domains with duplicate names.Scenario: Domains with duplicate names0.93 sec1
 Scenario: Domains with duplicate names.Scenario: Domains with duplicate names0.91 sec1
 Scenario: Domains with duplicate names.Scenario: Domains with duplicate names0.9 sec1
 Scenario: Duplicate group name in root scope.Scenario: Duplicate group name in root scope0.74 sec1
 Scenario: Duplicate group name in root scope.Scenario: Duplicate group name in root scope0.75 sec1
 Scenario: Duplicate group name in root scope.Scenario: Duplicate group name in root scope3 ms1
 Scenario: Duplicate group name in root scope.Scenario: Duplicate group name in root scope0.73 sec1
 Scenario: Duplicate role names.Scenario: Duplicate role names0.64 sec1
 Scenario: Duplicate role names.Scenario: Duplicate role names0.66 sec1
 Scenario: Duplicate role names.Scenario: Duplicate role names0.68 sec1
 Scenario: Duplicate role names.Scenario: Duplicate role names0.69 sec1
 Scenario: Every account must have the default configuration items.Scenario: Every account must have the default configuration items4 ms1
 Scenario: Find a connection by its client ID.Scenario: Find a connection by its client ID1.8 sec1
 Scenario: Find a group entry in the database.Scenario: Find a group entry in the database0.9 sec1
 Scenario: Find a group entry in the database.Scenario: Find a group entry in the database0.91 sec1
 Scenario: Find a group entry in the database.Scenario: Find a group entry in the database0.87 sec1
 Scenario: Find a group entry in the database.Scenario: Find a group entry in the database0.92 sec1
 Scenario: Find a non existing event.Scenario: Find a non existing event2.3 sec1
 Scenario: Find account by Id.Given An existing account with the name "test_acc_42"2 ms1
 Scenario: Find account by Id.Scenario: Find account by Id3 ms1
 Scenario: Find account by Ids.Scenario: Find account by Ids42 ms1
 Scenario: Find account by name.Scenario: Find account by name0.5 sec1
 Scenario: Find account by random Id.Scenario: Find account by random Id4 ms1
 Scenario: Find all child accounts.Scenario: Find all child accounts1.1 sec1
 Scenario: Find an event by its ID.And I configure the device service2 ms1
 Scenario: Find an event by its ID.Scenario: Find an event by its ID3 ms1
 Scenario: Find an existing access role entity.Scenario: Find an existing access role entity49 ms1
 Scenario: Find an existing access role entity.Scenario: Find an existing access role entity59 ms1
 Scenario: Find an existing access role entity.Scenario: Find an existing access role entity20 ms1
 Scenario: Find an existing access role entity.Scenario: Find an existing access role entity36 ms1
 Scenario: Find an existing access role entity.Scenario: Find an existing access role entity71 ms1
 Scenario: Find by name nonexisting account.Scenario: Find by name nonexisting account23 ms1
 Scenario: Find last created permision.Scenario: Find last created permision61 ms1
 Scenario: Find last created permision.Scenario: Find last created permision16 ms1
 Scenario: Find last created permision.Scenario: Find last created permision71 ms1
 Scenario: Find last created permision.Scenario: Find last created permision4 ms1
 Scenario: Find last created permision.Scenario: Find last created permision47 ms1
 Scenario: Find multiple users.Scenario: Find multiple users4 ms1
 Scenario: Find role by ID.Scenario: Find role by ID0.15 sec1
 Scenario: Find role by ID.Scenario: Find role by ID23 ms1
 Scenario: Find role by ID.Scenario: Find role by ID0.86 sec1
 Scenario: Find role by ID.Scenario: Find role by ID6 ms1
 Scenario: Find the last created domain entry.Scenario: Find the last created domain entry18 ms1
 Scenario: Find the last created domain entry.Scenario: Find the last created domain entry62 ms1
 Scenario: Find the last created domain entry.Scenario: Find the last created domain entry33 ms1
 Scenario: Find the last created domain entry.Scenario: Find the last created domain entry5 ms1
 Scenario: Find user by id.Scenario: Find user by id0.3 sec1
 Scenario: Find user by name.Scenario: Find user by name0.21 sec1
 Scenario: Find user by name that doesn't exist.Scenario: Find user by name that doesn't exist0.22 sec1
 Scenario: Find user with id and scope id that doesn't exist.Scenario: Find user with id and scope id that doesn't exist5 ms1
 Scenario: Generic connection query.Scenario: Generic connection query0.99 sec1
 Scenario: Generic connection query.Scenario: Generic connection query1.6 sec1
 Scenario: Generic connection query.Scenario: Generic connection query1.6 sec1
 Scenario: Get metadata.Scenario: Get metadata4 ms1
 Scenario: Group with a null name.Scenario: Group with a null name0.74 sec1
 Scenario: Group with a null name.Scenario: Group with a null name5 ms1
 Scenario: Group with a null name.Scenario: Group with a null name0.72 sec1
 Scenario: Group with a null name.Scenario: Group with a null name0.75 sec1
 Scenario: Handle account creation.Scenario: Handle account creation2.4 sec1
 Scenario: Handle duplicate account names.Scenario: Handle duplicate account names0.11 sec1
 Scenario: Handle null account name.Scenario: Handle null account name2.4 sec1
 Scenario: Handling of 2 birth messages.Scenario: Handling of 2 birth messages3 ms1
 Scenario: Installing a package.Scenario: Installing a package0.52 sec1
 Scenario: It is possible to change the configuration items.Scenario: It is possible to change the configuration items4 ms1
 Scenario: Job execution factory sanity checks.Scenario: Job execution factory sanity checks0.19 sec1
 Scenario: Job execution factory sanity checks.Scenario: Job execution factory sanity checks0.1 sec1
 Scenario: Job execution factory sanity checks.Scenario: Job execution factory sanity checks0.65 sec1
 Scenario: Job execution factory sanity checks.Scenario: Job execution factory sanity checks0.83 sec1
 Scenario: Job execution factory sanity checks.Scenario: Job execution factory sanity checks5 ms1
 Scenario: Job factory sanity checks.Scenario: Job factory sanity checks0.6 sec1
 Scenario: Job factory sanity checks.Scenario: Job factory sanity checks0.38 sec1
 Scenario: Job factory sanity checks.Scenario: Job factory sanity checks0.5 sec1
 Scenario: Job factory sanity checks.Scenario: Job factory sanity checks0.47 sec1
 Scenario: Job factory sanity checks.Scenario: Job factory sanity checks0.49 sec1
 Scenario: Job target factory sanity checks.Scenario: Job target factory sanity checks0.18 sec1
 Scenario: Job target factory sanity checks.Scenario: Job target factory sanity checks2 ms1
 Scenario: Job target factory sanity checks.Scenario: Job target factory sanity checks26 ms1
 Scenario: Job target factory sanity checks.Scenario: Job target factory sanity checks12 ms1
 Scenario: Job target factory sanity checks.Scenario: Job target factory sanity checks67 ms1
 Scenario: Job with a duplicate name.Scenario: Job with a duplicate name0.15 sec1
 Scenario: Job with a duplicate name.Scenario: Job with a duplicate name7 ms1
 Scenario: Job with a duplicate name.Scenario: Job with a duplicate name0.19 sec1
 Scenario: Job with a duplicate name.Scenario: Job with a duplicate name0.18 sec1
 Scenario: Job with a null name.Scenario: Job with a null name0.48 sec1
 Scenario: Job with a null name.Scenario: Job with a null name75 ms1
 Scenario: Job with a null name.Scenario: Job with a null name0.91 sec1
 Scenario: Job with a null scope ID.Scenario: Job with a null scope ID92 ms1
 Scenario: Job with a null scope ID.Scenario: Job with a null scope ID0.1 sec1
 Scenario: Job with a null scope ID.Scenario: Job with a null scope ID0.49 sec1
 Scenario: Job with a null scope ID.Scenario: Job with a null scope ID3 ms1
 Scenario: Job with a null scope ID.Scenario: Job with a null scope ID0.37 sec1
 Scenario: Job with an empty name.Scenario: Job with an empty name67 ms1
 Scenario: Job with an empty name.Scenario: Job with an empty name82 ms1
 Scenario: Job with an empty name.Scenario: Job with an empty name0.29 sec1
 Scenario: Job with an empty name.Scenario: Job with an empty name49 ms1
 Scenario: Job with an empty name.Scenario: Job with an empty name0.51 sec1
 Scenario: MetricsInfo client ID and topic data based on the client id.Scenario: MetricsInfo client ID and topic data based on the client id3 ms1
 Scenario: MetricsInfo last published date.Scenario: MetricsInfo last published date3 ms1
 Scenario: Modify a role that was deleted.Scenario: Modify a role that was deleted0.27 sec1
 Scenario: Modify a role that was deleted.Scenario: Modify a role that was deleted0.34 sec1
 Scenario: Modify a role that was deleted.Scenario: Modify a role that was deleted0.29 sec1
 Scenario: Modify a role that was deleted.Scenario: Modify a role that was deleted0.3 sec1
 Scenario: Modify a role that was deleted.Scenario: Modify a role that was deleted0.31 sec1
 Scenario: Modify an existing account.Scenario: Modify an existing account11 ms1
 Scenario: Modify nonexisting account.Scenario: Modify nonexisting account0.85 sec1
 Scenario: Nameless role entry.Scenario: Nameless role entry63 ms1
 Scenario: Nameless role entry.Scenario: Nameless role entry8 ms1
 Scenario: Nameless role entry.Scenario: Nameless role entry29 ms1
 Scenario: Nameless role entry.Scenario: Nameless role entry97 ms1
 Scenario: Nameless role entry.Scenario: Nameless role entry46 ms1
 Scenario: Negative scenario when client connects twice with same client id.And topic "$EDC/kapua-sys/client-1/MQTT/BIRTH" content "src/test/resources/mqtt/rpione3_MQTT_BIRTH.mqtt" is published by client named "client-1-1"0 ms1
 Scenario: Negative scenario when client connects twice with same client id.Scenario: Negative scenario when client connects twice with same client id0 ms1
 Scenario: Permission factory sanity checks.Scenario: Permission factory sanity checks0.19 sec1
 Scenario: Permission factory sanity checks.Scenario: Permission factory sanity checks0.16 sec1
 Scenario: Permission factory sanity checks.Scenario: Permission factory sanity checks0.13 sec1
 Scenario: Permission factory sanity checks.Scenario: Permission factory sanity checks0.17 sec1
 Scenario: Permission factory sanity checks.Scenario: Permission factory sanity checks0.11 sec1
 Scenario: Positive scenario without stealing link.Scenario: Positive scenario without stealing link0.15 sec1
 Scenario: Query based on message ordering.Scenario: Query based on message ordering3 ms1
 Scenario: Query based on metrics ordering.Scenario: Query based on metrics ordering0.18 sec1
 Scenario: Query before schema search.Scenario: Query before schema search4 ms1
 Scenario: Query for a specific group by name.Scenario: Query for a specific group by name0.23 sec1
 Scenario: Query for a specific group by name.Scenario: Query for a specific group by name0.98 sec1
 Scenario: Query for a specific group by name.Scenario: Query for a specific group by name1.6 sec1
 Scenario: Query for all the access info entities of a specific user.Scenario: Query for all the access info entities of a specific user3 ms1
 Scenario: Query for all the access info entities of a specific user.Scenario: Query for all the access info entities of a specific user49 ms1
 Scenario: Query for all the access info entities of a specific user.Scenario: Query for all the access info entities of a specific user37 ms1
 Scenario: Query for all the access info entities of a specific user.Scenario: Query for all the access info entities of a specific user26 ms1
 Scenario: Query for all the access info entities of a specific user.Scenario: Query for all the access info entities of a specific user15 ms1
 Scenario: Query for all the access info entities of an invalid user.Scenario: Query for all the access info entities of an invalid user1 sec1
 Scenario: Query for all the access info entities of an invalid user.Scenario: Query for all the access info entities of an invalid user1 sec1
 Scenario: Query for all the access info entities of an invalid user.Scenario: Query for all the access info entities of an invalid user1 sec1
 Scenario: Query for all the access info entities of an invalid user.Scenario: Query for all the access info entities of an invalid user17 ms1
 Scenario: Query for executions of a specific job.Scenario: Query for executions of a specific job97 ms1
 Scenario: Query for executions of a specific job.Scenario: Query for executions of a specific job0.1 sec1
 Scenario: Query for executions of a specific job.Scenario: Query for executions of a specific job73 ms1
 Scenario: Query for executions of a specific job.Scenario: Query for executions of a specific job0.14 sec1
 Scenario: Query for executions of a specific job.Scenario: Query for executions of a specific job85 ms1
 Scenario: Query for jobs with specified name.Scenario: Query for jobs with specified name0.27 sec1
 Scenario: Query for jobs with specified name.Scenario: Query for jobs with specified name0.39 sec1
 Scenario: Query for jobs with specified name.Scenario: Query for jobs with specified name0.51 sec1
 Scenario: Query for jobs with specified name.Scenario: Query for jobs with specified name0.37 sec1
 Scenario: Query for jobs with specified name.Scenario: Query for jobs with specified name0.5 sec1
 Scenario: Query for step definitions.Scenario: Query for step definitions0.65 sec1
 Scenario: Query for step definitions.Scenario: Query for step definitions0.87 sec1
 Scenario: Query for step definitions.Scenario: Query for step definitions0.5 sec1
 Scenario: Query for step definitions.Scenario: Query for step definitions1 sec1
 Scenario: Query for step definitions.Scenario: Query for step definitions0.21 sec1
 Scenario: Query for the targets of a specific job.Scenario: Query for the targets of a specific job0.91 sec1
 Scenario: Query for the targets of a specific job.Scenario: Query for the targets of a specific job0.53 sec1
 Scenario: Query for the targets of a specific job.Scenario: Query for the targets of a specific job0.66 sec1
 Scenario: Query for the targets of a specific job.Scenario: Query for the targets of a specific job1.1 sec1
 Scenario: Query for the targets of a specific job.Scenario: Query for the targets of a specific job0.33 sec1
 Scenario: Query user.Scenario: Query user4 ms1
 Scenario: Regular creation of Access Role entity.Scenario: Regular creation of Access Role entity0.46 sec1
 Scenario: Regular creation of Access Role entity.Scenario: Regular creation of Access Role entity0.72 sec1
 Scenario: Regular creation of Access Role entity.Scenario: Regular creation of Access Role entity0.67 sec1
 Scenario: Regular creation of Access Role entity.Scenario: Regular creation of Access Role entity0.7 sec1
 Scenario: Regular domain.Scenario: Regular domain5 ms1
 Scenario: Regular domain.Scenario: Regular domain56 ms1
 Scenario: Regular domain.Scenario: Regular domain31 ms1
 Scenario: Regular domain.Scenario: Regular domain18 ms1
 Scenario: Regular group in random scope.Scenario: Regular group in random scope0.57 sec1
 Scenario: Regular group in random scope.Scenario: Regular group in random scope4 ms1
 Scenario: Regular group in random scope.Scenario: Regular group in random scope14 ms1
 Scenario: Regular group in random scope.Scenario: Regular group in random scope0.62 sec1
 Scenario: Regular group in random scope.Scenario: Regular group in random scope0.61 sec1
 Scenario: Regular group in root scope.Scenario: Regular group in root scope0.77 sec1
 Scenario: Regular group in root scope.Scenario: Regular group in root scope0.78 sec1
 Scenario: Regular group in root scope.Scenario: Regular group in root scope0.8 sec1
 Scenario: Regular group in root scope.Scenario: Regular group in root scope0.74 sec1
 Scenario: Regular job creation.Scenario: Regular job creation23 ms1
 Scenario: Regular job creation.Scenario: Regular job creation1 sec1
 Scenario: Regular job creation.Scenario: Regular job creation1 sec1
 Scenario: Regular job creation.Scenario: Regular job creation0.97 sec1
 Scenario: Regular job creation.Scenario: Regular job creation1 sec1
 Scenario: Regular job execution creation.Scenario: Regular job execution creation0.4 sec1
 Scenario: Regular job execution creation.Scenario: Regular job execution creation36 ms1
 Scenario: Regular job execution creation.Scenario: Regular job execution creation46 ms1
 Scenario: Regular job execution creation.Scenario: Regular job execution creation26 ms1
 Scenario: Regular job execution creation.Scenario: Regular job execution creation12 ms1
 Scenario: Regular role creation.Scenario: Regular role creation4 ms1
 Scenario: Regular role creation.Scenario: Regular role creation0.67 sec1
 Scenario: Regular role creation.Scenario: Regular role creation0.79 sec1
 Scenario: Regular role creation.Scenario: Regular role creation0.68 sec1
 Scenario: Regular step creation.Scenario: Regular step creation0.21 sec1
 Scenario: Regular step creation.Scenario: Regular step creation0.9 sec1
 Scenario: Regular step creation.Scenario: Regular step creation0.56 sec1
 Scenario: Regular step creation.Scenario: Regular step creation0.35 sec1
 Scenario: Regular step creation.Scenario: Regular step creation0.71 sec1
 Scenario: Regular step definition creation.Scenario: Regular step definition creation4 ms1
 Scenario: Regular step definition creation.Scenario: Regular step definition creation45 ms1
 Scenario: Regular step definition creation.Scenario: Regular step definition creation26 ms1
 Scenario: Regular step definition creation.Scenario: Regular step definition creation36 ms1
 Scenario: Regular step definition creation.Scenario: Regular step definition creation15 ms1
 Scenario: Regular step definition with a property list.Scenario: Regular step definition with a property list0.2 sec1
 Scenario: Regular step definition with a property list.Scenario: Regular step definition with a property list36 ms1
 Scenario: Regular step definition with a property list.Scenario: Regular step definition with a property list0.21 sec1
 Scenario: Regular step definition with a property list.Scenario: Regular step definition with a property list3 ms1
 Scenario: Regular step definition with a property list.Scenario: Regular step definition with a property list47 ms1
 Scenario: Regular target creation.Scenario: Regular target creation1.2 sec1
 Scenario: Regular target creation.Scenario: Regular target creation1.2 sec1
 Scenario: Regular target creation.Scenario: Regular target creation0.18 sec1
 Scenario: Regular target creation.Scenario: Regular target creation1.1 sec1
 Scenario: Regular target creation.Scenario: Regular target creation0.38 sec1
 Scenario: Role entry with no actions.Scenario: Role entry with no actions0.59 sec1
 Scenario: Role entry with no actions.Scenario: Role entry with no actions1.2 sec1
 Scenario: Role entry with no actions.Scenario: Role entry with no actions3 ms1
 Scenario: Search for a non existent client ID.Scenario: Search for a non existent client ID4.3 sec1
 Scenario: Search the role database for a random ID.Scenario: Search the role database for a random ID27 ms1
 Scenario: Search the role database for a random ID.Scenario: Search the role database for a random ID0.83 sec1
 Scenario: Search the role database for a random ID.Scenario: Search the role database for a random ID0.84 sec1
 Scenario: Search the role database for a random ID.Scenario: Search the role database for a random ID8 ms1
 Scenario: Send BIRTH message and then DC message.Scenario: Send BIRTH message and then DC message4 ms1
 Scenario: Send BIRTH message and then DC message while broker ip is NOT set.And Device death message is sent2 ms1
 Scenario: Send BIRTH message and then DC message while broker ip is NOT set.Scenario: Send BIRTH message and then DC message while broker ip is NOT set3 ms1
 Scenario: Send BIRTH message and then DC message while broker ip is set by config file.Scenario: Send BIRTH message and then DC message while broker ip is set by config file4 ms1
 Scenario: Setting configuration without mandatory items must raise an error.Scenario: Setting configuration without mandatory items must raise an error23 ms1
 Scenario: Simple create.Scenario: Simple create1.8 sec1
 Scenario: Simple create.Scenario: Simple create1.8 sec1
 Scenario: Simple create.Scenario: Simple create2.8 sec1
 Scenario: Simple create.Scenario: Simple create1.8 sec1
 Scenario: Simple create.Scenario: Simple create2.2 sec1
 Scenario: Simple positive scenario for creating daily index.And REST response containing text "1-2018-01-02"2 ms1
 Scenario: Simple positive scenario for creating daily index.Scenario: Simple positive scenario for creating daily index2 ms1
 Scenario: Simple positive scenario for creating hourly index.And REST response containing text "1-2018-01-02-10"2 ms1
 Scenario: Simple positive scenario for creating hourly index.Scenario: Simple positive scenario for creating hourly index3 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios4 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios9 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios0 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios4 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios1 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2.9 sec1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios0 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2.7 sec1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios0 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios3 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios0.71 sec1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios1.8 sec1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios8 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios8 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios0.33 sec1
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios0.15 sec1
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios34 ms1
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios0.21 sec1
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios62 ms1
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios0.13 sec1
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios0.62 sec1
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios23 ms1
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios3.8 sec1
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios78 ms1
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios0.18 sec1
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios4.1 sec1
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios0.54 sec1
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios0.15 sec1
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios68 ms1
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios3 sec1
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios3.1 sec1
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios0.13 sec1
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios0.17 sec1
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios3 ms1
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios0.1 sec1
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios15 ms1
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios0.19 sec1
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios0.26 sec1
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios9 ms1
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios0 ms1
 Scenario: Starting and stopping the simulator should create a device entry and properly set its status.Scenario: Starting and stopping the simulator should create a device entry and properly set its status5 ms1
 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 ms1
 Scenario: Stealing link scenario.And topic "$EDC/kapua-sys/client-1/MQTT/BIRTH" content "src/test/resources/mqtt/rpione3_MQTT_BIRTH.mqtt" is published by client named "client-1"0 ms1
 Scenario: Stealing link scenario.Scenario: Stealing link scenario0 ms1
 Scenario: Step definition factory sanity checks.Scenario: Step definition factory sanity checks0.56 sec1
 Scenario: Step definition factory sanity checks.Scenario: Step definition factory sanity checks0.84 sec1
 Scenario: Step definition factory sanity checks.Scenario: Step definition factory sanity checks0.15 sec1
 Scenario: Step definition factory sanity checks.Scenario: Step definition factory sanity checks0.29 sec1
 Scenario: Step definition factory sanity checks.Scenario: Step definition factory sanity checks0.7 sec1
 Scenario: Step definition with a duplicate name.Scenario: Step definition with a duplicate name0.42 sec1
 Scenario: Step definition with a duplicate name.Scenario: Step definition with a duplicate name1.4 sec1
 Scenario: Step definition with a duplicate name.Scenario: Step definition with a duplicate name0.83 sec1
 Scenario: Step definition with a duplicate name.Scenario: Step definition with a duplicate name0.59 sec1
 Scenario: Step definition with a duplicate name.Scenario: Step definition with a duplicate name1.1 sec1
 Scenario: Step definition with a null name.Scenario: Step definition with a null name1 sec1
 Scenario: Step definition with a null name.Scenario: Step definition with a null name0.63 sec1
 Scenario: Step definition with a null name.Scenario: Step definition with a null name0.8 sec1
 Scenario: Step definition with a null name.Scenario: Step definition with a null name0.43 sec1
 Scenario: Step definition with a null name.Scenario: Step definition with a null name0.26 sec1
 Scenario: Step definition with a null scope ID.Scenario: Step definition with a null scope ID0.54 sec1
 Scenario: Step definition with a null scope ID.Scenario: Step definition with a null scope ID13 ms1
 Scenario: Step definition with a null scope ID.Scenario: Step definition with a null scope ID0.82 sec1
 Scenario: Step definition with a null scope ID.Scenario: Step definition with a null scope ID3 ms1
 Scenario: Step definition with a null scope ID.Scenario: Step definition with a null scope ID0.27 sec1
 Scenario: Step definition with an empty name.Scenario: Step definition with an empty name0.23 sec1
 Scenario: Step definition with an empty name.Scenario: Step definition with an empty name1 sec1
 Scenario: Step definition with an empty name.Scenario: Step definition with an empty name0.47 sec1
 Scenario: Step definition with an empty name.Scenario: Step definition with an empty name0.87 sec1
 Scenario: Step definition with an empty name.Scenario: Step definition with an empty name0.7 sec1
 Scenario: Step factory sanity checks.Scenario: Step factory sanity checks0.57 sec1
 Scenario: Step factory sanity checks.Scenario: Step factory sanity checks0.23 sec1
 Scenario: Step factory sanity checks.Scenario: Step factory sanity checks0.41 sec1
 Scenario: Step factory sanity checks.Scenario: Step factory sanity checks1.1 sec1
 Scenario: Step factory sanity checks.Scenario: Step factory sanity checks1.2 sec1
 Scenario: Step with a null scope ID.Scenario: Step with a null scope ID0.38 sec1
 Scenario: Step with a null scope ID.Scenario: Step with a null scope ID0.21 sec1
 Scenario: Step with a null scope ID.Scenario: Step with a null scope ID0.77 sec1
 Scenario: Step with a null scope ID.Scenario: Step with a null scope ID0.93 sec1
 Scenario: Step with a null scope ID.Scenario: Step with a null scope ID0.59 sec1
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios3 ms1
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios5 ms1
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios12 ms1
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios15 ms1
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios3 ms1
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios4 ms1
 Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios6 ms1
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios5 ms1
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios4 ms1
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios4 ms1
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios12 ms1
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios2 ms1
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios0.48 sec1
 Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios21 ms1
 Scenario: Stop event broker after all scenarios.Scenario: Stop event broker after all scenarios4 ms1
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios1 sec1
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios2 ms1
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios8 ms1
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios5 ms1
 Scenario: Target with a null scope ID.Scenario: Target with a null scope ID0.15 sec1
 Scenario: Target with a null scope ID.Scenario: Target with a null scope ID0.18 sec1
 Scenario: Target with a null scope ID.Scenario: Target with a null scope ID0.23 sec1
 Scenario: Target with a null scope ID.Scenario: Target with a null scope ID0.19 sec1
 Scenario: Target with a null scope ID.Scenario: Target with a null scope ID0.27 sec1
 Scenario: Test account query.Scenario: Test account query3 ms1
 Scenario: Test the message store with server timestamp indexing.Scenario: Test the message store with server timestamp indexing3 ms1
 Scenario: Test the message store with timestamp indexing.Scenario: Test the message store with timestamp indexing4 ms1
 Scenario: The Client ID is case sensitive.Scenario: The Client ID is case sensitive1.2 sec1
 Scenario: The Client ID is case sensitive.Scenario: The Client ID is case sensitive1.3 sec1
 Scenario: Unknown configuiration items are silently ignored.Scenario: Unknown configuiration items are silently ignored0.24 sec1
 Scenario: Update a group entry in the database.Scenario: Update a group entry in the database0.65 sec1
 Scenario: Update a group entry in the database.Scenario: Update a group entry in the database0.63 sec1
 Scenario: Update a group entry in the database.Scenario: Update a group entry in the database3 ms1
 Scenario: Update a group entry in the database.Scenario: Update a group entry in the database14 ms1
 Scenario: Update a group entry with a false ID.Scenario: Update a group entry with a false ID39 ms1
 Scenario: Update a group entry with a false ID.Scenario: Update a group entry with a false ID6 ms1
 Scenario: Update a group entry with a false ID.Scenario: Update a group entry with a false ID22 ms1
 Scenario: Update a group entry with a false ID.Scenario: Update a group entry with a false ID0.78 sec1
 Scenario: Update a job XML definition.Scenario: Update a job XML definition0.22 sec1
 Scenario: Update a job XML definition.Scenario: Update a job XML definition0.18 sec1
 Scenario: Update a job XML definition.Scenario: Update a job XML definition0.19 sec1
 Scenario: Update a job XML definition.Scenario: Update a job XML definition0.21 sec1
 Scenario: Update a job XML definition.Scenario: Update a job XML definition0.2 sec1
 Scenario: Update a job description.Scenario: Update a job description0.68 sec1
 Scenario: Update a job description.Scenario: Update a job description0.84 sec1
 Scenario: Update a job description.Scenario: Update a job description0.17 sec1
 Scenario: Update a job description.Scenario: Update a job description1.1 sec1
 Scenario: Update a job description.Scenario: Update a job description0.44 sec1
 Scenario: Update a job name.Scenario: Update a job name0.42 sec1
 Scenario: Update a job name.Scenario: Update a job name0.61 sec1
 Scenario: Update a job name.Scenario: Update a job name0.83 sec1
 Scenario: Update a job name.Scenario: Update a job name1.1 sec1
 Scenario: Update a job name.Scenario: Update a job name1.3 sec1
 Scenario: Update a job target TargetId.Scenario: Update a job target TargetId0.23 sec1
 Scenario: Update a job target TargetId.Scenario: Update a job target TargetId1.1 sec1
 Scenario: Update a job target TargetId.Scenario: Update a job target TargetId0.9 sec1
 Scenario: Update a job target TargetId.Scenario: Update a job target TargetId0.46 sec1
 Scenario: Update a job target TargetId.Scenario: Update a job target TargetId0.69 sec1
 Scenario: Update a job target status.Scenario: Update a job target status0.48 sec1
 Scenario: Update a job target status.Scenario: Update a job target status0.51 sec1
 Scenario: Update a job target status.Scenario: Update a job target status0.32 sec1
 Scenario: Update a job target status.Scenario: Update a job target status61 ms1
 Scenario: Update a job target status.Scenario: Update a job target status0.5 sec1
 Scenario: Update a job target step index.Scenario: Update a job target step index61 ms1
 Scenario: Update a job target step index.Scenario: Update a job target step index96 ms1
 Scenario: Update a job target step index.Scenario: Update a job target step index87 ms1
 Scenario: Update a job target step index.Scenario: Update a job target step index77 ms1
 Scenario: Update a job target step index.Scenario: Update a job target step index3 ms1
 Scenario: Update a nonexistent job.Scenario: Update a nonexistent job0.61 sec1
 Scenario: Update a nonexistent job.Scenario: Update a nonexistent job0.72 sec1
 Scenario: Update a nonexistent job.Scenario: Update a nonexistent job3 ms1
 Scenario: Update a nonexistent job.Scenario: Update a nonexistent job0.26 sec1
 Scenario: Update a nonexistent step definition.Scenario: Update a nonexistent step definition0.35 sec1
 Scenario: Update a nonexistent step definition.Scenario: Update a nonexistent step definition0.98 sec1
 Scenario: Update a nonexistent step definition.Scenario: Update a nonexistent step definition0.81 sec1
 Scenario: Update a nonexistent step definition.Scenario: Update a nonexistent step definition0.17 sec1
 Scenario: Update a nonexistent step definition.Scenario: Update a nonexistent step definition0.55 sec1
 Scenario: Update a step definition name.Scenario: Update a step definition name0.82 sec1
 Scenario: Update a step definition name.Scenario: Update a step definition name0.58 sec1
 Scenario: Update a step definition name.Scenario: Update a step definition name0.17 sec1
 Scenario: Update a step definition name.Scenario: Update a step definition name0.98 sec1
 Scenario: Update a step definition name.Scenario: Update a step definition name0.39 sec1
 Scenario: Update a step definition processor name.Scenario: Update a step definition processor name0.2 sec1
 Scenario: Update a step definition processor name.Scenario: Update a step definition processor name0.73 sec1
 Scenario: Update a step definition processor name.Scenario: Update a step definition processor name0.42 sec1
 Scenario: Update a step definition processor name.Scenario: Update a step definition processor name1.1 sec1
 Scenario: Update a step definition processor name.Scenario: Update a step definition processor name0.93 sec1
 Scenario: Update a step definition target type.Scenario: Update a step definition target type0.46 sec1
 Scenario: Update a step definition target type.Scenario: Update a step definition target type1.1 sec1
 Scenario: Update a step definition target type.Scenario: Update a step definition target type0.25 sec1
 Scenario: Update a step definition target type.Scenario: Update a step definition target type0.73 sec1
 Scenario: Update a step definition target type.Scenario: Update a step definition target type0.94 sec1
 Scenario: Update existing role name.Scenario: Update existing role name1.6 sec1
 Scenario: Update existing role name.Scenario: Update existing role name3 ms1
 Scenario: Update existing role name.Scenario: Update existing role name1.5 sec1
 Scenario: Update the end time of an existing execution item.Scenario: Update the end time of an existing execution item9 ms1
 Scenario: Update the end time of an existing execution item.Scenario: Update the end time of an existing execution item0.82 sec1
 Scenario: Update the end time of an existing execution item.Scenario: Update the end time of an existing execution item0.37 sec1
 Scenario: Update the end time of an existing execution item.Scenario: Update the end time of an existing execution item0.84 sec1
 Scenario: Update the end time of an existing execution item.Scenario: Update the end time of an existing execution item0.85 sec1
 Scenario: Update user.Scenario: Update user0.27 sec1
 Scenario: Update user that doesn't exist.Scenario: Update user that doesn't exist3 ms1
 Scenario: Validate a device client based search with a null client ID.Scenario: Validate a device client based search with a null client ID4 ms1
 Scenario: Validate a device client based search with a null client ID.Scenario: Validate a device client based search with a null client ID0.11 sec1
 Scenario: Validate a device client based search with an empty client ID.Scenario: Validate a device client based search with an empty client ID0.18 sec1
 Scenario: Validate a device client based search with an empty client ID.Scenario: Validate a device client based search with an empty client ID17 ms1
 Scenario: Validate a device client search with null scope.Scenario: Validate a device client search with null scope27 ms1
 Scenario: Validate a device count with a null Scope ID.Scenario: Validate a device count with a null Scope ID78 ms1
 Scenario: Validate a device count with a null Scope ID.Scenario: Validate a device count with a null Scope ID15 ms1
 Scenario: Validate a device count with a null Scope ID.Scenario: Validate a device count with a null Scope ID4 ms1
 Scenario: Validate a device creator with a null client ID.Scenario: Validate a device creator with a null client ID76 ms1
 Scenario: Validate a device creator with a null client ID.Scenario: Validate a device creator with a null client ID48 ms1
 Scenario: Validate a device creator with a null client ID.Scenario: Validate a device creator with a null client ID66 ms1
 Scenario: Validate a device creator with a null scope ID.Scenario: Validate a device creator with a null scope ID0.11 sec1
 Scenario: Validate a device creator with a null scope ID.Scenario: Validate a device creator with a null scope ID0.27 sec1
 Scenario: Validate a device creator with a null scope ID.Scenario: Validate a device creator with a null scope ID68 ms1
 Scenario: Validate a device query with a null Scope ID.Scenario: Validate a device query with a null Scope ID0.11 sec1
 Scenario: Validate a device query with a null Scope ID.Scenario: Validate a device query with a null Scope ID0.23 sec1
 Scenario: Validate a device search with a null device ID.Scenario: Validate a device search with a null device ID38 ms1
 Scenario: Validate a device search with a null device ID.Scenario: Validate a device search with a null device ID5 ms1
 Scenario: Validate a device search with a null device ID.Scenario: Validate a device search with a null device ID59 ms1
 Scenario: Validate a device search with a null scope ID.Scenario: Validate a device search with a null scope ID0.12 sec1
 Scenario: Validate a device search with a null scope ID.Scenario: Validate a device search with a null scope ID0.1 sec1
 Scenario: Validate a null creator.Scenario: Validate a null creator0.2 sec1
 Scenario: Validate a null creator.Scenario: Validate a null creator0.43 sec1
 Scenario: Validate a null device.Scenario: Validate a null device0.12 sec1
 Scenario: Validate a null device count.Scenario: Validate a null device count0.26 sec1
 Scenario: Validate a null device count.Scenario: Validate a null device count93 ms1
 Scenario: Validate a null device count.Scenario: Validate a null device count0.35 sec1
 Scenario: Validate a null device query.Scenario: Validate a null device query48 ms1
 Scenario: Validate a null device query.Scenario: Validate a null device query67 ms1
 Scenario: Validate a regular creator.Scenario: Validate a regular creator0.29 sec1
 Scenario: Validate a regular creator.Scenario: Validate a regular creator0.44 sec1
 Scenario: Validate a regular creator.Scenario: Validate a regular creator0.1 sec1
 Scenario: Validate a regular device.Scenario: Validate a regular device0.2 sec1
 Scenario: Validate a regular device.Scenario: Validate a regular device0.27 sec1
 Scenario: Validate a regular device.Scenario: Validate a regular device3 ms1
 Scenario: Validate a regular device client search.Scenario: Validate a regular device client search0.39 sec1
 Scenario: Validate a regular device client search.Scenario: Validate a regular device client search0.64 sec1
 Scenario: Validate a regular device client search.Scenario: Validate a regular device client search0.86 sec1
 Scenario: Validate a regular device count.Scenario: Validate a regular device count0.33 sec1
 Scenario: Validate a regular device count.Scenario: Validate a regular device count0.2 sec1
 Scenario: Validate a regular device count.Scenario: Validate a regular device count0.27 sec1
 Scenario: Validate a regular device deletion.Scenario: Validate a regular device deletion0.23 sec1
 Scenario: Validate a regular device deletion.Scenario: Validate a regular device deletion76 ms1
 Scenario: Validate a regular device query.Scenario: Validate a regular device query0.25 sec1
 Scenario: Validate a regular device query.Scenario: Validate a regular device query0.38 sec1
 Scenario: Validate a regular device query.Scenario: Validate a regular device query0.12 sec1
 Scenario: Validate a regular device search.Scenario: Validate a regular device search99 ms1
 Scenario: Validate a regular device search.Scenario: Validate a regular device search0.24 sec1
 Scenario: Validate a regular device search.Scenario: Validate a regular device search75 ms1
 Scenario: Validate deleting a device with a null device ID.Scenario: Validate deleting a device with a null device ID16 ms1
 Scenario: Validate deleting a device with a null device ID.Scenario: Validate deleting a device with a null device ID4 ms1
 Scenario: Validate deleting a device with a null scope ID.Scenario: Validate deleting a device with a null scope ID0.19 sec1
 Scenario: Validate deleting a device with a null scope ID.Scenario: Validate deleting a device with a null scope ID3 ms1

All Tests

ClassDurationFail(diff)Skip(diff)Pass(diff)Total(diff)
Scenario: A fresh database must contain 1 default role in the root scope3 ms1+12+203+3
Scenario: A mock test scenario11 sec5+52+207+7
Scenario: A newly created account must have some metadata4 ms1+12+203+3
Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic3 ms2+25+51+18+8
Scenario: Access info service sanity checks4.2 sec4+43+307+7
Scenario: Access service comparison sanity checks0.12 sec4+42+206+6
Scenario: Account based ClientInfo data check0.15 sec1+111+1112+1224+24
Scenario: Account exactly on its expiration date1 ms0014+1414+14
Scenario: Account expiration date test - Parent and child expiration set, then parent expiration date changed to before child expiration date3 ms1+15+506+6
Scenario: Account expiration date test - Parent expiration set, child expiration after father expiration5 ms1+15+506+6
Scenario: Account expiration date test - Parent expiration set, child expiration before father expiration0 ms2+23+305+5
Scenario: Account expiration date test - Parent expiration set, child expiration null0.26 sec1+15+506+6
Scenario: Account name must not be mutable0.23 sec1+15+506+6
Scenario: Account past its expiration date3 ms0014+1414+14
Scenario: Account service metadata3 ms1+11+102+2
Scenario: Account wide metrics check7 ms1+113+1314+1428+28
Scenario: Account with future expiration date3 ms0013+1313+13
Scenario: Account with no expiration date1 ms0013+1313+13
Scenario: All device parameters must match the device creator3 ms003+33+3
Scenario: B1 Broker publish to CTRL_ACC_REPLY9 ms2+25+52+29+9
Scenario: B10 Broker create sub-topic on ACL_DATA_ACC is not allowed3 ms1+18+809+9
Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed3 ms1+17+708+8
Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI3 ms1+18+809+9
Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed4 ms1+18+809+9
Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed6 ms008+88+8
Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY6 ms2+25+52+29+9
Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY7 ms2+25+52+29+9
Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account1 ms009+99+9
Scenario: B5 Broker publish to CTRL_ACC is not allowed0.45 sec1+18+809+9
Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed4 ms1+18+809+9
Scenario: B7 Broker subscribe on CTRL_ACC is not allowed3 ms2+23+33+38+8
Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI0.33 sec1+18+809+9
Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed24 ms1+18+809+9
Scenario: Basic Device Event queries7 ms0014+1414+14
Scenario: Birth and applications event handling0.35 sec1+111+11012+12
Scenario: Birth and death message handling4 ms0012+1212+12
Scenario: Birth and missing event handling3 ms0012+1212+12
Scenario: Birth message handling from a new device4 ms1+112+12013+13
Scenario: Birth message handling from an existing device4 ms1+111+11012+12
Scenario: Both the parent and child accounts do not expire3 ms0011+1111+11
Scenario: Both the parent and child accounts have the same expiration date1 ms0011+1111+11
Scenario: Captured date based ClientInfo data check19 ms0030+3030+30
Scenario: Case sensitivness of named device searches6 ms003+33+3
Scenario: Change an existing step name3.5 sec5+57+7012+12
Scenario: Change the account parent Id0.32 sec1+14+405+5
Scenario: Change the account parent path0.15 sec1+14+405+5
Scenario: Channel info queries based on datastore channel filters14 ms1+124+2425+2550+50
Scenario: ChannelInfo client ID and topic data based on the client id0.19 sec1+113+1314+1428+28
Scenario: ChannelInfo client ID based on the account id7 ms1+112+1213+1326+26
Scenario: ChannelInfo last published date7 ms1+114+1415+1530+30
Scenario: ChannelInfo topic data based on the account id10 ms1+112+1213+1326+26
Scenario: Check account properties68 ms1+13+304+4
Scenario: Check the Device Connection Domain data seetting0.86 sec3+31+104+4
Scenario: Check the database cache coherency11 ms0030+3030+30
Scenario: Check the mapping for message semantic topics10 ms1+114+1415+1530+30
Scenario: Check the message store0.53 sec1+19+910+1020+20
Scenario: Check the sanity of the Device Connection Domain data initialization0.79 sec2+21+103+3
Scenario: Child account expires after parent4 ms009+99+9
Scenario: Child account expires before parent7 ms0011+1111+11
Scenario: Child account has null expiration date1 ms009+99+9
Scenario: Client Id based ClientInfo data check0.11 sec1+113+1314+1428+28
Scenario: Compare domain entries1.5 sec5+51+106+6
Scenario: Connect to the system and publish some data7 ms2+213+135+520+20
Scenario: Connection Service factory sanity checks0.32 sec3+31+104+4
Scenario: Count access info entities in a specific scope8.9 sec4+418+18022+22
Scenario: Count access role entities by scope1.3 sec4+432+32036+36
Scenario: Count connections in empty scope6 ms004+44+4
Scenario: Count connections in scope6 ms005+55+5
Scenario: Count devices in a specific scope6 ms0011+1111+11
Scenario: Count devices with a specific BIOS version6 ms006+66+6
Scenario: Count domains in a blank database4.4 sec4+42+206+6
Scenario: Count domains in the database0.96 sec4+45+509+9
Scenario: Count events in empty scope8 ms0010+1010+10
Scenario: Count events in scope14 ms0014+1414+14
Scenario: Count groups0.38 sec4+411+11015+15
Scenario: Count groups in a blank database1.2 sec4+42+206+6
Scenario: Count job items0.11 sec5+53+308+8
Scenario: Count job items in wrong (empty) scope0.91 sec5+5005+5
Scenario: Count role permissions in specific scopes1.3 sec3+314+14017+17
Scenario: Count roles in specific scopes4.4 sec4+412+12016+16
Scenario: Count step definition items0.56 sec5+53+308+8
Scenario: Count step definitions in wrong (empty) scope3.2 sec5+5005+5
Scenario: Count steps in the database2.8 sec5+510+10015+15
Scenario: Count user3 ms1+15+506+6
Scenario: Create a regular event12 sec2+29+9011+11
Scenario: Create a single device7 ms004+44+4
Scenario: Create an event with a null action4.1 sec2+210+10012+12
Scenario: Create an event with a null scope ID27 ms0010+1010+10
Scenario: Create and count multiple job targets2.4 sec5+57+7012+12
Scenario: Create and count several execution items for a job0.97 sec5+58+8013+13
Scenario: Create index with specific prefix4 ms2+21+110+1013+13
Scenario: Create multiple users58 ms1+14+405+5
Scenario: Create regular access permissions1.1 sec4+414+14018+18
Scenario: Create some regular role permissions0 ms006+66+6
Scenario: Create user that already exist15 ms1+16+607+7
Scenario: Create user that has more than DB allowed length30 ms1+14+405+5
Scenario: Create user with short name0.54 sec1+14+405+5
Scenario: Create user with special characters in his name32 ms1+14+405+5
Scenario: Create with permissions4 ms1+19+9010+10
Scenario: Create with permissions and a role0 ms0013+1313+13
Scenario: Create with permissions and a role in the wrong scope6.3 sec4+49+9013+13
Scenario: Creating index with regular user6 ms0025+2525+25
Scenario: Creating new device and tagging it with specific Tag3 ms1+113+13014+14
Scenario: Creating new device, tagging it with specific Tag and then deleting this Tag3 ms1+115+15016+16
Scenario: Creating tag7 ms007+77+7
Scenario: Creating two indexes with daily index6 ms2+22+213+1317+17
Scenario: Creating two indexes with hourly index4 ms2+22+213+1317+17
Scenario: Creating two indexes with weekly index12 ms0017+1717+17
Scenario: Creating user4.6 sec1+14+405+5
Scenario: Creation of access role with neither acess info and role entities0.11 sec5+57+7012+12
Scenario: Creation of access role without an acess info entity2.3 sec4+47+7011+11
Scenario: D1 Device publish to CTRL_ACC_REPLY0.25 sec1+18+809+9
Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI11 ms2+25+52+29+9
Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed11 ms2+25+52+29+9
Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed7 ms2+203+35+5
Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY10 ms2+25+52+29+9
Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY5 ms2+25+52+29+9
Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account6 ms2+23+34+49+9
Scenario: D5 Device subscribe - publish - admin on CTRL_ACC7 ms2+25+52+29+9
Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI9 ms2+25+52+29+9
Scenario: D7 Device publish to ACL_DATA_ACC is not allowed7 ms2+25+52+29+9
Scenario: D8 Device create sub-topic on ACL_DATA_ACC is not allowed11 ms2+22+25+59+9
Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed9 ms2+22+24+48+8
Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed3 ms1+18+809+9
Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI4 ms1+18+809+9
Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed3 ms2+25+52+29+9
Scenario: DM13 Data manage subscribe on ACL_CTRL_ACC_NOTIFY is not allowed2 ms008+88+8
Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY3 ms1+18+809+9
Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY3 ms1+18+809+9
Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account3 ms1+18+809+9
Scenario: DM5 Data manage publish to CTRL_ACC is not allowed3 ms1+18+809+9
Scenario: DM6 Data manage create sub-topic on CTRL_ACC is not allowed13 ms2+25+52+29+9
Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed7 ms2+23+33+38+8
Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI7 ms2+25+52+29+9
Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC0.16 sec1+18+809+9
Scenario: DV1 Data view publish to CTRL_ACC_REPLY3 ms009+99+9
Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed0.37 sec1+18+809+9
Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed0.42 sec1+19+9010+10
Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed3 ms1+18+809+9
Scenario: DV13 Data view create sub-topic on ACL_CTRL_ACC_CLI is not allowed3 ms1+18+809+9
Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed9 ms2+25+52+29+9
Scenario: DV17 Data view subscribe on ACL_CTRL_ACC_NOTIFY is not allowed0.32 sec1+17+708+8
Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY6 ms2+25+52+29+9
Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY6 ms2+25+52+29+9
Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account4 ms009+99+9
Scenario: DV5 Data view publish to CTRL_ACC is not allowed15 ms2+25+52+29+9
Scenario: DV6 Data view create sub-topic on CTRL_ACC is not allowed8 ms2+25+52+29+9
Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed5 ms008+88+8
Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI6 ms2+25+52+29+9
Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed3 ms2+25+52+29+9
Scenario: Delete Kapua system user0.18 sec1+14+405+5
Scenario: Delete a access info entity with permissions and roles0 ms009+99+9
Scenario: Delete a connection from the database0.9 sec3+36+609+9
Scenario: Delete a group from the database2.2 sec3+35+508+8
Scenario: Delete a group from the database - Unknown group ID3.6 sec3+33+306+6
Scenario: Delete a job7.3 sec5+57+7012+12
Scenario: Delete a job execution item0.63 sec5+55+5010+10
Scenario: Delete a job execution item twice0.43 sec5+56+6011+11
Scenario: Delete a job target2.5 sec5+55+5010+10
Scenario: Delete a job target twice0.84 sec5+56+6011+11
Scenario: Delete a job twice4.3 sec5+56+6011+11
Scenario: Delete a non existent event1 sec1+110+10011+11
Scenario: Delete a non existing connection0.48 sec3+35+508+8
Scenario: Delete a non existing permission entity2.2 sec4+411+11015+15
Scenario: Delete a non existing role entry0.13 sec5+57+7012+12
Scenario: Delete a non-existing step3 sec5+58+8013+13
Scenario: Delete a nonexistent domain2.5 sec3+33+306+6
Scenario: Delete a step definition3.9 sec5+57+7012+12
Scenario: Delete a step definition twice3.7 sec5+56+6011+11
Scenario: Delete an access info entity twice1.6 sec1+17+708+8
Scenario: Delete an access info entity using the wrong scope ID1 ms008+88+8
Scenario: Delete an existing access info entity0 ms009+99+9
Scenario: Delete an existing access permission entity78 ms4+410+10014+14
Scenario: Delete an existing access role entry0.74 sec3+317+17020+20
Scenario: Delete an existing account18 ms1+14+405+5
Scenario: Delete an existing device from the registry8 ms004+44+4
Scenario: Delete an existing event38 ms1+112+12013+13
Scenario: Delete an existing role0.69 sec5+54+409+9
Scenario: Delete an existing role twice2 sec4+410+10014+14
Scenario: Delete an existing step2.9 sec5+57+7012+12
Scenario: Delete items based on query results12 ms1+141+4142+4284+84
Scenario: Delete items by the datastore ID0.14 sec1+132+3233+3366+66
Scenario: Delete middle child expiration3 ms0015+1515+15
Scenario: Delete nonexisting account0.18 sec1+13+304+4
Scenario: Delete nonexisting role permission2 ms0010+1010+10
Scenario: Delete parent expiration2 ms0014+1414+14
Scenario: Delete role permissions2 sec1+16+607+7
Scenario: Delete the Kapua system account11 ms1+14+405+5
Scenario: Delete the last created domain entry0.13 sec5+56+6011+11
Scenario: Delete user72 ms1+15+506+6
Scenario: Delete user that doesn't exist3 ms1+14+405+5
Scenario: Deleting tag1 ms007+77+7
Scenario: Deleting user in account that is higher in hierarchy1 ms0023+2323+23
Scenario: Deleting user in account that is lower in hierarchy1 ms0024+2424+24
Scenario: Device connection update8 ms006+66+6
Scenario: Device factory sanity checks6 ms002+22+2
Scenario: Device queries8 ms0013+1313+13
Scenario: Device query - find by BIOS version9 ms007+77+7
Scenario: Domain entry query1.3 sec3+33+306+6
Scenario: Domain with null actions2.1 sec4+43+307+7
Scenario: Domain with null name0.75 sec5+53+308+8
Scenario: Domains with duplicate names2.9 sec4+46+6010+10
Scenario: Duplicate group name in root scope2.2 sec4+47+7011+11
Scenario: Duplicate role names2.6 sec4+43+307+7
Scenario: Empty query results are supported0 ms005+55+5
Scenario: Event factory sanity checks8 ms006+66+6
Scenario: Event service domain check9 ms006+66+6
Scenario: Every account must have the default configuration items4 ms1+12+203+3
Scenario: Extra long continuous test with multiple subscenarios with LOOSE default connection mode51 ms00418+418418+418
Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode44 ms00396+396396+396
Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode and no previously defined devices27 ms00304+304304+304
Scenario: Find a connection by its IDs5 ms005+55+5
Scenario: Find a connection by its client ID1.8 sec1+14+405+5
Scenario: Find a group entry in the database3.6 sec4+46+6010+10
Scenario: Find a non existing event2.3 sec1+19+9010+10
Scenario: Find account by Id5 ms2+22+204+4
Scenario: Find account by Ids42 ms1+13+304+4
Scenario: Find account by name0.5 sec1+13+304+4
Scenario: Find account by random Id4 ms1+12+203+3
Scenario: Find all child accounts1.1 sec1+12+203+3
Scenario: Find an access info entity1 ms008+88+8
Scenario: Find an access info entity by user ID0 ms007+77+7
Scenario: Find an event by its ID5 ms2+27+71+110+10
Scenario: Find an existing access role entity0.23 sec5+58+8013+13
Scenario: Find by name nonexisting account23 ms1+12+203+3
Scenario: Find device by client ID6 ms003+33+3
Scenario: Find device by registry ID12 ms004+44+4
Scenario: Find last created permision0.19 sec5+57+7012+12
Scenario: Find multiple users4 ms1+14+405+5
Scenario: Find role by ID1 sec4+43+307+7
Scenario: Find the last created domain entry0.11 sec4+43+307+7
Scenario: Find user by id0.3 sec1+14+405+5
Scenario: Find user by name0.21 sec1+14+405+5
Scenario: Find user by name that doesn't exist0.22 sec1+12+203+3
Scenario: Find user with id and scope id that doesn't exist5 ms1+12+203+3
Scenario: Generic connection query4.2 sec3+36+609+9
Scenario: Get metadata4 ms1+12+203+3
Scenario: Group with a null name2.2 sec4+44+408+8
Scenario: Handle account creation2.4 sec1+12+203+3
Scenario: Handle duplicate account names0.11 sec1+14+405+5
Scenario: Handle null account name2.4 sec1+13+304+4
Scenario: Handling of 2 birth messages3 ms1+111+11012+12
Scenario: Handling of a disconnect message from a non existing device3 ms0010+1010+10
Scenario: I try to find a non-existing connection6 ms005+55+5
Scenario: If user credential expiration date is before today, user can not login2 ms0014+1414+14
Scenario: If user credential expiration date is today, user can not login it is day inclusive2 ms0014+1414+14
Scenario: If user credential expiration date is tomorrow, user can login1 ms0013+1313+13
Scenario: If user credential is in state disabled, user can not login3 ms0014+1414+14
Scenario: If user credential is in state enabled, user can login4 ms0013+1313+13
Scenario: If user expiration date is before today, user can not login9 ms0013+1313+13
Scenario: If user expiration date is today, user can not login because expiration date was reached2 ms0013+1313+13
Scenario: If user expiration date is tomorrow, user can login1 ms0012+1212+12
Scenario: Installing a package0.52 sec1+112+12013+13
Scenario: It is possible to change the configuration items4 ms1+13+304+4
Scenario: It must be possible to query for specific entries in the role database1 ms005+55+5
Scenario: Job execution factory sanity checks1.7 sec5+51+106+6
Scenario: Job factory sanity checks2.4 sec5+52+207+7
Scenario: Job target factory sanity checks0.29 sec5+51+106+6
Scenario: Job with a duplicate name0.53 sec4+45+509+9
Scenario: Job with a null name1.4 sec3+34+407+7
Scenario: Job with a null scope ID1 sec5+55+5010+10
Scenario: Job with an empty name1 sec5+55+5010+10
Scenario: MetricsInfo client ID and topic data based on the client id12 ms1+116+1617+1734+34
Scenario: MetricsInfo last published date10 ms1+123+2324+2448+48
Scenario: Modify a role that was deleted1.5 sec5+55+5010+10
Scenario: Modify an existing account11 ms1+13+304+4
Scenario: Modify last child expiration so that it still expires before parent2 ms0014+1414+14
Scenario: Modify middle child expiration so that it still expires before parent1 ms0014+1414+14
Scenario: Modify middle child expiration to outlive parent3 ms0015+1515+15
Scenario: Modify nonexisting account0.85 sec1+15+506+6
Scenario: Modify parent expiration so that it still expires after child1 ms0014+1414+14
Scenario: Modify parent expiration to before child expiration1 ms0015+1515+15
Scenario: Nameless role entry0.24 sec5+53+308+8
Scenario: Negative scenario when client connects twice with same client id0 ms2+28+81+111+11
Scenario: New connection with reserved ID16 ms0033+3333+33
Scenario: Permission factory sanity checks0.78 sec5+52+207+7
Scenario: Positive scenario without stealing link0.15 sec1+111+11012+12
Scenario: Query based on message ordering9 ms1+19+910+1020+20
Scenario: Query based on metrics ordering0.19 sec1+19+910+1020+20
Scenario: Query before schema search12 ms1+140+4041+4182+82
Scenario: Query for a specific group by name2.9 sec3+313+13016+16
Scenario: Query for all the access info entities of a specific user0.13 sec5+514+14019+19
Scenario: Query for all the access info entities of an invalid user3.1 sec4+46+6010+10
Scenario: Query for executions of a specific job0.5 sec5+515+15020+20
Scenario: Query for jobs with specified name2 sec5+55+5010+10
Scenario: Query for step definitions3.3 sec5+56+6011+11
Scenario: Query for the targets of a specific job3.5 sec5+518+18023+23
Scenario: Query user4 ms1+15+506+6
Scenario: Regular connection9 ms006+66+6
Scenario: Regular creation of Access Role entity2.5 sec4+49+9013+13
Scenario: Regular domain0.11 sec4+43+307+7
Scenario: Regular group in random scope1.8 sec5+54+409+9
Scenario: Regular group in root scope3.1 sec4+44+408+8
Scenario: Regular job creation4.2 sec5+56+6011+11
Scenario: Regular job execution creation0.52 sec5+54+409+9
Scenario: Regular role creation2.1 sec4+45+509+9
Scenario: Regular step creation2.7 sec5+57+7012+12
Scenario: Regular step definition creation0.12 sec5+56+6011+11
Scenario: Regular step definition with a property list0.5 sec5+53+308+8
Scenario: Regular target creation4.2 sec5+54+409+9
Scenario: Role creator sanity checks0 ms002+22+2
Scenario: Role entry with no actions1.8 sec3+33+306+6
Scenario: Role object equality check0 ms002+22+2
Scenario: Role service related objects sanity checks0 ms004+44+4
Scenario: Search for a non existent client ID4.3 sec1+14+405+5
Scenario: Search for an access info entity by an incorrect user ID0 ms008+88+8
Scenario: Search the role database for a random ID1.7 sec4+43+307+7
Scenario: Send BIRTH message and then DC message4 ms1+114+14015+15
Scenario: Send BIRTH message and then DC message while broker ip is NOT set5 ms2+204+46+6
Scenario: Send BIRTH message and then DC message while broker ip is set by System20 ms008+88+8
Scenario: Send BIRTH message and then DC message while broker ip is set by config file4 ms1+17+708+8
Scenario: Setting configuration without mandatory items must raise an error23 ms1+14+405+5
Scenario: Simple create10 sec5+56+6011+11
Scenario: Simple positive scenario for creating daily index4 ms2+21+111+1114+14
Scenario: Simple positive scenario for creating default - weekly index8 ms0012+1212+12
Scenario: Simple positive scenario for creating hourly index6 ms2+21+111+1114+14
Scenario: Start broker for all scenarios13 sec16+1607+723+23
Scenario: Start datastore for all scenarios24 sec18+1806+624+24
Scenario: Start event broker for all scenarios27 sec7+7010+1017+17
Scenario: Starting and stopping the simulator should create a device entry and properly set its status7 ms2+214+144+420+20
Scenario: Stealing link scenario0 ms2+224+242+228+28
Scenario: Step definition factory sanity checks2.5 sec5+51+106+6
Scenario: Step definition with a duplicate name4.4 sec5+55+5010+10
Scenario: Step definition with a null name3.1 sec5+55+5010+10
Scenario: Step definition with a null scope ID1.6 sec5+55+5010+10
Scenario: Step definition with an empty name3.3 sec5+54+409+9
Scenario: Step factory sanity checks3.6 sec5+51+106+6
Scenario: Step with a null scope ID2.9 sec5+57+7012+12
Scenario: Stop broker after all scenarios6.7 sec7+7011+1118+18
Scenario: Stop datastore after all scenario0.62 sec001+11+1
Scenario: Stop datastore after all scenarios5.6 sec7+709+916+16
Scenario: Stop event broker after all scenarios0.58 sec1+101+12+2
Scenario: Stop event broker for all scenarios8.1 sec4+4011+1115+15
Scenario: Target with a null scope ID1 sec5+54+409+9
Scenario: Test LOOSE user coupling on single connection12 ms0027+2727+27
Scenario: Test LOOSE user coupling with 3 connections6 ms0037+3737+37
Scenario: Test STRICT user coupling on single connection19 ms0024+2424+24
Scenario: Test STRICT user coupling with 3 connections and a reserved user23 ms0062+6262+62
Scenario: Test STRICT user coupling with user change allowed on single connection9 ms0035+3535+35
Scenario: Test account query3 ms1+13+304+4
Scenario: Test the message store with server timestamp indexing13 ms1+112+1213+1326+26
Scenario: Test the message store with timestamp indexing10 ms1+112+1213+1326+26
Scenario: The Client ID is case sensitive2.6 sec2+26+608+8
Scenario: To be defined0.57 sec015+151+116+16
Scenario: Try to change an existing connection ID7 ms006+66+6
Scenario: Try to create an access into entity with an invalid role id0 ms008+88+8
Scenario: Try to delete a non existing device from the registry9 ms004+44+4
Scenario: Try to find a device with an invalid client ID7 ms003+33+3
Scenario: Try to find a device with an invalid registry ID10 ms003+33+3
Scenario: Try to modify the connection client ID9 ms006+66+6
Scenario: Try to update the device client ID6 ms004+44+4
Scenario: Unknown configuiration items are silently ignored0.24 sec1+13+304+4
Scenario: Update a group entry in the database1.3 sec4+46+6010+10
Scenario: Update a group entry with a false ID0.84 sec4+47+7011+11
Scenario: Update a job XML definition1 sec5+56+6011+11
Scenario: Update a job description3.3 sec5+56+6011+11
Scenario: Update a job name4.3 sec5+56+6011+11
Scenario: Update a job target TargetId3.4 sec5+55+5010+10
Scenario: Update a job target status1.8 sec5+56+6011+11
Scenario: Update a job target step index0.32 sec5+54+409+9
Scenario: Update a non existing device10 ms005+55+5
Scenario: Update a nonexistent job1.6 sec4+46+6010+10
Scenario: Update a nonexistent step definition2.8 sec5+56+6011+11
Scenario: Update a step definition name2.9 sec5+56+6011+11
Scenario: Update a step definition processor name3.4 sec5+57+7012+12
Scenario: Update a step definition target type3.5 sec5+57+7012+12
Scenario: Update an existing device7 ms004+44+4
Scenario: Update existing role name3.1 sec3+34+407+7
Scenario: Update job id of an existing execution item28 ms006+66+6
Scenario: Update the end time of an existing execution item2.8 sec5+56+6011+11
Scenario: Update user0.27 sec1+16+607+7
Scenario: Update user that doesn't exist3 ms1+14+405+5
Scenario: User locking itself out by using out login attempts4 ms0016+1616+16
Scenario: User locking itself out with failed attempts and not waiting to unlock2 ms0017+1717+17
Scenario: User locking itself out with failed attempts and waiting to unlock6 ms0017+1717+17
Scenario: User login with wrong pass, but with enough time between login failures3 ms0019+1919+19
Scenario: User not locking itself out by using less than max failed login attempts2 ms0017+1717+17
Scenario: Validate a device client based search with a null client ID0.12 sec2+23+305+5
Scenario: Validate a device client based search with an empty client ID0.19 sec2+23+305+5
Scenario: Validate a device client search with null scope27 ms1+13+304+4
Scenario: Validate a device count with a null Scope ID97 ms3+34+407+7
Scenario: Validate a device creator with a null client ID0.19 sec3+35+508+8
Scenario: Validate a device creator with a null scope ID0.45 sec3+35+508+8
Scenario: Validate a device query with a null Scope ID0.35 sec2+24+406+6
Scenario: Validate a device search with a null device ID0.1 sec3+33+306+6
Scenario: Validate a device search with a null scope ID0.23 sec2+23+305+5
Scenario: Validate a null creator0.63 sec2+24+406+6
Scenario: Validate a null device0.12 sec1+14+405+5
Scenario: Validate a null device count0.71 sec3+34+407+7
Scenario: Validate a null device query0.11 sec2+24+406+6
Scenario: Validate a regular creator0.84 sec3+33+306+6
Scenario: Validate a regular device0.48 sec3+33+306+6
Scenario: Validate a regular device client search1.9 sec3+32+205+5
Scenario: Validate a regular device count0.8 sec3+33+306+6
Scenario: Validate a regular device deletion0.3 sec2+22+204+4
Scenario: Validate a regular device query0.76 sec3+33+306+6
Scenario: Validate a regular device search0.41 sec3+32+205+5
Scenario: Validate deleting a device with a null device ID20 ms2+23+305+5
Scenario: Validate deleting a device with a null scope ID0.19 sec2+23+305+5
empty) scope0 ms08+808+8