Test Result : (root)

125 failures (+72) , 623 skipped (+219)
16,563 tests (±0)
Took 34 sec.

All Failed Tests

Test NameDurationAge
 Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic.Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic0 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 "#"0 ms1
 Scenario: Add datastore permissions to the role.And I search for data message with id "fake-id"1 ms6
 Scenario: Add datastore permissions to the role.Scenario: Add datastore permissions to the role2 ms6
 Scenario: B1 Broker publish to CTRL_ACC_REPLY.Scenario: B1 Broker publish to CTRL_ACC_REPLY0 ms1
 Scenario: B1 Broker publish to CTRL_ACC_REPLY.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic ""0 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 allowed0 ms1
 Scenario: B10 Broker create sub-topic on ACL_DATA_ACC is not allowed.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic ""0 ms1
 Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI.Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI0 ms1
 Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic "acme/client-1/foo"0 ms1
 Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed0 ms1
 Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic ""0 ms1
 Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY.Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY0 ms1
 Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic ""0 ms1
 Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY.Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY0 ms1
 Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic "$EDC/acme/client-1/CONF-V1/REPLY"0 ms1
 Scenario: B5 Broker publish to CTRL_ACC is not allowed.Scenario: B5 Broker publish to CTRL_ACC is not allowed0 ms1
 Scenario: B5 Broker publish to CTRL_ACC is not allowed.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic ""0 ms1
 Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed.Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed0 ms1
 Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic ""0 ms1
 Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI.Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI0 ms1
 Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic "$EDC/acme/client-1/foo"0 ms1
 Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed.Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed0 ms1
 Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic ""0 ms1
 Scenario: Bug when user can retrieve user in another account if it has other account's user id.Scenario: Bug when user can retrieve user in another account if it has other account's user id3 ms8
 Scenario: Bug when user can retrieve user in another account if it has other account's user id.Then REST POST call at "/v1/authentication/user" with JSON "{"password": "ToManySecrets123#", "username": "kapua-a"}"2 ms8
 Scenario: Check the mapping for message semantic topics.Scenario: Check the mapping for message semantic topics3 ms1
 Scenario: Check the mapping for message semantic topics.Then I store the messages from list "TestMessages" and remember the IDs as "StoredMessageIDs"2 ms1
 Scenario: Connect to the system and publish some data.Scenario: Connect to the system and publish some data2 ms1
 Scenario: Connect to the system and publish some data.Then I expect the number of messages for this device to be 51 ms1
 Scenario: Create same user in different accounts.Scenario: Create same user in different accounts1.9 sec6
 Scenario: Create scheduler with correct end date.Scenario: Create scheduler with correct end date4 ms4
 Scenario: Create scheduler with correct end date.Then I create a new trigger from the existing creator with previously defined date properties2 ms4
 Scenario: Create scheduler with end date before start date.Scenario: Create scheduler with end date before start date14 ms4
 Scenario: Create scheduler with end date before start date.Then I create a new trigger from the existing creator with previously defined date properties14 ms4
 Scenario: Creating unique Access Group with special symbols in description.Scenario: Creating unique Access Group with special symbols in description11 ms26
 Scenario: Creating unique Access Group with special symbols in description.Then I find the group with name "groupName53"11 ms26
 Scenario: D1 Device publish to CTRL_ACC_REPLY.Scenario: D1 Device publish to CTRL_ACC_REPLY1 ms1
 Scenario: D1 Device publish to CTRL_ACC_REPLY.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic ""1 ms1
 Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI.Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI0 ms1
 Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic "acme/client-1/foo"0 ms1
 Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed0 ms1
 Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic ""0 ms1
 Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY.Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY0 ms1
 Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic ""0 ms1
 Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY.Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY0 ms1
 Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic "$EDC/acme/client-1/CONF-V1/REPLY"0 ms1
 Scenario: D5 Device subscribe - publish - admin on CTRL_ACC.Scenario: D5 Device subscribe - publish - admin on CTRL_ACC0 ms1
 Scenario: D5 Device subscribe - publish - admin on CTRL_ACC.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic "$EDC/acme/foo"0 ms1
 Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI.Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI0 ms1
 Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic "$EDC/acme/client-1/foo"0 ms1
 Scenario: D7 Device publish to ACL_DATA_ACC is not allowed.Scenario: D7 Device publish to ACL_DATA_ACC is not allowed0 ms1
 Scenario: D7 Device publish to ACL_DATA_ACC is not allowed.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic ""0 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 allowed0 ms1
 Scenario: D8 Device create sub-topic on ACL_DATA_ACC is not allowed.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic ""0 ms1
 Scenario: DV1 Data view publish to CTRL_ACC_REPLY.Scenario: DV1 Data view publish to CTRL_ACC_REPLY0 ms1
 Scenario: DV1 Data view publish to CTRL_ACC_REPLY.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic ""0 ms1
 Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed.Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed2 ms1
 Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic ""1 ms1
 Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed.Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed0 ms1
 Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic "acme"0 ms1
 Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed.Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed0 ms1
 Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic ""0 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 allowed0 ms1
 Scenario: DV13 Data view create sub-topic on ACL_CTRL_ACC_CLI is not allowed.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic ""0 ms1
 Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed0 ms1
 Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic ""0 ms1
 Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY.Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY0 ms1
 Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic ""0 ms1
 Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY.Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY0 ms1
 Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic "$EDC/acme/client-1/CONF-V1/REPLY"0 ms1
 Scenario: DV5 Data view publish to CTRL_ACC is not allowed.Scenario: DV5 Data view publish to CTRL_ACC is not allowed0 ms1
 Scenario: DV5 Data view publish to CTRL_ACC is not allowed.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic ""0 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 allowed0 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 "KeepCalm123." is listening on topic ""0 ms1
 Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI.Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI0 ms1
 Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic "$EDC/acme/client-1/foo"0 ms1
 Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed.Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed0 ms1
 Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic ""0 ms1
 Scenario: Delete items based on query results.Scenario: Delete items based on query results3 ms1
 Scenario: Delete items based on query results.Then I store the messages from list "TestMessages1" and remember the IDs as "StoredMessageIDs1"2 ms1
 Scenario: Delete items by date ranges.Scenario: Delete items by date ranges3 ms1
 Scenario: Delete items by date ranges.Then I store the messages from list "TestMessages" and remember the IDs as "StoredMessageIDs"2 ms1
 Scenario: Delete items by the datastore ID.Given I delete all indices0 ms1
 Scenario: Delete items by the datastore ID.Scenario: Delete items by the datastore ID1 ms1
 Scenario: Deleting user in account that is higher in hierarchy.Scenario: Deleting user in account that is higher in hierarchy1.8 sec6
 Scenario: Deleting user in account that is lower in hierarchy.Scenario: Deleting user in account that is lower in hierarchy1.9 sec6
 Scenario: Execute possible docker steps to show its usage.Given List images by name "kapua/kapua-broker:1.5.0-SNAPSHOT"2 ms13
 Scenario: Execute possible docker steps to show its usage.Scenario: Execute possible docker steps to show its usage2 ms13
 Scenario: Executing Job And Then Restarting Device.Scenario: Executing Job And Then Restarting Device3 ms2
 Scenario: Executing Job And Then Restarting Device.When I search for events from device "rpione3" in account "kapua-sys"2 ms731
 Scenario: Executing Job When Device Connected After End Date And Time.Scenario: Executing Job When Device Connected After End Date And Time3 ms2
 Scenario: Executing Job When Device Connected After End Date And Time.When I search for events from device "rpione3" in account "kapua-sys"2 ms731
 Scenario: Executing Job When Device Connected After The Specified Start Date And Time.Scenario: Executing Job When Device Connected After The Specified Start Date And Time2 ms2
 Scenario: Executing Job When Device Connected After The Specified Start Date And Time.When I search for events from device "rpione3" in account "kapua-sys"1 ms731
 Scenario: Executing Job When Device Connected Before End Date And Time.Scenario: Executing Job When Device Connected Before End Date And Time2 ms2
 Scenario: Executing Job When Device Connected Before End Date And Time.When I search for events from device "rpione3" in account "kapua-sys"1 ms731
 Scenario: Executing Job When Device Connected Before The Specified Start Date And Time.Scenario: Executing Job When Device Connected Before The Specified Start Date And Time4 ms2
 Scenario: Executing Job When Device Connected Before The Specified Start Date And Time.When I search for events from device "rpione3" in account "kapua-sys"2 ms731
 Scenario: Executing Job Without Steps.Scenario: Executing Job Without Steps3 ms2
 Scenario: Executing Job Without Steps.When I search for events from device "rpione3" in account "kapua-sys"2 ms731
 Scenario: Init Security Context for all scenarios.Scenario: Init Security Context for all scenarios1.9 sec6
 Scenario: List Endpoints Created From Sub-Account.And I create endpoint with schema "Schema1", domain "abc.com" and port 22223 ms6
 Scenario: List Endpoints Created From Sub-Account.Scenario: List Endpoints Created From Sub-Account3 ms6
 Scenario: List Endpoints From "kapua-sys" Account.Scenario: List Endpoints From "kapua-sys" Account1 ms6
 Scenario: List Endpoints From "kapua-sys" Account.Then I find 3 endpoints1 ms6
 Scenario: List Endpoints From Sub-Account Of Another Sub-Account.And I create endpoint with schema "Schema1", domain "abc.com" and port 22222 ms6
 Scenario: List Endpoints From Sub-Account Of Another Sub-Account.Scenario: List Endpoints From Sub-Account Of Another Sub-Account3 ms6
 Scenario: List Endpoints From Sub-account.And I create endpoint with schema "Schema1", domain "abc.com" and port 22222 ms6
 Scenario: List Endpoints From Sub-account.Scenario: List Endpoints From Sub-account4 ms6
 Scenario: Reset Security Context for all scenarios.Scenario: Reset Security Context for all scenarios1.8 sec6
 Scenario: Restarting job with valid Bundle Stop step and multiple devices two times.And Bundles are requested12 ms1
 Scenario: Restarting job with valid Bundle Stop step and multiple devices two times.Scenario: Restarting job with valid Bundle Stop step and multiple devices two times13 ms1
 Scenario: Simple Jetty with rest-api war.Scenario: Simple Jetty with rest-api war3 ms8
 Scenario: Simple Jetty with rest-api war.When REST POST call at "/v1/authentication/user" with JSON "{"password": "kapua-password", "username": "kapua-sys"}"2 ms8
 Scenario: Start Jetty server for all scenarios.Given Start Jetty Server on host "127.0.0.1" at port "8081"1 ms8
 Scenario: Start Jetty server for all scenarios.Scenario: Start Jetty server for all scenarios2 ms8
 Scenario: Start datastore for all scenarios.Given Start Datastore1 ms6
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios2 ms6
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios1.9 sec6
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios1.8 sec6
 Scenario: Update scheduler end date.And I try to edit end date to 13-12-2020 at 10:001 ms4
 Scenario: Update scheduler end date.Scenario: Update scheduler end date2 ms4
 Scenario: Update trigger definition.And I try to edit trigger definition to "Cron Job"1 ms4
 Scenario: Update trigger definition.Scenario: Update trigger definition2 ms4

All Tests

ClassDurationFail(diff)Skip(diff)Pass(diff)Total(diff)
Scenario: A fresh database must contain 1 default role in the root scope7 ms0044
Scenario: A newly created account must have some metadata6 ms0033
Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic0 ms2+25+51-78
Scenario: Access info service sanity checks7 ms0044
Scenario: Access service comparison sanity checks10 ms0033
Scenario: Account based ClientInfo data check14 ms002424
Scenario: Account exactly on its expiration date8 ms001414
Scenario: Account name must not be mutable5 ms0066
Scenario: Account past its expiration date10 ms001414
Scenario: Account wide metrics check18 ms002828
Scenario: Account with future expiration date8 ms001313
Scenario: Account with no expiration date8 ms001313
Scenario: Add Access Info domain permissions to new user15 ms002626
Scenario: Add Account permissions to the role in child account28 ms002828
Scenario: Add Credential domain permissions to new user14 ms001818
Scenario: Add Datastore domain permissions to new user2.1 sec001919
Scenario: Add Device Connection domain permissions to kapua-sys user16 ms001111
Scenario: Add Device Connection domain permissions to new user16 ms002323
Scenario: Add Device Event domain permissions to new user15 ms001616
Scenario: Add Device domain permissions to new user17 ms001717
Scenario: Add Domain domain permissions to kapua-sys user14 ms001717
Scenario: Add Domain domain permissions to new user15 ms003232
Scenario: Add Endpoint Permission To The User17 ms003030
Scenario: Add Endpoint_info permissions to the role in child account22 ms003030
Scenario: Add Group domain permissions to new user19 ms001717
Scenario: Add Group permissions to the role in child account25 ms002626
Scenario: Add Job domain permissions to new user16 ms001919
Scenario: Add Role domain permissions to new user14 ms001717
Scenario: Add Role permissions to the role in child account19 ms002626
Scenario: Add Scheduler Permissions With Job Permissions15 ms003131
Scenario: Add Scheduler Permissions Without Job Permissions13 ms002121
Scenario: Add Scheduler permissions to the role in child account28 ms003636
Scenario: Add Tag domain permissions to new user15 ms001515
Scenario: Add Tag permissions to the role in child account19 ms002626
Scenario: Add User domain permissions to new user16 ms002020
Scenario: Add account permissions to the role20 ms001919
Scenario: Add admin role to the user19 ms004444
Scenario: Add and delete Account permissions from the "admin" role24 ms001414
Scenario: Add and delete Device permissions from the "admin" role25 ms001414
Scenario: Add and delete Endpoint_info permissions from the "admin" role18 ms001414
Scenario: Add and delete Group permissions from the "admin" role18 ms001414
Scenario: Add and delete Job permissions from the "admin" role27 ms001414
Scenario: Add and delete Role permissions from the "admin" role20 ms001414
Scenario: Add and delete User permissions from the "admin" role20 ms001515
Scenario: Add datastore permissions to the role3 ms232227
Scenario: Add deleted role again21 ms001010
Scenario: Add device event permissions to the role26 ms003232
Scenario: Add device permissions to the role19 ms001919
Scenario: Add device permissions to the role in child account20 ms002626
Scenario: Add domain, user and access_info permissions to the role23 ms002323
Scenario: Add endpoint_info permissions to the role19 ms003131
Scenario: Add group permissions to the role20 ms001818
Scenario: Add job permissions to the role28 ms001919
Scenario: Add job permissions to the role in child account22 ms002626
Scenario: Add role permissions to the role29 ms001919
Scenario: Add same permission twice to the same role31 ms001414
Scenario: Add same role to user twice24 ms001313
Scenario: Add scheduler permissions to the role19 ms003131
Scenario: Add tag permissions to the role19 ms001818
Scenario: Add user permissions to the role28 ms001919
Scenario: Add user permissions to the role in child account20 ms002626
Scenario: Adding "Cron Job" Schedule With All Valid Parameters7 ms001010
Scenario: Adding "Cron Job" Schedule With All Valid Parameters And Null Cron Value8 ms001010
Scenario: Adding "Cron Job" Schedule With All Valid Parameters Except Cron Format8 ms001111
Scenario: Adding "Cron Job" Schedule With End Date Only7 ms001010
Scenario: Adding "Cron Job" Schedule With End Time before Start time8 ms001212
Scenario: Adding "Cron Job" Schedule With Non-Unique End Date Parameter8 ms001616
Scenario: Adding "Cron Job" Schedule With Non-Unique Start Date Parameter9 ms001515
Scenario: Adding "Cron Job" Schedule With Start Date Only9 ms001111
Scenario: Adding "Cron Job" Schedule With the same Start and End time10 ms001212
Scenario: Adding "Cron Job" Schedule Without The Start Date Parameter10 ms001010
Scenario: Adding "Device Connect" Schedule With All Valid Parameters8 ms0088
Scenario: Adding "Device Connect" Schedule With End Date Only8 ms001010
Scenario: Adding "Device Connect" Schedule With End Time before Start time8 ms001111
Scenario: Adding "Device Connect" Schedule With Max Length Name8 ms0088
Scenario: Adding "Device Connect" Schedule With Min Length Name8 ms0088
Scenario: Adding "Device Connect" Schedule With Name Only9 ms0099
Scenario: Adding "Device Connect" Schedule With Non-Unique End Date Parameter9 ms001313
Scenario: Adding "Device Connect" Schedule With Non-Unique Name8 ms001414
Scenario: Adding "Device Connect" Schedule With Non-Unique Start Date Parameter8 ms001111
Scenario: Adding "Device Connect" Schedule With Start Date Only9 ms001010
Scenario: Adding "Device Connect" Schedule With the same Start and End time8 ms001111
Scenario: Adding "Device Connect" Schedule Without Name8 ms001010
Scenario: Adding "Device Connect" Schedule Without The Start Date Parameter7 ms0099
Scenario: Adding "Empty" Tag To Device7 ms0055
Scenario: Adding "Interval Job" Schedule With All Valid Parameters8 ms001010
Scenario: Adding "Interval Job" Schedule With End Date Only8 ms001010
Scenario: Adding "Interval Job" Schedule With End Time before Start time7 ms001212
Scenario: Adding "Interval Job" Schedule With Max Length Name7 ms001010
Scenario: Adding "Interval Job" Schedule With Min Length Name9 ms001010
Scenario: Adding "Interval Job" Schedule With Name Only10 ms001010
Scenario: Adding "Interval Job" Schedule With Non-Unique End Date Parameter8 ms001616
Scenario: Adding "Interval Job" Schedule With Non-Unique Name9 ms001515
Scenario: Adding "Interval Job" Schedule With Non-Unique Start Date Parameter10 ms001515
Scenario: Adding "Interval Job" Schedule With Null Interval Number7 ms001212
Scenario: Adding "Interval Job" Schedule With Start Date Only8 ms001111
Scenario: Adding "Interval Job" Schedule With the same Start and End time8 ms001212
Scenario: Adding "Interval Job" Schedule Without Interval Number8 ms001111
Scenario: Adding "Interval Job" Schedule Without The Start Date Parameter9 ms0099
Scenario: Adding "Interval Job" Schedule Without a Name9 ms001111
Scenario: Adding "admin" role to a user in a child account23 ms001414
Scenario: Adding "admin" role to multiple users20 ms001818
Scenario: Adding "admin" role twice26 ms001313
Scenario: Adding Account:Delete permission to user in same scope18 ms002525
Scenario: Adding Account:Delete permission to user in sub-account scope14 ms003030
Scenario: Adding Account:Read and Account:Delete permissions to user in same scope17 ms002121
Scenario: Adding Account:Read and Account:Write permissions to user in same scope13 ms001919
Scenario: Adding Account:Read permission to user in same scope15 ms002323
Scenario: Adding Account:Read permission to user in sub-account scope18 ms002929
Scenario: Adding Account:Write and Account:Delete permission to user in same scope15 ms002323
Scenario: Adding Account:Write permission to user in same scope15 ms002525
Scenario: Adding Account:Write permission to user in sub-account scope14 ms003131
Scenario: Adding Multiple Permissions To User21 ms002020
Scenario: Adding One Permission To User18 ms001111
Scenario: Adding Permissions To Child User15 ms001818
Scenario: Adding Permissions To Parallel User21 ms001818
Scenario: Adding Previously Deleted Permission18 ms002828
Scenario: Adding Previously Deleted Tag From Device Again10 ms001111
Scenario: Adding Regular Device to a Group With Description10 ms001010
Scenario: Adding Regular Device to a Group Without a Description10 ms001212
Scenario: Adding Regular Group Without Description to Device10 ms001010
Scenario: Adding Regular Tag Without Description To Device8 ms0066
Scenario: Adding Same Regular Group Without Description to Device17 ms001414
Scenario: Adding Tag With Long Name Without Description To Device6 ms0066
Scenario: Adding Tag With Numbers Without Description To Device7 ms0066
Scenario: Adding Tag With Short Name Without Description To Device6 ms0066
Scenario: Adding Tag With Special Symbols Without Description To Device6 ms0066
Scenario: Adding all Account permissions to user in same scope15 ms001717
Scenario: Adding all Account permissions to user in sub-account scope14 ms002424
Scenario: Adding existing roles to user22 ms001515
Scenario: Adding role from child account to user in new child account19 ms001515
Scenario: Adding role to multiple users in child account20 ms001818
Scenario: Adding same role twice to user in child account20 ms001515
Scenario: Adding the same role to user twice in child account21 ms001313
Scenario: All device parameters must match the device creator7 ms0033
Scenario: Assign 100 Devices to One Group20 ms001111
Scenario: B1 Broker publish to CTRL_ACC_REPLY0 ms2+25+52-79
Scenario: B10 Broker create sub-topic on ACL_DATA_ACC is not allowed0 ms2+25+52-79
Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed4 ms0088
Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI0 ms2+25+52-79
Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed0 ms2+25+52-79
Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed4 ms0088
Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY0 ms2+25+52-79
Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY0 ms2+25+52-79
Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account5 ms0099
Scenario: B5 Broker publish to CTRL_ACC is not allowed0 ms2+25+52-79
Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed1 ms2+25+52-79
Scenario: B7 Broker subscribe on CTRL_ACC is not allowed4 ms0088
Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI0 ms2+25+52-79
Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed0 ms2+25+52-79
Scenario: Basic Device Event queries37 ms001010
Scenario: Birth and applications event handling6 ms001212
Scenario: Birth and death message handling7 ms001212
Scenario: Birth and missing event handling7 ms001212
Scenario: Birth message handling from a new device7 ms001313
Scenario: Birth message handling from an existing device7 ms001212
Scenario: Both the parent and child accounts do not expire8 ms001111
Scenario: Both the parent and child accounts have the same expiration date11 ms001111
Scenario: Bug when user can retrieve user in another account if it has other account's user id5 ms2121933
Scenario: Captured date based ClientInfo data check15 ms003030
Scenario: Case sensitiveness of named device searches7 ms0044
Scenario: Change an existing step name5 ms001111
Scenario: Change role name so it is too short5 ms0066
Scenario: Change the account parent path6 ms0055
Scenario: Changing Client ID7 ms0099
Scenario: Changing Description On Group With Long Description11 ms0077
Scenario: Changing Description On Group With Long Name8 ms0077
Scenario: Changing Description On Group With Numbers In Name9 ms001010
Scenario: Changing Description On Group With Permitted Symbols9 ms0077
Scenario: Changing Description On Group With Short Description9 ms0077
Scenario: Changing Description On Group With Short Name9 ms0077
Scenario: Changing Description On Tag With Long Description6 ms0044
Scenario: Changing Description On Tag With Long Name7 ms0055
Scenario: Changing Description On Tag With Numbers In Name7 ms0066
Scenario: Changing Description On Tag With Permitted Symbols In Name8 ms0044
Scenario: Changing Description On Tag With Short Description7 ms0044
Scenario: Changing Description On Tag With Short Name19 ms0044
Scenario: Changing Device Status To Disabled9 ms0099
Scenario: Changing Device Status To Enabled8 ms0099
Scenario: Changing Group's Description To Non-Uniqe One7 ms0077
Scenario: Changing Group's Description To Uniqe One8 ms0077
Scenario: Changing Group's Name To Contain Invalid Symbols In Name Without Changing Description10 ms0088
Scenario: Changing Group's Name To Contain Permitted Symbols In Name Without Changing Description8 ms0077
Scenario: Changing Group's Name To Non-Unique One8 ms0099
Scenario: Changing Group's Name To Short One Without Changing Description8 ms0077
Scenario: Changing Group's Name To Unique One7 ms0077
Scenario: Changing Group's Name To a Long One Without Changing Description10 ms0077
Scenario: Changing Group's Name To a Too Long One Without Changing Description14 ms0088
Scenario: Changing Group's Name To a Too Short One Without Changing Description9 ms0088
Scenario: Changing Tag's Description To Non-Unique One6 ms0055
Scenario: Changing Tag's Description To Unique One6 ms0077
Scenario: Changing Tag's Name To Contain Invalid Symbols In Name Without Description6 ms0055
Scenario: Changing Tag's Name To Contain Permitted Symbols In Name Without Description7 ms0055
Scenario: Changing Tag's Name To Non-Unique One8 ms0066
Scenario: Changing Tag's Name To Short One Without Description7 ms0077
Scenario: Changing Tag's Name To Unique One8 ms0077
Scenario: Changing Tag's Name To a Long One Without Description7 ms0077
Scenario: Changing Tag's Name To a Too Long One Without Description17 ms0055
Scenario: Changing Tag's Name To a Too Short One Without Description7 ms0055
Scenario: Changing description of a nonexisting role5 ms0077
Scenario: Changing job description to non-unique one10 ms0077
Scenario: Changing job description to the long one15 ms0066
Scenario: Changing job description to unique one10 ms0066
Scenario: Changing job description to very short one16 ms0077
Scenario: Changing job name to a long one without description10 ms0077
Scenario: Changing job name to a too long one without description10 ms0055
Scenario: Changing job name to a too short one without description21 ms0066
Scenario: Changing job name to contain invalid symbols in name without description10 ms0044
Scenario: Changing job name to contain permitted symbols in name without description10 ms0055
Scenario: Changing job name to non-unique one10 ms0088
Scenario: Changing job name to short one without description10 ms0077
Scenario: Changing job name to unique one27 ms0099
Scenario: Changing name of a nonexisting role5 ms0077
Scenario: Changing role description to a valid one5 ms0066
Scenario: Changing role name so it is too long5 ms0066
Scenario: Changing role name to contain special character7 ms0044
Scenario: Changing role name to null5 ms0066
Scenario: Changing role's name to a valid one5 ms0066
Scenario: Channel info queries based on datastore channel filters15 ms005050
Scenario: ChannelInfo client ID and topic data based on the client id14 ms002828
Scenario: ChannelInfo client ID based on the account id14 ms002626
Scenario: ChannelInfo last published date14 ms003030
Scenario: ChannelInfo topic data based on the account id13 ms002626
Scenario: Check account properties8 ms0044
Scenario: Check the Device Connection Domain data seetting5 ms0022
Scenario: Check the database cache coherency17 ms003030
Scenario: Check the mapping for message semantic topics12 ms2+28+820-1030
Scenario: Check the message store18 ms002020
Scenario: Check the sanity of the Device Connection Domain data initialization5 ms0022
Scenario: Child account expires after parent8 ms0099
Scenario: Child account expires before parent9 ms001111
Scenario: Child account has null expiration date10 ms0099
Scenario: Client Id based ClientInfo data check14 ms002828
Scenario: Compare domain entries12 ms0033
Scenario: Connect to the system and publish some data3 ms2+24+416-622
Scenario: Connection Service factory sanity checks5 ms0022
Scenario: Count access info entities in a specific scope55 ms002424
Scenario: Count access role entities by scope11 ms003939
Scenario: Count connections in empty scope6 ms0044
Scenario: Count connections in scope6 ms0055
Scenario: Count devices with a specific BIOS version7 ms0066
Scenario: Count domains in a blank database9 ms0044
Scenario: Count domains in the database10 ms0077
Scenario: Count events in empty scope13 ms0066
Scenario: Count groups8 ms001414
Scenario: Count groups in a blank database8 ms0055
Scenario: Count job items6 ms0077
Scenario: Count job items in wrong - empty - scope4 ms0088
Scenario: Count role permissions in specific scopes9 ms001818
Scenario: Count roles in specific scopes9 ms001515
Scenario: Count step definition items9 ms0044
Scenario: Count step definitions in wrong (empty) scope10 ms0011
Scenario: Count steps in the database5 ms001414
Scenario: Count user9 ms0066
Scenario: Counting created roles items in the DB7 ms0055
Scenario: Create a regular event29 ms0088
Scenario: Create a single device with an empty string for clientID9 ms0044
Scenario: Create a single device with null clientID value9 ms0044
Scenario: Create a valid job entry58 ms0066
Scenario: Create an event with a null scope ID18 ms0077
Scenario: Create and count several execution items for a job6 ms001111
Scenario: Create index with specific prefix7 ms0-20-212+412
Scenario: Create multiple users8 ms0055
Scenario: Create regular access permissions13 ms002020
Scenario: Create same user in different accounts1.9 sec114015
Scenario: Create scheduler with correct end date6 ms2158
Scenario: Create scheduler with empty schedule name25 ms0088
Scenario: Create scheduler with end date before start date28 ms2169
Scenario: Create scheduler with invalid Retry Interval property30 ms0099
Scenario: Create scheduler with invalid cron job trigger property48 ms0099
Scenario: Create scheduler with invalid schedule name35 ms0088
Scenario: Create scheduler with short schedule name21 ms0088
Scenario: Create scheduler with too long schedule name20 ms0088
Scenario: Create scheduler with valid Retry Interval property16 ms0077
Scenario: Create scheduler with valid cron job trigger property39 ms0077
Scenario: Create scheduler with valid schedule name68 ms0066
Scenario: Create scheduler without Cron Job Trigger property36 ms0099
Scenario: Create scheduler without Retry Interval property13 ms0099
Scenario: Create scheduler without start date19 ms0077
Scenario: Create some regular role permissions9 ms0099
Scenario: Create user that already exist8 ms0077
Scenario: Create user that has more than DB allowed length15 ms0055
Scenario: Create user with short name16 ms0055
Scenario: Create user with special characters in his name12 ms0055
Scenario: Create with permissions18 ms001414
Scenario: Create with permissions and a role18 ms001717
Scenario: Create with permissions and a role in the wrong scope10 ms001515
Scenario: Creating 100 Sub-accounts While InfiniteChildAccounts Is Set To True9 ms0077
Scenario: Creating A Device With Disabled Status8 ms0077
Scenario: Creating A Device With Enabled Status7 ms0077
Scenario: Creating A Device With Long Display Name8 ms0077
Scenario: Creating A Device With Long Name6 ms0077
Scenario: Creating A Device With Name Containing Invalid Symbols11 ms0088
Scenario: Creating A Device With Name Containing Permitted Symbols6 ms0077
Scenario: Creating A Device With No Name8 ms0088
Scenario: Creating A Device With Non-unique Display Name6 ms0077
Scenario: Creating A Device With Non-unique Name6 ms001010
Scenario: Creating A Device With Short Display Name7 ms0077
Scenario: Creating A Device With Short Name6 ms0077
Scenario: Creating A Device With Too Long Display Name4 ms0088
Scenario: Creating A Device With Too Long Name8 ms0088
Scenario: Creating A Device With Unique Name8 ms0099
Scenario: Creating A Valid Account7 ms0055
Scenario: Creating An Account With Long Name8 ms0055
Scenario: Creating An Account With Long Organization Name7 ms0055
Scenario: Creating An Account With Non-unique Name8 ms0088
Scenario: Creating An Account With Numbers And Valid Symbols In Name8 ms0055
Scenario: Creating An Account With Short Name8 ms0055
Scenario: Creating An Account With Short Organization Name9 ms0055
Scenario: Creating An Account With Special Symbols In Organization Name8 ms0055
Scenario: Creating An Account With Too Long Organization Name6 ms0066
Scenario: Creating An Account With Unique Name8 ms0077
Scenario: Creating An Account With Wrong TLD Format In Email7 ms001010
Scenario: Creating An Account Without Email8 ms0066
Scenario: Creating An Account Without Name7 ms0066
Scenario: Creating An Account Without Ogranization Name8 ms0066
Scenario: Creating And Account Without "@" In Email9 ms0066
Scenario: Creating Devices And Than Setting Device Service So It Does Not Allow Devices9 ms001212
Scenario: Creating Devices And Then Changing Device Service Values10 ms001010
Scenario: Creating Devices Under Account That Allows Infinite Child Devices10 ms001010
Scenario: Creating Devices Under Account That Does Not Allow Devices8 ms0099
Scenario: Creating Devices Under Account That Has Limited Child Devices23 ms001313
Scenario: Creating Endpoint Non-Unique "Domain Name"5 ms0088
Scenario: Creating Endpoint Non-Unique "Port"5 ms0088
Scenario: Creating Endpoint Non-Unique "Schema"5 ms0099
Scenario: Creating Endpoint With "Domain Name" Only5 ms0066
Scenario: Creating Endpoint With "Port" Only6 ms0066
Scenario: Creating Endpoint With "Schema" Only5 ms0066
Scenario: Creating Endpoint With Disabled Secure Field7 ms0066
Scenario: Creating Endpoint With Enabled Secure Field5 ms0066
Scenario: Creating Endpoint With Invalid "Domain Name"7 ms0066
Scenario: Creating Endpoint With Invalid "Schema" containing symbols3 ms0066
Scenario: Creating Endpoint With Long "Domain Name"6 ms0055
Scenario: Creating Endpoint With Max Length "Port"5 ms0055
Scenario: Creating Endpoint With NULL parameters5 ms0066
Scenario: Creating Endpoint With Schema Containing "http://"5 ms0066
Scenario: Creating Endpoint With Schema Containing "https://"5 ms0066
Scenario: Creating Endpoint With Short "Domain Name"5 ms0066
Scenario: Creating Endpoint With Short "Schema"5 ms0066
Scenario: Creating Endpoint With Small Number "Port"5 ms0066
Scenario: Creating Endpoint With Too Big "Port"5 ms0066
Scenario: Creating Endpoint With Too Long "Domain Name"5 ms0066
Scenario: Creating Endpoint With Too Long "Schema"6 ms0066
Scenario: Creating Endpoint Without "Domain Name"5 ms0066
Scenario: Creating Endpoint Without "Port"7 ms0066
Scenario: Creating Endpoint Without "Schema"5 ms0066
Scenario: Creating Endpoint Without Long "Schema"5 ms0055
Scenario: Creating Endpoint with invalid "Schema" which contains only numbers5 ms0066
Scenario: Creating Group Invalid Symbols In Name Without Description11 ms0077
Scenario: Creating Group With Invalid Symbols In Name With Valid Description7 ms0077
Scenario: Creating Group With Long Name With Valid Description10 ms0066
Scenario: Creating Group With Long Name Without Description8 ms0066
Scenario: Creating Group With Numbers In Name With Valid Description8 ms0088
Scenario: Creating Group With Permitted Symbols And Numbers In Name Without Description8 ms0066
Scenario: Creating Group With Permitted Symbols In Name With Valid Description7 ms0066
Scenario: Creating Group With Short Name With Valid Description9 ms0066
Scenario: Creating Group With Short Name Without Description8 ms0066
Scenario: Creating Group With Too Long Name With Valid Description11 ms0077
Scenario: Creating Group With Too Long Name Without Description8 ms0077
Scenario: Creating Group With Too Short Name With Valid Description11 ms0077
Scenario: Creating Group With Too Short Name Without Description10 ms0077
Scenario: Creating Group Without a Name And With Valid Description8 ms0077
Scenario: Creating Group Without a Name And Without Description8 ms0077
Scenario: Creating Groups And Than Setting Group Service So It Does Not Allow Groups8 ms001111
Scenario: Creating Groups And Then Changing InfiniteChildGroups To False And Set MaxNumberChildGroups7 ms001010
Scenario: Creating Groups Under Account That Allows Infinite Child Groups8 ms0099
Scenario: Creating Groups Under Account That Does Not Allow Groups11 ms0099
Scenario: Creating Groups Under Account That Has Limited Child Groups8 ms001212
Scenario: Creating Jobs And Than Setting Job Service So It Does Not Allow Jobs8 ms001212
Scenario: Creating Jobs And Then Changing Job Service Values9 ms001010
Scenario: Creating Jobs Under Account That Allows Infinite Child Devices9 ms001010
Scenario: Creating Jobs Under Account That Does Not Allow Jobs8 ms0099
Scenario: Creating Jobs Under Account That Has Limited Child Jobs8 ms001313
Scenario: Creating Non-Unique Group With Valid Description8 ms0088
Scenario: Creating Non-Unique Tag With Valid Description8 ms0055
Scenario: Creating Non-unique Group Without Description8 ms0088
Scenario: Creating Non-unique Tag Without Description18 ms0044
Scenario: Creating Roles And Than Setting Role Service So It Does Not Allow Roles8 ms001111
Scenario: Creating Roles And Then Changing Role Service Values8 ms001010
Scenario: Creating Roles Under Account That Allows Infinite Child Roles8 ms001010
Scenario: Creating Roles Under Account That Does Not Allow Roles7 ms0099
Scenario: Creating Roles Under Account That Has Limited Child Roles8 ms001212
Scenario: Creating Sub-accounts When InfiniteChildAccoounts Is Set To False And maxNumberChildAccounts Is Set8 ms001313
Scenario: Creating Sub-accounts When InfiniteChildAccoounts Is Set To True And maxNumberChildAccounts Is Set10 ms001414
Scenario: Creating Sub-accounts When InfiniteChildAccounts Is Set To False8 ms0099
Scenario: Creating Sub-accounts when InfiniteChildAccounts Is Set To True8 ms001212
Scenario: Creating Tag With Invalid Symbols In Name With Valid Description7 ms0044
Scenario: Creating Tag With Invalid Symbols In Name Without Description10 ms0044
Scenario: Creating Tag With Long Name With Valid Description10 ms0044
Scenario: Creating Tag With Long Name Without Description26 ms0044
Scenario: Creating Tag With Numbers In Name With Valid Description8 ms0044
Scenario: Creating Tag With Numbers In Name Without Description10 ms0044
Scenario: Creating Tag With Permitted Symbols In Name With Valid Description8 ms0044
Scenario: Creating Tag With Permitted Symbols In Name Without Description10 ms0044
Scenario: Creating Tag With Short Name With Valid Description9 ms0044
Scenario: Creating Tag With Short Name Without Description34 ms0044
Scenario: Creating Tag With Too Long Name With Valid Description9 ms0044
Scenario: Creating Tag With Too Long Name Without Description12 ms0044
Scenario: Creating Tag With Too Short Name With Valid Description8 ms0044
Scenario: Creating Tag With Too Short Name Without Description12 ms0044
Scenario: Creating Tag Without a Name And With Valid Description8 ms0044
Scenario: Creating Tag Without a Name And Without Description10 ms0044
Scenario: Creating Tags And Than Setting Tag Service So It Does Not Allow Tags8 ms001111
Scenario: Creating Tags And Then Changing Tag Service Values8 ms001010
Scenario: Creating Tags Under Account That Allows Infinite Child Devices8 ms001010
Scenario: Creating Tags Under Account That Does Not Allow Tags8 ms0099
Scenario: Creating Tags Under Account That Has Limited Child Tags8 ms001212
Scenario: Creating Unique Group With Long Description10 ms0066
Scenario: Creating Unique Group With Non-unique Description9 ms0077
Scenario: Creating Unique Group With Short Description9 ms0066
Scenario: Creating Unique Group With Unique Description9 ms0066
Scenario: Creating Unique Group Without Description8 ms0066
Scenario: Creating Unique Tag With Long Description7 ms0044
Scenario: Creating Unique Tag With Non-unique Description8 ms0055
Scenario: Creating Unique Tag With Short Description8 ms0044
Scenario: Creating Unique Tag With Unique Description10 ms0044
Scenario: Creating Unique Tag Without Description32 ms0044
Scenario: Creating Users And Than Setting User Service So It Does Not Allow Users10 ms001111
Scenario: Creating Users And Then Changing User Service Values10 ms001010
Scenario: Creating Users Under Account That Allows Infinite Child Users8 ms001010
Scenario: Creating Users Under Account That Does Not Allow Users24 ms0099
Scenario: Creating Users Under Account That Has Limited Child Users11 ms001212
Scenario: Creating Valid Endpoint6 ms0066
Scenario: Creating a Access Group with invalid special symbols in name2 ms0044
Scenario: Creating a Device With Permitted Symbols in its Display Name7 ms0077
Scenario: Creating a Device With Unique Display Name7 ms0088
Scenario: Creating a job with name only31 ms0066
Scenario: Creating a job with null name30 ms0055
Scenario: Creating a job without name with valid description13 ms0055
Scenario: Creating a new PASSWORD Credential meeting a custom length requirement11 ms0044
Scenario: Creating a new PASSWORD Credential meeting the standard length requirement35 ms0033
Scenario: Creating a new PASSWORD Credential not meeting a custom length requirement11 ms0055
Scenario: Creating a new PASSWORD Credential not meeting the standard length requirement19 ms0044
Scenario: Creating a role name with allowed symbols in its name5 ms0055
Scenario: Creating a role with 255 characters long description4 ms0055
Scenario: Creating a role with a name and description that contain digits only5 ms0055
Scenario: Creating a role with forbidden symbols in its name0 ms0044
Scenario: Creating a role with name only5 ms0055
Scenario: Creating a role with null name5 ms0055
Scenario: Creating a role with regular name and very short description" as description cannot be too short, as even one character is enough7 ms0055
Scenario: Creating a role with special characters in the description5 ms0044
Scenario: Creating a role with the name that contains digits5 ms0055
Scenario: Creating a role with too long name3 ms0055
Scenario: Creating a role with too short name9 ms0055
Scenario: Creating a role with valid name and with too long description7 ms0033
Scenario: Creating a role wtih 255 characters long name5 ms0055
Scenario: Creating a single device with case sensitive clientID8 ms0055
Scenario: Creating a single device with clientID that contains 255 characters8 ms0055
Scenario: Creating a single device with clientID that contains 256 characters6 ms0044
Scenario: Creating a single device with clientID that contains invalid character7 ms0044
Scenario: Creating a single device with clientID that contains invalid characters7 ms0044
Scenario: Creating a single device with spaces in clientID8 ms0055
Scenario: Creating a single device with valid clientID8 ms0055
Scenario: Creating a valid Access Group with numbers in name7 ms0055
Scenario: Creating a valid Access Group with only numbers in name8 ms0055
Scenario: Creating a valid Access Group with unique name10 ms0055
Scenario: Creating a valid Access Group with valid special symbols in name7 ms0055
Scenario: Creating a valid role5 ms0055
Scenario: Creating an Access Group with empty name10 ms0044
Scenario: Creating an Access Group with long name7 ms0055
Scenario: Creating an Access Group with short name8 ms0055
Scenario: Creating an Access Group with too long name8 ms0044
Scenario: Creating an Access Group with too short name7 ms0044
Scenario: Creating an Access Group without name and with description6 ms0044
Scenario: Creating and Deleting Endpoint Two Times12 ms002525
Scenario: Creating index with regular user11 ms002525
Scenario: Creating job with invalid symbols in name without description56 ms0044
Scenario: Creating job with long name and valid description16 ms0066
Scenario: Creating job with long name without description18 ms0066
Scenario: Creating job with numbers in name and valid description11 ms0066
Scenario: Creating job with numbers in name without description16 ms0066
Scenario: Creating job with permitted symbols in name without description17 ms0033
Scenario: Creating job with short name and valid job description14 ms0066
Scenario: Creating job with short name without description19 ms0066
Scenario: Creating job with too long name and valid description11 ms0055
Scenario: Creating job with too long name without description18 ms0055
Scenario: Creating job with too short name and valid description18 ms0055
Scenario: Creating job with too short name without description24 ms0055
Scenario: Creating job without name and without description19 ms0055
Scenario: Creating new device and tagging it with specific Tag8 ms001414
Scenario: Creating new device, tagging it with specific Tag and then deleting this Tag7 ms001616
Scenario: Creating non-unique Access Group9 ms0055
Scenario: Creating non-unique Access Group with unique description6 ms0055
Scenario: Creating non-unique job name with valid job description14 ms0077
Scenario: Creating two device with the same clientID7 ms0055
Scenario: Creating two indexes with daily index8 ms001717
Scenario: Creating two indexes with hourly index9 ms001717
Scenario: Creating two indexes with weekly index11 ms001717
Scenario: Creating two roles with the same description5 ms0066
Scenario: Creating two roles with the same name5 ms0077
Scenario: Creating unique Access Group with long description6 ms0055
Scenario: Creating unique Access Group with non-unique description6 ms0066
Scenario: Creating unique Access Group with numbers in description6 ms0055
Scenario: Creating unique Access Group with only numbers in description7 ms0055
Scenario: Creating unique Access Group with short description6 ms0055
Scenario: Creating unique Access Group with special symbols in description22 ms2114
Scenario: Creating unique Access Group with unique description7 ms0055
Scenario: Creating unique job with long description10 ms0066
Scenario: Creating unique job with non-unique description15 ms001010
Scenario: Creating unique job with short description11 ms0066
Scenario: Creating user30 ms0055
Scenario: Creation of access role with neither acess info and role entities11 ms001212
Scenario: Creation of access role without an acess info entity11 ms001212
Scenario: D1 Device publish to CTRL_ACC_REPLY2 ms2+25+52-79
Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI0 ms2+25+52-79
Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed0 ms2+25+52-79
Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed4 ms0077
Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY0 ms2+25+52-79
Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY0 ms2+25+52-79
Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account6 ms0099
Scenario: D5 Device subscribe - publish - admin on CTRL_ACC0 ms2+25+52-79
Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI1 ms2+25+52-79
Scenario: D7 Device publish to ACL_DATA_ACC is not allowed0 ms2+25+52-79
Scenario: D8 Device create sub-topic on ACL_DATA_ACC is not allowed0 ms2+25+52-79
Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed3 ms0088
Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed17 ms0099
Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI14 ms0099
Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed8 ms0099
Scenario: DM13 Data manage subscribe on ACL_CTRL_ACC_NOTIFY is not allowed10 ms0088
Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY9 ms0099
Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY10 ms0099
Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account7 ms0099
Scenario: DM5 Data manage publish to CTRL_ACC is not allowed9 ms0099
Scenario: DM6 Data manage create sub-topic on CTRL_ACC is not allowed9 ms0099
Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed9 ms0088
Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI5 ms0099
Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC12 ms0099
Scenario: DV1 Data view publish to CTRL_ACC_REPLY0 ms2+25+52-79
Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed3 ms2+25+52-79
Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed0 ms2+26+62-810
Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed0 ms2+25+52-79
Scenario: DV13 Data view create sub-topic on ACL_CTRL_ACC_CLI is not allowed0 ms2+25+52-79
Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed0 ms2+25+52-79
Scenario: DV17 Data view subscribe on ACL_CTRL_ACC_NOTIFY is not allowed4 ms0088
Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY0 ms2+25+52-79
Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY0 ms2+25+52-79
Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account3 ms0099
Scenario: DV5 Data view publish to CTRL_ACC is not allowed0 ms2+25+52-79
Scenario: DV6 Data view create sub-topic on CTRL_ACC is not allowed0 ms2+25+52-79
Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed4 ms0088
Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI0 ms2+25+52-79
Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed1 ms2+25+52-79
Scenario: Decreasing MaxNumberChildAccounts When Sub-accounts Are Already Created7 ms001515
Scenario: Delete Kapua system user9 ms0055
Scenario: Delete a access info entity with permissions and roles38 ms001717
Scenario: Delete a connection from the database5 ms0088
Scenario: Delete a group from the database8 ms001010
Scenario: Delete a group from the database - Unknown group ID7 ms0066
Scenario: Delete a job4 ms001111
Scenario: Delete a job execution item5 ms0088
Scenario: Delete a job execution item twice5 ms0099
Scenario: Delete a job twice5 ms001010
Scenario: Delete a non existent event11 ms0077
Scenario: Delete a non existing connection6 ms0077
Scenario: Delete a non existing permission entity13 ms001616
Scenario: Delete a non existing role entry9 ms001111
Scenario: Delete a non-existing step6 ms001212
Scenario: Delete a nonexistent domain10 ms0055
Scenario: Delete a step definition10 ms0088
Scenario: Delete a step definition twice10 ms0077
Scenario: Delete access role from user22 ms001212
Scenario: Delete an access info entity twice14 ms001111
Scenario: Delete an access info entity using the wrong scope ID15 ms001111
Scenario: Delete an existing access info entity29 ms001212
Scenario: Delete an existing access permission entity12 ms001515
Scenario: Delete an existing access role entry11 ms002222
Scenario: Delete an existing account26 ms0055
Scenario: Delete an existing device from the registry7 ms0044
Scenario: Delete an existing event41 ms0099
Scenario: Delete an existing role8 ms001010
Scenario: Delete an existing role twice10 ms001616
Scenario: Delete an existing step6 ms001111
Scenario: Delete items based on query results13 ms2+231+3151-3384
Scenario: Delete items by date ranges0.47 sec217-40113+40132
Scenario: Delete items by the datastore ID10 ms2+231+3133-3366
Scenario: Delete middle child expiration10 ms001515
Scenario: Delete nonexisting account8 ms0044
Scenario: Delete nonexisting role permission8 ms001313
Scenario: Delete parent expiration8 ms001414
Scenario: Delete permissions from role19 ms001818
Scenario: Delete role permissions8 ms001010
Scenario: Delete scheduler13 ms0088
Scenario: Delete scheduler which doesn't exist19 ms0055
Scenario: Delete the Kapua system account8 ms0055
Scenario: Delete the last created domain entry11 ms0088
Scenario: Delete user10 ms0066
Scenario: Delete user that doesn't exist7 ms0055
Scenario: Deleting "Cron Schedule" Triggering8 ms001313
Scenario: Deleting "Device Schedule" Triggering9 ms001111
Scenario: Deleting "Interval Schedule" Triggering8 ms001313
Scenario: Deleting Device With Disabled Status8 ms001010
Scenario: Deleting Device With Enabled Status7 ms001010
Scenario: Deleting Endpoint Domain Name And Leaving it Empty5 ms0088
Scenario: Deleting Endpoint Which Does Not Exist6 ms0066
Scenario: Deleting Existing Group8 ms0088
Scenario: Deleting Existing Group And Creating It Again With Same Name9 ms001212
Scenario: Deleting Existing Tag And Creating It Again With Same Name6 ms0077
Scenario: Deleting Group's Name And Leaving It Empty Without Changing Description7 ms0088
Scenario: Deleting Non-Existent Tag7 ms0077
Scenario: Deleting Tag From Device8 ms0088
Scenario: Deleting Tag's Name And Leaving It Empty Without Description6 ms0055
Scenario: Deleting Unexisitng Group12 ms001111
Scenario: Deleting a Permission21 ms002121
Scenario: Deleting a non-existing Access Group5 ms0066
Scenario: Deleting a role twice5 ms0077
Scenario: Deleting admin role23 ms0077
Scenario: Deleting an existing Access Group5 ms0055
Scenario: Deleting an existing Access Group and creating it again with the same name5 ms0077
Scenario: Deleting an existing role5 ms0066
Scenario: Deleting default permissions from admin role18 ms001212
Scenario: Deleting existing tag6 ms0099
Scenario: Deleting role after adding it to user23 ms001414
Scenario: Deleting role after it has been added to user in child account19 ms001616
Scenario: Deleting user in account that is higher in hierarchy1.8 sec122023
Scenario: Deleting user in account that is lower in hierarchy1.9 sec123024
Scenario: Device connection update8 ms0077
Scenario: Device factory sanity checks6 ms0022
Scenario: Device queries9 ms001010
Scenario: Device query - find by BIOS version6 ms0077
Scenario: Domain entry query10 ms0055
Scenario: Domain with null actions10 ms0055
Scenario: Domain with null name10 ms0055
Scenario: Domains with duplicate names11 ms0088
Scenario: Duplicate group name in root scope8 ms001010
Scenario: Duplicate role names8 ms0077
Scenario: Editing Access Group description to description with numbers5 ms0055
Scenario: Editing Access Group description to description with only numbers5 ms0055
Scenario: Editing Access Group description to description with special symbols6 ms0044
Scenario: Editing Access Group description to long description5 ms0055
Scenario: Editing Access Group description to non-unique one5 ms0055
Scenario: Editing Access Group description to short description5 ms0055
Scenario: Editing Access Group description to unique one5 ms0077
Scenario: Editing Access Group name to a long one5 ms0077
Scenario: Editing Access Group name to a too long one7 ms0055
Scenario: Editing Access Group name to empty name5 ms0055
Scenario: Editing Access Group name to name that contains numbers6 ms0077
Scenario: Editing Access Group name to name that contains only numbers6 ms0077
Scenario: Editing Access Group name to name with invalid special symbols in name0 ms0055
Scenario: Editing Access Group name to name with valid special symbols6 ms0077
Scenario: Editing Access Group name to non-unique one6 ms0066
Scenario: Editing Access Group name to short one5 ms0077
Scenario: Editing Access Group name to too short one6 ms0055
Scenario: Editing Access Group name to valid one6 ms0077
Scenario: Editing Endpoint Domain Name So It Contains Invalid Symbols5 ms0088
Scenario: Editing Endpoint Domain Name So It Contains Only Numbers5 ms0088
Scenario: Editing Endpoint Domain Name So It Has Max Value5 ms0077
Scenario: Editing Endpoint Domain Name So It Has Min Value5 ms0077
Scenario: Editing Endpoint Domain Name To Non-unique Value5 ms0099
Scenario: Editing Endpoint Domain Name To Unique Value5 ms0077
Scenario: Editing Endpoint Port To Non-unique Value8 ms0099
Scenario: Editing Endpoint Port To Unique Value5 ms0077
Scenario: Editing Endpoint Schema And Leaving It Empty6 ms0088
Scenario: Editing Endpoint Schema So It Contains "http://"7 ms0088
Scenario: Editing Endpoint Schema So It Contains "https://"5 ms0088
Scenario: Editing Endpoint Schema So It Contains Invalid Symbols6 ms0088
Scenario: Editing Endpoint Schema So It Contains Only Numbers8 ms0088
Scenario: Editing Endpoint Schema So It Has Max Length5 ms0077
Scenario: Editing Endpoint Schema So It Has Min Length6 ms0077
Scenario: Editing Endpoint Schema To Non-unique Value5 ms0088
Scenario: Editing Endpoint Schema To Unique Value6 ms0077
Scenario: Editing Endpoint Secure Field To Non-unique Value6 ms0099
Scenario: Editing Endpoint Secure Field To Unique Value7 ms0077
Scenario: Editing Endpoint To NULL Values5 ms001414
Scenario: Editing Endpoint To Non-unique Endpoint5 ms001010
Scenario: Editing Group's Name To Contain Numbers Without Changing Description8 ms0077
Scenario: Editing Tag's Name To Contain Numbers Without Description6 ms0077
Scenario: Empty query results are supported7 ms0088
Scenario: Event factory sanity checks27 ms0022
Scenario: Event service domain check9 ms0022
Scenario: Every account must have the default configuration items6 ms0033
Scenario: Execute possible docker steps to show its usage4 ms231033
Scenario: Executing Job And Then Restarting Device5 ms2331045
Scenario: Executing Job When Device Connected After End Date And Time5 ms2271039
Scenario: Executing Job When Device Connected After The Specified Start Date And Time3 ms2261038
Scenario: Executing Job When Device Connected Before End Date And Time4 ms2271039
Scenario: Executing Job When Device Connected Before The Specified Start Date And Time6 ms2251037
Scenario: Executing Job Without Steps5 ms2281040
Scenario: Extra long continuous test with multiple subscenarios with LOOSE default connection mode18 ms00419419
Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode15 ms00397397
Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode and no previously defined devices16 ms00305305
Scenario: Find a connection by its IDs6 ms0066
Scenario: Find a connection by its client ID6 ms0066
Scenario: Find a group entry in the database8 ms0099
Scenario: Find a non existing event16 ms0066
Scenario: Find account by Id11 ms0044
Scenario: Find account by Ids9 ms0044
Scenario: Find account by name10 ms0044
Scenario: Find account by random Id11 ms0033
Scenario: Find all child accounts18 ms0033
Scenario: Find an access info entity18 ms001111
Scenario: Find an access info entity by user ID16 ms001010
Scenario: Find an event by its ID15 ms0066
Scenario: Find an existing access role entity11 ms001313
Scenario: Find by name nonexisting account8 ms0033
Scenario: Find correct number of messages by corresponding metric0.32 sec005858
Scenario: Find device by client ID7 ms0033
Scenario: Find device by registry ID7 ms0044
Scenario: Find last created permission12 ms001212
Scenario: Find multiple users7 ms0055
Scenario: Find role by ID7 ms0077
Scenario: Find self account by id8 ms001111
Scenario: Find self account by id and scope id12 ms001111
Scenario: Find self account by name10 ms001111
Scenario: Find the last created domain entry8 ms0055
Scenario: Find user by id9 ms0055
Scenario: Find user by its email8 ms0066
Scenario: Find user by its phone number7 ms0066
Scenario: Find user by name9 ms0055
Scenario: Find user by name that doesn't exist7 ms0033
Scenario: Find user with id and scope id that doesn't exist8 ms0033
Scenario: Finding all messages by selecting all metrics0.29 sec004040
Scenario: Finding correct number of messages by corresponding two metrics0.3 sec005252
Scenario: Finding messages with incorrect metric parameters0.36 sec007272
Scenario: Finding user by expiration date in the future8 ms0055
Scenario: Finding user by expiration date in the past8 ms0066
Scenario: Finding user by expiration date in the present8 ms0066
Scenario: Generic connection query6 ms0088
Scenario: Get metadata13 ms0033
Scenario: Group with a null name8 ms0077
Scenario: Handle account creation46 ms0033
Scenario: Handle duplicate account names26 ms0055
Scenario: Handle null account name12 ms0044
Scenario: Handling of 2 birth messages8 ms001212
Scenario: Handling of a disconnect message from a non existing device8 ms001010
Scenario: Have Two Devices in The Same Group Without Description8 ms001313
Scenario: I try to find a non-existing connection5 ms0066
Scenario: If user credential expiration date is before today, user can not login5 ms001414
Scenario: If user credential expiration date is today, user can not login it is day inclusive6 ms001414
Scenario: If user credential expiration date is tomorrow, user can login5 ms001313
Scenario: If user credential is in state disabled, user can not login4 ms001414
Scenario: If user credential is in state enabled, user can login4 ms001313
Scenario: If user expiration date is before today, user can not login5 ms001313
Scenario: If user expiration date is today, user can not login because expiration date was reached6 ms001313
Scenario: If user expiration date is tomorrow, user can login7 ms001212
Scenario: Init Security Context for all scenarios2.6 sec114648
Scenario: Installing a package24 ms001313
Scenario: Interval Job" Schedule With Too Long Name10 ms001111
Scenario: It must be possible to query for specific entries in the role database7 ms0088
Scenario: It should not be possible to change the configuration items10 ms0055
Scenario: Job execution factory sanity checks2 ms0022
Scenario: Job factory sanity checks3 ms0033
Scenario: Job with a duplicate name6 ms0099
Scenario: Job with a null name4 ms0088
Scenario: Job with a null scope ID4 ms0099
Scenario: Job with an empty name5 ms0088
Scenario: List Endpoints Created From Sub-Account6 ms223126
Scenario: List Endpoints From "kapua-sys" Account2 ms24511
Scenario: List Endpoints From Sub-Account Of Another Sub-Account5 ms223126
Scenario: List Endpoints From Sub-account6 ms212115
Scenario: MetricsInfo client ID and topic data based on the client id14 ms003434
Scenario: MetricsInfo last published date14 ms004848
Scenario: Modify a role that was deleted11 ms0099
Scenario: Modify an existing account10 ms0044
Scenario: Modify last child expiration so that it still expires before parent8 ms001414
Scenario: Modify middle child expiration so that it still expires before parent10 ms001414
Scenario: Modify middle child expiration to outlive parent9 ms001515
Scenario: Modify nonexisting account8 ms0066
Scenario: Modify parent expiration so that it still expires after child8 ms001414
Scenario: Modify parent expiration to before child expiration8 ms001515
Scenario: Modifying Sub-account of a different parent account14 ms002525
Scenario: Moving Device From One Group With Description to Another8 ms001414
Scenario: Nameless role entry7 ms0077
Scenario: Negative scenario when client connects twice with same client id12 ms001111
Scenario: New connection with reserved ID12 ms003434
Scenario: Permission factory sanity checks8 ms0033
Scenario: Positive scenario without stealing link15 ms001212
Scenario: Query based on message ordering17 ms002020
Scenario: Query based on metrics ordering17 ms002020
Scenario: Query before schema search7 ms008282
Scenario: Query for a specific group by name8 ms001616
Scenario: Query for all the access info entities of a specific user12 ms001818
Scenario: Query for all the access info entities of an invalid user10 ms001010
Scenario: Query for executions of a specific job6 ms001818
Scenario: Query for jobs with specified name6 ms0099
Scenario: Query for step definitions9 ms0077
Scenario: Query user34 ms0066
Scenario: Querying Other Items With All Account Permissions15 ms003939
Scenario: Regular connection6 ms0077
Scenario: Regular creation of Access Role entity44 ms001414
Scenario: Regular domain10 ms0055
Scenario: Regular group in random scope8 ms0077
Scenario: Regular group in root scope9 ms0077
Scenario: Regular job creation5 ms001010
Scenario: Regular job execution creation5 ms0077
Scenario: Regular role creation7 ms0099
Scenario: Regular step creation6 ms001111
Scenario: Regular step definition creation10 ms0077
Scenario: Regular step definition with a property list10 ms0044
Scenario: Reset Security Context for all scenarios2 sec114648
Scenario: Restarting a job with Asset Write and Bundle Start steps15 ms002828
Scenario: Restarting a job with Command Execution and Bundle Start steps14 ms002828
Scenario: Restarting a job with Configuration Put and Bundle Start steps14 ms002828
Scenario: Restarting a job with Package Uninstall and Bundle Start steps16 ms002828
Scenario: Restarting a job with invalid Configuration Put and multiple devices two times62 ms003333
Scenario: Restarting a job with invalid Configuration Put step two times64 ms003636
Scenario: Restarting a job with invalid Package Install step and multiple devices two times65 ms003131
Scenario: Restarting a job with invalid Package Install step two times21 ms003434
Scenario: Restarting a job with invalid Package Uninstall step and multiple devices two times47 ms003232
Scenario: Restarting a job with invalid Package Uninstall step two times21 ms003434
Scenario: Restarting a job with valid Configuration Put step and multiple devices two times48 ms003333
Scenario: Restarting a job with valid Configuration Put step two times25 ms003636
Scenario: Restarting a job with valid Package Install step and multiple devices two times0.11 sec002929
Scenario: Restarting a job with valid Package Install step two times18 ms003434
Scenario: Restarting a job with valid Package Uninstall step and multiple devices two times21 ms003030
Scenario: Restarting a job with valid Package Uninstall step two times20 ms003232
Scenario: Restarting job With invalid Asset Write and multiple two times17 ms003434
Scenario: Restarting job With valid Asset Write step two times31 ms003636
Scenario: Restarting job with Asset Write and Bundle Start steps and multiple devices14 ms003131
Scenario: Restarting job with Asset Write step17 ms002525
Scenario: Restarting job with Asset Write step and multiple devices15 ms002828
Scenario: Restarting job with Bundle Start step21 ms002525
Scenario: Restarting job with Bundle Start step and multiple devices16 ms002727
Scenario: Restarting job with Bundle Stop and Bundle Start step and multiple devices19 ms003131
Scenario: Restarting job with Bundle Stop and Bundle Start steps20 ms002929
Scenario: Restarting job with Bundle Stop step15 ms002525
Scenario: Restarting job with Bundle Stop step and multiple devices16 ms002727
Scenario: Restarting job with Command Execution and Bundle Start steps and multiple devices21 ms003131
Scenario: Restarting job with Command Execution step26 ms002525
Scenario: Restarting job with Command Execution step and multiple devices18 ms002727
Scenario: Restarting job with Configuration Put and Bundle Start steps and multiple devices14 ms003131
Scenario: Restarting job with Configuration Put step18 ms002525
Scenario: Restarting job with Configuration Put step and multiple devices19 ms002727
Scenario: Restarting job with Package Download/Install and Bundle Start steps and multiple devices42 ms005959
Scenario: Restarting job with Package Download/Install step and multiple devices21 ms002727
Scenario: Restarting job with Package Install step15 ms002525
Scenario: Restarting job with Package Uninstall and Bundle start steps and multiple device19 ms003131
Scenario: Restarting job with Package Uninstall step14 ms002525
Scenario: Restarting job with Package Uninstall step and multiple device14 ms002727
Scenario: Restarting job with invalid Asset Write step two times24 ms003636
Scenario: Restarting job with invalid Bundle Start and Bundle Stop steps and multiple devices two times42 ms004141
Scenario: Restarting job with invalid Bundle Start and Bundle Stop steps two times19 ms004343
Scenario: Restarting job with invalid Bundle Start step and multiple devices two times34 ms003535
Scenario: Restarting job with invalid Bundle Start step two times17 ms003737
Scenario: Restarting job with invalid Bundle Stop step and multiple devices two times74 ms003535
Scenario: Restarting job with invalid Bundle Stop step two times17 ms003737
Scenario: Restarting job with invalid Command Execution and Package Install step two times34 ms003636
Scenario: Restarting job with invalid Command Execution and Package Install steps and multiple devices two times27 ms003737
Scenario: Restarting job with invalid Command Execution step and multiple devices two times55 ms003131
Scenario: Restarting job with invalid Command Execution step two times27 ms003232
Scenario: Restarting job with invalid Configuration Put And Command Execution steps two times15 ms003838
Scenario: Restarting job with invalid Configuration Put and Command Execution steps and multiple devices two times92 ms003737
Scenario: Restarting job with invalid Package Uninstall and Asset Write steps and multiple devices two times25 ms003838
Scenario: Restarting job with invalid Package Uninstall and Asset Write steps two times54 ms004040
Scenario: Restarting job with two Bundle Start steps16 ms002929
Scenario: Restarting job with two Bundle Start steps and multiple devices16 ms003131
Scenario: Restarting job with valid Asset Write step and multiple devices two times21 ms003434
Scenario: Restarting job with valid Bundle Start And Bundle Stop steps two times22 ms004343
Scenario: Restarting job with valid Bundle Start and Bundle Stop steps and multiple devices two times18 ms004141
Scenario: Restarting job with valid Bundle Start step and multiple devices two times81 ms003535
Scenario: Restarting job with valid Bundle Start step two times44 ms003737
Scenario: Restarting job with valid Bundle Stop step and multiple devices two times25 ms2+226+267-2835
Scenario: Restarting job with valid Bundle Stop step two times39 ms003737
Scenario: Restarting job with valid Command Execution and Package Install steps and multiple devices two times0.2 sec003333
Scenario: Restarting job with valid Command Execution and Package Install steps two times81 ms003434
Scenario: Restarting job with valid Command Execution step and multiple devices two times61 ms003131
Scenario: Restarting job with valid Command Execution step two times21 ms003232
Scenario: Restarting job with valid Configuration Put and Command Execution steps and multiple devices two times73 ms003737
Scenario: Restarting job with valid Configuration Put and Command Execution steps two times44 ms003838
Scenario: Restarting job with valid Package Uninstall and Asset Write steps and multiple devices two times0.16 sec003636
Scenario: Restarting job with valid Package Uninstall and Asset Write steps two times20 ms003838
Scenario: Role creator sanity checks5 ms0022
Scenario: Role entry with no actions8 ms0066
Scenario: Role object equality check32 ms0022
Scenario: Role service related objects sanity checks8 ms0044
Scenario: Search By Client ID And Get Multiple Matches22 ms003737
Scenario: Search By Client ID And Get No Matches7 ms001010
Scenario: Search By Client ID And Get One Match15 ms0088
Scenario: Search By Client ID and Display Name8 ms001212
Scenario: Search By Client ID and Serial Number9 ms001212
Scenario: Search By Client ID and Status7 ms001212
Scenario: Search By Client ID, Display Name and Serial Number8 ms001212
Scenario: Search By Client ID, Display Name and Status8 ms001212
Scenario: Search By Client ID, Display Name, Serial Number and Status9 ms001212
Scenario: Search By Device Status And Get No Matches7 ms0088
Scenario: Search By Device's Display Name And Get One Match8 ms0088
Scenario: Search By Display Name and Serial Number7 ms001212
Scenario: Search By Display Name and Status7 ms001212
Scenario: Search By Full Client ID And Get One Match8 ms001010
Scenario: Search By Non-existing Client ID And Get No Matches7 ms0088
Scenario: Search By One Letter Of Display Name7 ms0088
Scenario: Search By One Letter Of Serial Number6 ms001212
Scenario: Search By Serial Number And Get Multiple Matches6 ms001414
Scenario: Search By Serial Number And Get No Matches7 ms001010
Scenario: Search By Serial Number And Get One Match7 ms001111
Scenario: Search By Serial Number and Status8 ms001212
Scenario: Search By Serial Number, Display Name and Status8 ms001212
Scenario: Search By Specific Serial Number7 ms001010
Scenario: Search By Status And Get Multiple Matches7 ms001010
Scenario: Search by Device Status And Get One Match8 ms001010
Scenario: Search for a non existent client ID5 ms0066
Scenario: Search for an access info entity by an incorrect user ID15 ms001111
Scenario: Search the role database for a random ID9 ms0077
Scenario: Send BIRTH message and then DC message30 ms001515
Scenario: Send BIRTH message and then DC message while broker ip is NOT set17 ms0066
Scenario: Send BIRTH message and then DC message while broker ip is set by System21 ms0088
Scenario: Send BIRTH message and then DC message while broker ip is set by config file21 ms0088
Scenario: Set a correct minimum for password length16 ms0033
Scenario: Set an incorrect minimum for password length11 ms0066
Scenario: Set environment variables0.13 sec006161
Scenario: Setting InfiniteChildAccounts To False And Increasing MaxNumberChildAccounts When Sub-accounts Are Already Created7 ms001414
Scenario: Setting InfiniteChildAccounts To False When Sub-accounts Are Already Created8 ms001515
Scenario: Setting InfiniteChildAccounts To True And Decreasing MaxNumberChildAccounts When Sub-accounts Are Already Created9 ms001414
Scenario: Setting Lockout Duration To 0 Seconds8 ms001515
Scenario: Setting Lockout Duration To Negative Value9 ms0077
Scenario: Setting Max Failures To 08 ms001515
Scenario: Setting Max Failures To 110 ms001515
Scenario: Setting Max Failures To 10013 ms001515
Scenario: Setting Max Failures To Negative Value9 ms0077
Scenario: Setting Reset After Login Counter To 0 Seconds11 ms001717
Scenario: Setting Reset After Login Counter To Negative Value7 ms0077
Scenario: Setting configuration without mandatory items must raise an error6 ms0055
Scenario: Simple Jetty with rest-api war5 ms2316
Scenario: Simple create20 ms001111
Scenario: Simple positive scenario for creating daily index11 ms001414
Scenario: Simple positive scenario for creating default - weekly index10 ms001212
Scenario: Simple positive scenario for creating hourly index9 ms001414
Scenario: Start Jetty server for all scenarios3 ms2002
Scenario: Start broker for all scenarios0.31 sec004444
Scenario: Start datastore for all scenarios0.32 sec202830
Scenario: Start event broker for all scenarios2.1 sec115052
Scenario: Starting a job with Asset Write and Bundle Start steps18 ms003636
Scenario: Starting a job with Asset Write step14 ms002525
Scenario: Starting a job with Bundle Start step15 ms003434
Scenario: Starting a job with Bundle Stop and Bundle Start steps15 ms003939
Scenario: Starting a job with Bundle Stop step14 ms003535
Scenario: Starting a job with Command Execution and Bundle Start steps19 ms003737
Scenario: Starting a job with Command Execution step16 ms002525
Scenario: Starting a job with Configuration Put and Bundle Start steps15 ms003737
Scenario: Starting a job with Configuration Put step18 ms002525
Scenario: Starting a job with Package Install and Bundle Start steps18 ms003939
Scenario: Starting a job with Package Install step20 ms003232
Scenario: Starting a job with Package Uninstall and Bundle Start steps19 ms003636
Scenario: Starting a job with Package Uninstall step21 ms003333
Scenario: Starting a job with invalid Asset Write step17 ms003131
Scenario: Starting a job with invalid Asset Write step and multiple targets32 ms002929
Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps18 ms003636
Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps and multiple devices22 ms003535
Scenario: Starting a job with invalid Bundle Start step14 ms003131
Scenario: Starting a job with invalid Bundle Stop step17 ms003131
Scenario: Starting a job with invalid Bundle Stop step and multiple devices29 ms002929
Scenario: Starting a job with invalid Command Execution step26 ms002727
Scenario: Starting a job with invalid Configuration Put step23 ms003030
Scenario: Starting a job with invalid Configuration Put step and multiple devices42 ms002828
Scenario: Starting a job with invalid Package Install step15 ms002929
Scenario: Starting a job with invalid Package Install step and multiple devices48 ms002626
Scenario: Starting a job with invalid Package Uninstall and Asset Write steps23 ms003434
Scenario: Starting a job with invalid Package Uninstall and Asset Write steps and multiple devices35 ms003232
Scenario: Starting a job with invalid Package Uninstall step20 ms002929
Scenario: Starting a job with invalid Package Uninstall step and multiple targets19 ms002626
Scenario: Starting a job with two Bundle Start steps21 ms003939
Scenario: Starting a job with valid Asset Write step26 ms003131
Scenario: Starting a job with valid Asset Write step and multiple targets18 ms002929
Scenario: Starting a job with valid Bundle Start and Bundle Stop steps15 ms003636
Scenario: Starting a job with valid Bundle Start and Bundle Stop steps and multiple devices15 ms003434
Scenario: Starting a job with valid Bundle Start step17 ms003131
Scenario: Starting a job with valid Bundle Stop step23 ms003131
Scenario: Starting a job with valid Bundle Stop step and multiple devices18 ms002929
Scenario: Starting a job with valid Command Execution step20 ms002727
Scenario: Starting a job with valid Configuration Put step21 ms003131
Scenario: Starting a job with valid Configuration Put step and multiple devices15 ms002626
Scenario: Starting a job with valid Package Install step31 ms002929
Scenario: Starting a job with valid Package Install step and multiple devices18 ms002626
Scenario: Starting a job with valid Package Uninstall and Asset Write steps27 ms003333
Scenario: Starting a job with valid Package Uninstall and Asset Write steps and multiple devices26 ms003232
Scenario: Starting a job with valid Package Uninstall step40 ms003030
Scenario: Starting a job with valid Package Uninstall step and multiple targets0.12 sec002626
Scenario: Starting and stopping the simulator should create a device entry and properly set its status7 ms002020
Scenario: Starting job with Asset Write and Bundle Start steps and multiple devices20 ms003232
Scenario: Starting job with Asset Write step and multiple devices15 ms002828
Scenario: Starting job with Bundle Start step and multiple devices17 ms002828
Scenario: Starting job with Bundle Stop and Bundle Start step and multiple devices14 ms003232
Scenario: Starting job with Bundle Stop step and multiple devices16 ms002828
Scenario: Starting job with Command Execution and Bundle Start steps and multiple devices13 ms003232
Scenario: Starting job with Command Execution step and multiple devices13 ms002828
Scenario: Starting job with Configuration Put and Bundle Start steps and multiple devices20 ms003232
Scenario: Starting job with Configuration Put step and multiple devices14 ms002828
Scenario: Starting job with Package Download/Install and Bundle Start steps and multiple devices44 ms003838
Scenario: Starting job with Package Download/Install step and multiple devices96 ms003434
Scenario: Starting job with Package Uninstall and Bundle start steps and multiple device15 ms003232
Scenario: Starting job with Package Uninstall step and multiple device15 ms002727
Scenario: Starting job with invalid Bundle Start step and multiple devices64 ms002929
Scenario: Starting job with invalid Command Execution and Package Install steps14 ms003131
Scenario: Starting job with invalid Command Execution step and multiple devices86 ms002828
Scenario: Starting job with invalid Command Execution, invalid Package Install steps and multiple devices19 ms002929
Scenario: Starting job with invalid Configuration Put and Command Execution steps17 ms003232
Scenario: Starting job with invalid Configuration Put and Command Execution steps and multiple devices34 ms003131
Scenario: Starting job with two Bundle Start steps and multiple devices18 ms003232
Scenario: Starting job with valid Bundle Start step and multiple devices23 ms002929
Scenario: Starting job with valid Command Execution and Package Install steps24 ms003131
Scenario: Starting job with valid Command Execution step and multiple devices0.11 sec002626
Scenario: Starting job with valid Command Execution, valid Package Install steps and multiple devices45 ms002929
Scenario: Starting job with valid Configuration Put and Command Execution steps16 ms003232
Scenario: Starting job with valid Configuration Put and Command Execution steps and multiple devices20 ms003030
Scenario: Stealing link scenario8 ms002828
Scenario: Step definition factory sanity checks9 ms0022
Scenario: Step definition with a duplicate name14 ms0066
Scenario: Step definition with a null name9 ms0066
Scenario: Step definition with a null scope ID10 ms0066
Scenario: Step definition with an empty name10 ms0055
Scenario: Step factory sanity checks3 ms0022
Scenario: Step with a null scope ID4 ms001111
Scenario: Stop Jetty server for all scenarios3 ms0022
Scenario: Stop broker after all scenarios0.23 sec004646
Scenario: Stop datastore after all scenarios0.18 sec003030
Scenario: Stop event broker for all scenarios2 sec115052
Scenario: Stop job with multiple Asset Write and Package Install steps and one target30 ms003737
Scenario: Stop job with multiple Bundle Start and Package Install steps and one target33 ms003737
Scenario: Stop job with multiple Bundle Stop and Package Uninstall steps and one target23 ms003737
Scenario: Stop job with multiple Command Execution and Package Install steps and one target0.21 sec003434
Scenario: Stop job with multiple Configuration Put and Package Uninstall steps and one target19 ms003535
Scenario: Stop job with multiple targets and Asset Write and Package Install steps and one target19 ms003737
Scenario: Stop job with multiple targets and Bundle Start and Package Install steps49 ms003636
Scenario: Stop job with multiple targets and Bundle Stop and Package Uninstall steps85 ms003737
Scenario: Stop job with multiple targets and Command Execution and Package Install steps31 ms003434
Scenario: Stop job with multiple targets and Configuration Put and Package Uninstall steps19 ms003737
Scenario: Test LOOSE user coupling on single connection7 ms002828
Scenario: Test LOOSE user coupling with 3 connections6 ms003838
Scenario: Test STRICT user coupling on single connection10 ms002525
Scenario: Test STRICT user coupling with 3 connections and a reserved user16 ms006363
Scenario: Test STRICT user coupling with user change allowed on single connection8 ms003636
Scenario: Test account query6 ms0044
Scenario: Test the message store with server timestamp indexing14 ms002626
Scenario: Test the message store with timestamp indexing21 ms002626
Scenario: The Client ID is case sensitive5 ms0088
Scenario: To be defined5 ms001313
Scenario: Translating "CommandRequestMessage" to "KuraRequestMessage"53 ms0044
Scenario: Translating CommandRequestMessage to null19 ms0044
Scenario: Translating empty message to empty message21 ms0044
Scenario: Translating from "AssetRequestMessage" to "AssetResponseMessage"11 ms0044
Scenario: Translating invalid jms data message with valid channel, body and metrics into kura data message9 ms0055
Scenario: Translating invalid kura data message with valid channel, body and metrics into jms message7 ms0055
Scenario: Translating invalid kura data message with valid channel, body and metrics into mqtt message7 ms0055
Scenario: Translating kura data message with null channel, and payload without body and with metrics7 ms0055
Scenario: Translating kura data message with valid channel and with null payload8 ms0055
Scenario: Translating kura data message with valid channel and without body and metrics into jms message8 ms0055
Scenario: Translating kura data message with valid channel, and with null payload5 ms0055
Scenario: Translating kura data message with valid channel, body and metrics into jms message6 ms0055
Scenario: Translating kura data message with valid channel, metrics and without body into jms message7 ms0055
Scenario: Translating kura data message with valid channel, metrics and without body into mqtt message6 ms0055
Scenario: Translating null to KuraRequestMessage12 ms0044
Scenario: Translating of jms message with empty payload and invalid topic that contain only userName into kura data message6 ms0055
Scenario: Translating of jms message with empty payload and valid topic into kura data message9 ms0066
Scenario: Translating of jms message with invalid payload and valid topic into kura data message7 ms0066
Scenario: Translating of jms message with valid payload and valid topic into kura data message7 ms0066
Scenario: Translating of mqtt message with invalid payload and invalid topic into kura data message8 ms0055
Scenario: Translating of mqtt message with invalid payload and with null topic into kura data message8 ms0055
Scenario: Translation of kura data message with valid channel and without body and metrics into mqtt message8 ms0055
Scenario: Translation of kura data message with valid channel, body and metrics into mqtt message8 ms0055
Scenario: Translation of kura data message with valid channel, metrics and without body into mqtt message8 ms0055
Scenario: Translation of mqtt message with empty payload into kura data message8 ms0066
Scenario: Translation of mqtt message with invalid payload and invalid topic into kura response message9 ms0055
Scenario: Translation of mqtt message with invalid payload and valid topic into kura data message10 ms0066
Scenario: Translation of mqtt message with invalid payload and valid topic into kura response message8 ms0066
Scenario: Translation of mqtt message with valid payload and invalid topic into kura response message7 ms0055
Scenario: Translation of mqtt message with valid payload and valid topic into kura data message9 ms0066
Scenario: Translation of mqtt message with valid payload and valid topic into kura response message7 ms0066
Scenario: Try to add two different roles with same permissions21 ms002121
Scenario: Try to change an existing connection ID5 ms0077
Scenario: Try to create an access into entity with an invalid role id35 ms001212
Scenario: Try to delete a non existing device from the registry6 ms0044
Scenario: Try to find a device with an invalid client ID6 ms0033
Scenario: Try to find a device with an invalid registry ID8 ms0033
Scenario: Try to find users granted to "admin" role19 ms001212
Scenario: Try to find users that have assigned specific role23 ms001212
Scenario: Try to modify the connection client ID5 ms0077
Scenario: Try to update the device client ID6 ms0044
Scenario: Uncorrect Login While Lockout Policy Is Disabled8 ms001717
Scenario: Uncorrect Login While Lockout Policy Is Enabled9 ms001717
Scenario: Update a group entry in the database8 ms0099
Scenario: Update a group entry with a false ID7 ms001010
Scenario: Update a job XML definition5 ms001010
Scenario: Update a job description6 ms001010
Scenario: Update a job name6 ms001010
Scenario: Update a non existing device6 ms0055
Scenario: Update a nonexistent job4 ms001010
Scenario: Update a nonexistent step definition10 ms0077
Scenario: Update a step definition name9 ms0077
Scenario: Update a step definition processor name9 ms0088
Scenario: Update a step definition target type22 ms0088
Scenario: Update existing role name9 ms0088
Scenario: Update job id of an existing execution item6 ms0088
Scenario: Update schedule which doesn't exist12 ms0055
Scenario: Update scheduler end date3 ms2169
Scenario: Update scheduler name14 ms0088
Scenario: Update scheduler start date13 ms0088
Scenario: Update the end time of an existing execution item4 ms0099
Scenario: Update trigger definition3 ms2158
Scenario: Update user11 ms0077
Scenario: Update user that doesn't exist7 ms0055
Scenario: User locking itself out by using out login attempts4 ms001616
Scenario: User locking itself out with failed attempts and not waiting to unlock4 ms001717
Scenario: User locking itself out with failed attempts and waiting to unlock7 ms001717
Scenario: User login with wrong pass, but with enough time between login failures6 ms001919
Scenario: User not locking itself out by using less than max failed login attempts6 ms001717
Scenario: Validate a device client based search with a null client ID5 ms0055
Scenario: Validate a device client based search with an empty client ID5 ms0055
Scenario: Validate a device client search with null scope6 ms0055
Scenario: Validate a device creator with a null client ID6 ms0066
Scenario: Validate a device creator with a null scope ID5 ms0066
Scenario: Validate a device query with a null Scope ID5 ms0044
Scenario: Validate a device search with a null device ID5 ms0066
Scenario: Validate a device search with a null scope ID5 ms0066
Scenario: Validate a null creator5 ms0055
Scenario: Validate a null device5 ms0055
Scenario: Validate a null device count5 ms0055
Scenario: Validate a null device query5 ms0055
Scenario: Validate a regular creator6 ms0044
Scenario: Validate a regular device client search5 ms0044
Scenario: Validate a regular device count5 ms0044
Scenario: Validate a regular device query6 ms0044
Scenario: Validate a regular device search6 ms0055
Scenario: Validate deleting a device with a null device ID6 ms0066
Scenario: Validate deleting a device with a null scope ID6 ms0066
Scenario: Waiting For Lock Duration Time To Pass9 ms001919
Scenario: Waiting For Reset After Login Counter To Pass8 ms001818
empty) scope0 ms0044