Test Result : (root)

53 failures (-11) , 404 skipped (-474)
16,563 tests (-1)
Took 25 sec.

All Failed Tests

Test NameDurationAge
 Scenario: Add datastore permissions to the role.And I search for data message with id "fake-id"2 ms5
 Scenario: Add datastore permissions to the role.Scenario: Add datastore permissions to the role3 ms5
 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 ms7
 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 ms7
 Scenario: Create index with specific prefix.Scenario: Create index with specific prefix0 ms1
 Scenario: Create index with specific prefix.When REST GET call at "/_cat/indices/"0 ms1
 Scenario: Create same user in different accounts.Scenario: Create same user in different accounts1.3 sec5
 Scenario: Create scheduler with correct end date.Scenario: Create scheduler with correct end date3 ms3
 Scenario: Create scheduler with correct end date.Then I create a new trigger from the existing creator with previously defined date properties2 ms3
 Scenario: Create scheduler with end date before start date.Scenario: Create scheduler with end date before start date11 ms3
 Scenario: Create scheduler with end date before start date.Then I create a new trigger from the existing creator with previously defined date properties11 ms3
 Scenario: Creating unique Access Group with special symbols in description.Scenario: Creating unique Access Group with special symbols in description9 ms25
 Scenario: Creating unique Access Group with special symbols in description.Then I find the group with name "groupName53"8 ms25
 Scenario: Delete items by date ranges.Scenario: Delete items by date ranges2 ms3
 Scenario: Delete items by date ranges.Then I store the messages from list "TestMessages" and remember the IDs as "StoredMessageIDs"2 ms730
 Scenario: Deleting user in account that is higher in hierarchy.Scenario: Deleting user in account that is higher in hierarchy1.3 sec5
 Scenario: Deleting user in account that is lower in hierarchy.Scenario: Deleting user in account that is lower in hierarchy1.3 sec5
 Scenario: Execute possible docker steps to show its usage.Given List images by name "kapua/kapua-broker:1.5.0-SNAPSHOT"1 ms12
 Scenario: Execute possible docker steps to show its usage.Scenario: Execute possible docker steps to show its usage2 ms12
 Scenario: Executing Job And Then Restarting Device.Scenario: Executing Job And Then Restarting Device2 ms1
 Scenario: Executing Job And Then Restarting Device.When I search for events from device "rpione3" in account "kapua-sys"1 ms1
 Scenario: Executing Job When Device Connected After End Date And Time.Scenario: Executing Job When Device Connected After End Date And Time3 ms1
 Scenario: Executing Job When Device Connected After End Date And Time.When I search for events from device "rpione3" in account "kapua-sys"2 ms1
 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 ms1
 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 ms1
 Scenario: Executing Job When Device Connected Before End Date And Time.Scenario: Executing Job When Device Connected Before End Date And Time3 ms1
 Scenario: Executing Job When Device Connected Before End Date And Time.When I search for events from device "rpione3" in account "kapua-sys"2 ms1
 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 Time2 ms1
 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"1 ms1
 Scenario: Executing Job Without Steps.Scenario: Executing Job Without Steps2 ms1
 Scenario: Executing Job Without Steps.When I search for events from device "rpione3" in account "kapua-sys"1 ms1
 Scenario: Init Security Context for all scenarios.Scenario: Init Security Context for all scenarios1.3 sec5
 Scenario: List Endpoints Created From Sub-Account.And I create endpoint with schema "Schema1", domain "abc.com" and port 22222 ms5
 Scenario: List Endpoints Created From Sub-Account.Scenario: List Endpoints Created From Sub-Account3 ms5
 Scenario: List Endpoints From "kapua-sys" Account.Scenario: List Endpoints From "kapua-sys" Account2 ms5
 Scenario: List Endpoints From "kapua-sys" Account.Then I find 3 endpoints1 ms5
 Scenario: List Endpoints From Sub-Account Of Another Sub-Account.And I create endpoint with schema "Schema1", domain "abc.com" and port 22222 ms5
 Scenario: List Endpoints From Sub-Account Of Another Sub-Account.Scenario: List Endpoints From Sub-Account Of Another Sub-Account3 ms5
 Scenario: List Endpoints From Sub-account.And I create endpoint with schema "Schema1", domain "abc.com" and port 22222 ms5
 Scenario: List Endpoints From Sub-account.Scenario: List Endpoints From Sub-account3 ms5
 Scenario: Reset Security Context for all scenarios.Scenario: Reset Security Context for all scenarios1.4 sec5
 Scenario: Simple Jetty with rest-api war.Scenario: Simple Jetty with rest-api war3 ms7
 Scenario: Simple Jetty with rest-api war.When REST POST call at "/v1/authentication/user" with JSON "{"password": "kapua-password", "username": "kapua-sys"}"2 ms7
 Scenario: Start Jetty server for all scenarios.Given Start Jetty Server on host "127.0.0.1" at port "8081"2 ms7
 Scenario: Start Jetty server for all scenarios.Scenario: Start Jetty server for all scenarios3 ms7
 Scenario: Start datastore for all scenarios.Given Start Datastore2 ms5
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios2 ms5
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios1.3 sec5
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios1.4 sec5
 Scenario: Update scheduler end date.And I try to edit end date to 13-12-2020 at 10:001 ms3
 Scenario: Update scheduler end date.Scenario: Update scheduler end date2 ms3
 Scenario: Update trigger definition.And I try to edit trigger definition to "Cron Job"2 ms3
 Scenario: Update trigger definition.Scenario: Update trigger definition3 ms3

All Tests

ClassDurationFail(diff)Skip(diff)Pass(diff)Total(diff)
Scenario: A fresh database must contain 1 default role in the root scope6 ms0044
Scenario: A newly created account must have some metadata4 ms0033
Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic4 ms0088
Scenario: Access info service sanity checks8 ms0044
Scenario: Access service comparison sanity checks7 ms0033
Scenario: Account based ClientInfo data check12 ms002424
Scenario: Account exactly on its expiration date8 ms001414
Scenario: Account name must not be mutable4 ms0066
Scenario: Account past its expiration date8 ms001414
Scenario: Account wide metrics check17 ms002828
Scenario: Account with future expiration date8 ms001313
Scenario: Account with no expiration date6 ms001313
Scenario: Add Access Info domain permissions to new user15 ms002626
Scenario: Add Account permissions to the role in child account21 ms002828
Scenario: Add Credential domain permissions to new user13 ms001818
Scenario: Add Datastore domain permissions to new user0.13 sec001919
Scenario: Add Device Connection domain permissions to kapua-sys user12 ms001111
Scenario: Add Device Connection domain permissions to new user12 ms002323
Scenario: Add Device Event domain permissions to new user13 ms001616
Scenario: Add Device domain permissions to new user12 ms001717
Scenario: Add Domain domain permissions to kapua-sys user11 ms001717
Scenario: Add Domain domain permissions to new user15 ms003232
Scenario: Add Endpoint Permission To The User16 ms003030
Scenario: Add Endpoint_info permissions to the role in child account17 ms003030
Scenario: Add Group domain permissions to new user15 ms001717
Scenario: Add Group permissions to the role in child account17 ms002626
Scenario: Add Job domain permissions to new user12 ms001919
Scenario: Add Role domain permissions to new user11 ms001717
Scenario: Add Role permissions to the role in child account20 ms002626
Scenario: Add Scheduler Permissions With Job Permissions12 ms003131
Scenario: Add Scheduler Permissions Without Job Permissions12 ms002121
Scenario: Add Scheduler permissions to the role in child account18 ms003636
Scenario: Add Tag domain permissions to new user12 ms001515
Scenario: Add Tag permissions to the role in child account18 ms002626
Scenario: Add User domain permissions to new user14 ms002020
Scenario: Add account permissions to the role20 ms001919
Scenario: Add admin role to the user21 ms004444
Scenario: Add and delete Account permissions from the "admin" role17 ms001414
Scenario: Add and delete Device permissions from the "admin" role19 ms001414
Scenario: Add and delete Endpoint_info permissions from the "admin" role19 ms001414
Scenario: Add and delete Group permissions from the "admin" role18 ms001414
Scenario: Add and delete Job permissions from the "admin" role19 ms001414
Scenario: Add and delete Role permissions from the "admin" role19 ms001414
Scenario: Add and delete User permissions from the "admin" role17 ms001515
Scenario: Add datastore permissions to the role5 ms232227
Scenario: Add deleted role again17 ms001010
Scenario: Add device event permissions to the role22 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 role16 ms002323
Scenario: Add endpoint_info permissions to the role23 ms003131
Scenario: Add group permissions to the role18 ms001818
Scenario: Add job permissions to the role20 ms001919
Scenario: Add job permissions to the role in child account16 ms002626
Scenario: Add role permissions to the role20 ms001919
Scenario: Add same permission twice to the same role17 ms001414
Scenario: Add same role to user twice17 ms001313
Scenario: Add scheduler permissions to the role16 ms003131
Scenario: Add tag permissions to the role18 ms001818
Scenario: Add user permissions to the role18 ms001919
Scenario: Add user permissions to the role in child account21 ms002626
Scenario: Adding "Cron Job" Schedule With All Valid Parameters6 ms001010
Scenario: Adding "Cron Job" Schedule With All Valid Parameters And Null Cron Value6 ms001010
Scenario: Adding "Cron Job" Schedule With All Valid Parameters Except Cron Format7 ms001111
Scenario: Adding "Cron Job" Schedule With End Date Only9 ms001010
Scenario: Adding "Cron Job" Schedule With End Time before Start time9 ms001212
Scenario: Adding "Cron Job" Schedule With Non-Unique End Date Parameter7 ms001616
Scenario: Adding "Cron Job" Schedule With Non-Unique Start Date Parameter8 ms001515
Scenario: Adding "Cron Job" Schedule With Start Date Only6 ms001111
Scenario: Adding "Cron Job" Schedule With the same Start and End time9 ms001212
Scenario: Adding "Cron Job" Schedule Without The Start Date Parameter7 ms001010
Scenario: Adding "Device Connect" Schedule With All Valid Parameters8 ms0088
Scenario: Adding "Device Connect" Schedule With End Date Only6 ms001010
Scenario: Adding "Device Connect" Schedule With End Time before Start time7 ms001111
Scenario: Adding "Device Connect" Schedule With Max Length Name6 ms0088
Scenario: Adding "Device Connect" Schedule With Min Length Name6 ms0088
Scenario: Adding "Device Connect" Schedule With Name Only6 ms0099
Scenario: Adding "Device Connect" Schedule With Non-Unique End Date Parameter7 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 Only7 ms001010
Scenario: Adding "Device Connect" Schedule With the same Start and End time7 ms001111
Scenario: Adding "Device Connect" Schedule Without Name5 ms001010
Scenario: Adding "Device Connect" Schedule Without The Start Date Parameter8 ms0099
Scenario: Adding "Empty" Tag To Device4 ms0055
Scenario: Adding "Interval Job" Schedule With All Valid Parameters6 ms001010
Scenario: Adding "Interval Job" Schedule With End Date Only8 ms001010
Scenario: Adding "Interval Job" Schedule With End Time before Start time6 ms001212
Scenario: Adding "Interval Job" Schedule With Max Length Name7 ms001010
Scenario: Adding "Interval Job" Schedule With Min Length Name7 ms001010
Scenario: Adding "Interval Job" Schedule With Name Only8 ms001010
Scenario: Adding "Interval Job" Schedule With Non-Unique End Date Parameter8 ms001616
Scenario: Adding "Interval Job" Schedule With Non-Unique Name6 ms001515
Scenario: Adding "Interval Job" Schedule With Non-Unique Start Date Parameter7 ms001515
Scenario: Adding "Interval Job" Schedule With Null Interval Number6 ms001212
Scenario: Adding "Interval Job" Schedule With Start Date Only6 ms001111
Scenario: Adding "Interval Job" Schedule With the same Start and End time7 ms001212
Scenario: Adding "Interval Job" Schedule Without Interval Number6 ms001111
Scenario: Adding "Interval Job" Schedule Without The Start Date Parameter6 ms0099
Scenario: Adding "Interval Job" Schedule Without a Name8 ms001111
Scenario: Adding "admin" role to a user in a child account23 ms001414
Scenario: Adding "admin" role to multiple users17 ms001818
Scenario: Adding "admin" role twice18 ms001313
Scenario: Adding Account:Delete permission to user in same scope11 ms002525
Scenario: Adding Account:Delete permission to user in sub-account scope12 ms003030
Scenario: Adding Account:Read and Account:Delete permissions to user in same scope11 ms002121
Scenario: Adding Account:Read and Account:Write permissions to user in same scope13 ms001919
Scenario: Adding Account:Read permission to user in same scope13 ms002323
Scenario: Adding Account:Read permission to user in sub-account scope13 ms002929
Scenario: Adding Account:Write and Account:Delete permission to user in same scope12 ms002323
Scenario: Adding Account:Write permission to user in same scope11 ms002525
Scenario: Adding Account:Write permission to user in sub-account scope13 ms003131
Scenario: Adding Multiple Permissions To User15 ms002020
Scenario: Adding One Permission To User18 ms001111
Scenario: Adding Permissions To Child User12 ms001818
Scenario: Adding Permissions To Parallel User12 ms001818
Scenario: Adding Previously Deleted Permission11 ms002828
Scenario: Adding Previously Deleted Tag From Device Again4 ms001111
Scenario: Adding Regular Device to a Group With Description6 ms001010
Scenario: Adding Regular Device to a Group Without a Description7 ms001212
Scenario: Adding Regular Group Without Description to Device10 ms001010
Scenario: Adding Regular Tag Without Description To Device5 ms0066
Scenario: Adding Same Regular Group Without Description to Device8 ms001414
Scenario: Adding Tag With Long Name Without Description To Device4 ms0066
Scenario: Adding Tag With Numbers Without Description To Device4 ms0066
Scenario: Adding Tag With Short Name Without Description To Device4 ms0066
Scenario: Adding Tag With Special Symbols Without Description To Device4 ms0066
Scenario: Adding all Account permissions to user in same scope12 ms001717
Scenario: Adding all Account permissions to user in sub-account scope11 ms002424
Scenario: Adding existing roles to user27 ms001515
Scenario: Adding role from child account to user in new child account18 ms001515
Scenario: Adding role to multiple users in child account18 ms001818
Scenario: Adding same role twice to user in child account18 ms001515
Scenario: Adding the same role to user twice in child account22 ms001313
Scenario: All device parameters must match the device creator5 ms0033
Scenario: Assign 100 Devices to One Group15 ms001111
Scenario: B1 Broker publish to CTRL_ACC_REPLY5 ms0099
Scenario: B10 Broker create sub-topic on ACL_DATA_ACC is not allowed4 ms0099
Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed4 ms0088
Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI6 ms0099
Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed4 ms0099
Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed4 ms0088
Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY6 ms0099
Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY3 ms0099
Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account5 ms0099
Scenario: B5 Broker publish to CTRL_ACC is not allowed4 ms0099
Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed6 ms0099
Scenario: B7 Broker subscribe on CTRL_ACC is not allowed4 ms0088
Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI4 ms0099
Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed5 ms0099
Scenario: Basic Device Event queries6 ms001010
Scenario: Birth and applications event handling8 ms001212
Scenario: Birth and death message handling6 ms001212
Scenario: Birth and missing event handling7 ms001212
Scenario: Birth message handling from a new device5 ms001313
Scenario: Birth message handling from an existing device6 ms001212
Scenario: Both the parent and child accounts do not expire7 ms001111
Scenario: Both the parent and child accounts have the same expiration date7 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 check12 ms003030
Scenario: Case sensitiveness of named device searches5 ms0044
Scenario: Change an existing step name3 ms001111
Scenario: Change role name so it is too short5 ms0066
Scenario: Change the account parent path7 ms0055
Scenario: Changing Client ID6 ms0099
Scenario: Changing Description On Group With Long Description8 ms0077
Scenario: Changing Description On Group With Long Name6 ms0077
Scenario: Changing Description On Group With Numbers In Name7 ms001010
Scenario: Changing Description On Group With Permitted Symbols6 ms0077
Scenario: Changing Description On Group With Short Description8 ms0077
Scenario: Changing Description On Group With Short Name7 ms0077
Scenario: Changing Description On Tag With Long Description6 ms0044
Scenario: Changing Description On Tag With Long Name4 ms0055
Scenario: Changing Description On Tag With Numbers In Name4 ms0066
Scenario: Changing Description On Tag With Permitted Symbols In Name4 ms0044
Scenario: Changing Description On Tag With Short Description4 ms0044
Scenario: Changing Description On Tag With Short Name4 ms0044
Scenario: Changing Device Status To Disabled6 ms0099
Scenario: Changing Device Status To Enabled7 ms0099
Scenario: Changing Group's Description To Non-Uniqe One6 ms0077
Scenario: Changing Group's Description To Uniqe One7 ms0077
Scenario: Changing Group's Name To Contain Invalid Symbols In Name Without Changing Description8 ms0088
Scenario: Changing Group's Name To Contain Permitted Symbols In Name Without Changing Description7 ms0077
Scenario: Changing Group's Name To Non-Unique One7 ms0099
Scenario: Changing Group's Name To Short One Without Changing Description9 ms0077
Scenario: Changing Group's Name To Unique One7 ms0077
Scenario: Changing Group's Name To a Long One Without Changing Description8 ms0077
Scenario: Changing Group's Name To a Too Long One Without Changing Description7 ms0088
Scenario: Changing Group's Name To a Too Short One Without Changing Description8 ms0088
Scenario: Changing Tag's Description To Non-Unique One7 ms0055
Scenario: Changing Tag's Description To Unique One4 ms0077
Scenario: Changing Tag's Name To Contain Invalid Symbols In Name Without Description5 ms0055
Scenario: Changing Tag's Name To Contain Permitted Symbols In Name Without Description5 ms0055
Scenario: Changing Tag's Name To Non-Unique One5 ms0066
Scenario: Changing Tag's Name To Short One Without Description5 ms0077
Scenario: Changing Tag's Name To Unique One6 ms0077
Scenario: Changing Tag's Name To a Long One Without Description5 ms0077
Scenario: Changing Tag's Name To a Too Long One Without Description4 ms0055
Scenario: Changing Tag's Name To a Too Short One Without Description6 ms0055
Scenario: Changing description of a nonexisting role3 ms0077
Scenario: Changing job description to non-unique one8 ms0077
Scenario: Changing job description to the long one8 ms0066
Scenario: Changing job description to unique one9 ms0066
Scenario: Changing job description to very short one7 ms0077
Scenario: Changing job name to a long one without description7 ms0077
Scenario: Changing job name to a too long one without description3 ms0055
Scenario: Changing job name to a too short one without description8 ms0066
Scenario: Changing job name to contain invalid symbols in name without description8 ms0044
Scenario: Changing job name to contain permitted symbols in name without description7 ms0055
Scenario: Changing job name to non-unique one9 ms0088
Scenario: Changing job name to short one without description8 ms0077
Scenario: Changing job name to unique one8 ms0099
Scenario: Changing name of a nonexisting role3 ms0077
Scenario: Changing role description to a valid one2 ms0066
Scenario: Changing role name so it is too long3 ms0066
Scenario: Changing role name to contain special character3 ms0044
Scenario: Changing role name to null3 ms0066
Scenario: Changing role's name to a valid one3 ms0066
Scenario: Channel info queries based on datastore channel filters12 ms005050
Scenario: ChannelInfo client ID and topic data based on the client id12 ms002828
Scenario: ChannelInfo client ID based on the account id12 ms002626
Scenario: ChannelInfo last published date15 ms003030
Scenario: ChannelInfo topic data based on the account id11 ms002626
Scenario: Check account properties6 ms0044
Scenario: Check the Device Connection Domain data seetting5 ms0022
Scenario: Check the database cache coherency11 ms003030
Scenario: Check the mapping for message semantic topics13 ms003030
Scenario: Check the message store12 ms002020
Scenario: Check the sanity of the Device Connection Domain data initialization4 ms0022
Scenario: Child account expires after parent7 ms0099
Scenario: Child account expires before parent8 ms001111
Scenario: Child account has null expiration date6 ms0099
Scenario: Client Id based ClientInfo data check12 ms002828
Scenario: Compare domain entries7 ms0033
Scenario: Connect to the system and publish some data0.13 sec002222
Scenario: Connection Service factory sanity checks3 ms0022
Scenario: Count access info entities in a specific scope40 ms002424
Scenario: Count access role entities by scope10 ms003939
Scenario: Count connections in empty scope4 ms0044
Scenario: Count connections in scope6 ms0055
Scenario: Count devices with a specific BIOS version5 ms0066
Scenario: Count domains in a blank database9 ms0044
Scenario: Count domains in the database9 ms0077
Scenario: Count events in empty scope6 ms0066
Scenario: Count groups7 ms001414
Scenario: Count groups in a blank database8 ms0055
Scenario: Count job items4 ms0077
Scenario: Count job items in wrong - empty - scope4 ms0088
Scenario: Count role permissions in specific scopes7 ms001818
Scenario: Count roles in specific scopes6 ms001515
Scenario: Count step definition items6 ms0044
Scenario: Count step definitions in wrong (empty) scope6 ms0011
Scenario: Count steps in the database4 ms001414
Scenario: Count user5 ms0066
Scenario: Counting created roles items in the DB3 ms0055
Scenario: Create a regular event21 ms0088
Scenario: Create a single device with an empty string for clientID6 ms0044
Scenario: Create a single device with null clientID value5 ms0044
Scenario: Create a valid job entry30 ms0066
Scenario: Create an event with a null scope ID13 ms0077
Scenario: Create and count several execution items for a job5 ms001111
Scenario: Create index with specific prefix0 ms2+22+28-412
Scenario: Create multiple users5 ms0055
Scenario: Create regular access permissions10 ms002020
Scenario: Create same user in different accounts1.3 sec114015
Scenario: Create scheduler with correct end date5 ms2158
Scenario: Create scheduler with empty schedule name15 ms0088
Scenario: Create scheduler with end date before start date23 ms2169
Scenario: Create scheduler with invalid Retry Interval property25 ms0099
Scenario: Create scheduler with invalid cron job trigger property11 ms0099
Scenario: Create scheduler with invalid schedule name18 ms0088
Scenario: Create scheduler with short schedule name13 ms0088
Scenario: Create scheduler with too long schedule name12 ms0088
Scenario: Create scheduler with valid Retry Interval property33 ms0077
Scenario: Create scheduler with valid cron job trigger property27 ms0077
Scenario: Create scheduler with valid schedule name35 ms0066
Scenario: Create scheduler without Cron Job Trigger property10 ms0099
Scenario: Create scheduler without Retry Interval property9 ms0099
Scenario: Create scheduler without start date12 ms0077
Scenario: Create some regular role permissions7 ms0099
Scenario: Create user that already exist5 ms0077
Scenario: Create user that has more than DB allowed length10 ms0055
Scenario: Create user with short name9 ms0055
Scenario: Create user with special characters in his name12 ms0055
Scenario: Create with permissions16 ms001414
Scenario: Create with permissions and a role44 ms001717
Scenario: Create with permissions and a role in the wrong scope7 ms001515
Scenario: Creating 100 Sub-accounts While InfiniteChildAccounts Is Set To True8 ms0077
Scenario: Creating A Device With Disabled Status6 ms0077
Scenario: Creating A Device With Enabled Status6 ms0077
Scenario: Creating A Device With Long Display Name5 ms0077
Scenario: Creating A Device With Long Name6 ms0077
Scenario: Creating A Device With Name Containing Invalid Symbols9 ms0088
Scenario: Creating A Device With Name Containing Permitted Symbols5 ms0077
Scenario: Creating A Device With No Name5 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 Name4 ms0077
Scenario: Creating A Device With Short Name5 ms0077
Scenario: Creating A Device With Too Long Display Name4 ms0088
Scenario: Creating A Device With Too Long Name6 ms0088
Scenario: Creating A Device With Unique Name7 ms0099
Scenario: Creating A Valid Account7 ms0055
Scenario: Creating An Account With Long Name9 ms0055
Scenario: Creating An Account With Long Organization Name8 ms0055
Scenario: Creating An Account With Non-unique Name8 ms0088
Scenario: Creating An Account With Numbers And Valid Symbols In Name6 ms0055
Scenario: Creating An Account With Short Name7 ms0055
Scenario: Creating An Account With Short Organization Name7 ms0055
Scenario: Creating An Account With Special Symbols In Organization Name7 ms0055
Scenario: Creating An Account With Too Long Organization Name11 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 Email6 ms0066
Scenario: Creating An Account Without Name6 ms0066
Scenario: Creating An Account Without Ogranization Name8 ms0066
Scenario: Creating And Account Without "@" In Email7 ms0066
Scenario: Creating Devices And Than Setting Device Service So It Does Not Allow Devices8 ms001212
Scenario: Creating Devices And Then Changing Device Service Values7 ms001010
Scenario: Creating Devices Under Account That Allows Infinite Child Devices7 ms001010
Scenario: Creating Devices Under Account That Does Not Allow Devices8 ms0099
Scenario: Creating Devices Under Account That Has Limited Child Devices7 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" Only4 ms0066
Scenario: Creating Endpoint With "Port" Only4 ms0066
Scenario: Creating Endpoint With "Schema" Only8 ms0066
Scenario: Creating Endpoint With Disabled Secure Field6 ms0066
Scenario: Creating Endpoint With Enabled Secure Field6 ms0066
Scenario: Creating Endpoint With Invalid "Domain Name"4 ms0066
Scenario: Creating Endpoint With Invalid "Schema" containing symbols3 ms0066
Scenario: Creating Endpoint With Long "Domain Name"4 ms0055
Scenario: Creating Endpoint With Max Length "Port"6 ms0055
Scenario: Creating Endpoint With NULL parameters5 ms0066
Scenario: Creating Endpoint With Schema Containing "http://"4 ms0066
Scenario: Creating Endpoint With Schema Containing "https://"5 ms0066
Scenario: Creating Endpoint With Short "Domain Name"6 ms0066
Scenario: Creating Endpoint With Short "Schema"5 ms0066
Scenario: Creating Endpoint With Small Number "Port"4 ms0066
Scenario: Creating Endpoint With Too Big "Port"4 ms0066
Scenario: Creating Endpoint With Too Long "Domain Name"6 ms0066
Scenario: Creating Endpoint With Too Long "Schema"4 ms0066
Scenario: Creating Endpoint Without "Domain Name"4 ms0066
Scenario: Creating Endpoint Without "Port"4 ms0066
Scenario: Creating Endpoint Without "Schema"5 ms0066
Scenario: Creating Endpoint Without Long "Schema"4 ms0055
Scenario: Creating Endpoint with invalid "Schema" which contains only numbers5 ms0066
Scenario: Creating Group Invalid Symbols In Name Without Description4 ms0077
Scenario: Creating Group With Invalid Symbols In Name With Valid Description6 ms0077
Scenario: Creating Group With Long Name With Valid Description7 ms0066
Scenario: Creating Group With Long Name Without Description8 ms0066
Scenario: Creating Group With Numbers In Name With Valid Description6 ms0088
Scenario: Creating Group With Permitted Symbols And Numbers In Name Without Description9 ms0066
Scenario: Creating Group With Permitted Symbols In Name With Valid Description10 ms0066
Scenario: Creating Group With Short Name With Valid Description8 ms0066
Scenario: Creating Group With Short Name Without Description9 ms0066
Scenario: Creating Group With Too Long Name With Valid Description7 ms0077
Scenario: Creating Group With Too Long Name Without Description9 ms0077
Scenario: Creating Group With Too Short Name With Valid Description6 ms0077
Scenario: Creating Group With Too Short Name Without Description6 ms0077
Scenario: Creating Group Without a Name And With Valid Description7 ms0077
Scenario: Creating Group Without a Name And Without Description8 ms0077
Scenario: Creating Groups And Than Setting Group Service So It Does Not Allow Groups7 ms001111
Scenario: Creating Groups And Then Changing InfiniteChildGroups To False And Set MaxNumberChildGroups7 ms001010
Scenario: Creating Groups Under Account That Allows Infinite Child Groups6 ms0099
Scenario: Creating Groups Under Account That Does Not Allow Groups7 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 Values8 ms001010
Scenario: Creating Jobs Under Account That Allows Infinite Child Devices7 ms001010
Scenario: Creating Jobs Under Account That Does Not Allow Jobs7 ms0099
Scenario: Creating Jobs Under Account That Has Limited Child Jobs7 ms001313
Scenario: Creating Non-Unique Group With Valid Description6 ms0088
Scenario: Creating Non-Unique Tag With Valid Description6 ms0055
Scenario: Creating Non-unique Group Without Description8 ms0088
Scenario: Creating Non-unique Tag Without Description16 ms0044
Scenario: Creating Roles And Than Setting Role Service So It Does Not Allow Roles6 ms001111
Scenario: Creating Roles And Then Changing Role Service Values7 ms001010
Scenario: Creating Roles Under Account That Allows Infinite Child Roles6 ms001010
Scenario: Creating Roles Under Account That Does Not Allow Roles8 ms0099
Scenario: Creating Roles Under Account That Has Limited Child Roles7 ms001212
Scenario: Creating Sub-accounts When InfiniteChildAccoounts Is Set To False And maxNumberChildAccounts Is Set6 ms001313
Scenario: Creating Sub-accounts When InfiniteChildAccoounts Is Set To True And maxNumberChildAccounts Is Set6 ms001414
Scenario: Creating Sub-accounts When InfiniteChildAccounts Is Set To False7 ms0099
Scenario: Creating Sub-accounts when InfiniteChildAccounts Is Set To True7 ms001212
Scenario: Creating Tag With Invalid Symbols In Name With Valid Description6 ms0044
Scenario: Creating Tag With Invalid Symbols In Name Without Description1 ms0044
Scenario: Creating Tag With Long Name With Valid Description7 ms0044
Scenario: Creating Tag With Long Name Without Description7 ms0044
Scenario: Creating Tag With Numbers In Name With Valid Description5 ms0044
Scenario: Creating Tag With Numbers In Name Without Description6 ms0044
Scenario: Creating Tag With Permitted Symbols In Name With Valid Description5 ms0044
Scenario: Creating Tag With Permitted Symbols In Name Without Description6 ms0044
Scenario: Creating Tag With Short Name With Valid Description14 ms0044
Scenario: Creating Tag With Short Name Without Description9 ms0044
Scenario: Creating Tag With Too Long Name With Valid Description5 ms0044
Scenario: Creating Tag With Too Long Name Without Description7 ms0044
Scenario: Creating Tag With Too Short Name With Valid Description3 ms0044
Scenario: Creating Tag With Too Short Name Without Description7 ms0044
Scenario: Creating Tag Without a Name And With Valid Description5 ms0044
Scenario: Creating Tag Without a Name And Without Description7 ms0044
Scenario: Creating Tags And Than Setting Tag Service So It Does Not Allow Tags9 ms001111
Scenario: Creating Tags And Then Changing Tag Service Values9 ms001010
Scenario: Creating Tags Under Account That Allows Infinite Child Devices7 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 Description8 ms0066
Scenario: Creating Unique Group With Non-unique Description7 ms0077
Scenario: Creating Unique Group With Short Description7 ms0066
Scenario: Creating Unique Group With Unique Description8 ms0066
Scenario: Creating Unique Group Without Description8 ms0066
Scenario: Creating Unique Tag With Long Description5 ms0044
Scenario: Creating Unique Tag With Non-unique Description7 ms0055
Scenario: Creating Unique Tag With Short Description5 ms0044
Scenario: Creating Unique Tag With Unique Description6 ms0044
Scenario: Creating Unique Tag Without Description30 ms0044
Scenario: Creating Users And Than Setting User Service So It Does Not Allow Users7 ms001111
Scenario: Creating Users And Then Changing User Service Values7 ms001010
Scenario: Creating Users Under Account That Allows Infinite Child Users6 ms001010
Scenario: Creating Users Under Account That Does Not Allow Users9 ms0099
Scenario: Creating Users Under Account That Has Limited Child Users7 ms001212
Scenario: Creating Valid Endpoint5 ms0066
Scenario: Creating a Access Group with invalid special symbols in name4 ms0044
Scenario: Creating a Device With Permitted Symbols in its Display Name5 ms0077
Scenario: Creating a Device With Unique Display Name5 ms0088
Scenario: Creating a job with name only15 ms0066
Scenario: Creating a job with null name16 ms0055
Scenario: Creating a job without name with valid description8 ms0055
Scenario: Creating a new PASSWORD Credential meeting a custom length requirement7 ms0044
Scenario: Creating a new PASSWORD Credential meeting the standard length requirement26 ms0033
Scenario: Creating a new PASSWORD Credential not meeting a custom length requirement7 ms0055
Scenario: Creating a new PASSWORD Credential not meeting the standard length requirement10 ms0044
Scenario: Creating a role name with allowed symbols in its name3 ms0055
Scenario: Creating a role with 255 characters long description3 ms0055
Scenario: Creating a role with a name and description that contain digits only3 ms0055
Scenario: Creating a role with forbidden symbols in its name0 ms0044
Scenario: Creating a role with name only4 ms0055
Scenario: Creating a role with null name2 ms0055
Scenario: Creating a role with regular name and very short description" as description cannot be too short, as even one character is enough4 ms0055
Scenario: Creating a role with special characters in the description32 ms0044
Scenario: Creating a role with the name that contains digits3 ms0055
Scenario: Creating a role with too long name3 ms0055
Scenario: Creating a role with too short name3 ms0055
Scenario: Creating a role with valid name and with too long description5 ms0033
Scenario: Creating a role wtih 255 characters long name16 ms0055
Scenario: Creating a single device with case sensitive clientID6 ms0055
Scenario: Creating a single device with clientID that contains 255 characters5 ms0055
Scenario: Creating a single device with clientID that contains 256 characters4 ms0044
Scenario: Creating a single device with clientID that contains invalid character5 ms0044
Scenario: Creating a single device with clientID that contains invalid characters2 ms0044
Scenario: Creating a single device with spaces in clientID6 ms0055
Scenario: Creating a single device with valid clientID9 ms0055
Scenario: Creating a valid Access Group with numbers in name6 ms0055
Scenario: Creating a valid Access Group with only numbers in name4 ms0055
Scenario: Creating a valid Access Group with unique name36 ms0055
Scenario: Creating a valid Access Group with valid special symbols in name4 ms0055
Scenario: Creating a valid role3 ms0055
Scenario: Creating an Access Group with empty name6 ms0044
Scenario: Creating an Access Group with long name4 ms0055
Scenario: Creating an Access Group with short name5 ms0055
Scenario: Creating an Access Group with too long name5 ms0044
Scenario: Creating an Access Group with too short name5 ms0044
Scenario: Creating an Access Group without name and with description6 ms0044
Scenario: Creating and Deleting Endpoint Two Times8 ms002525
Scenario: Creating index with regular user7 ms002525
Scenario: Creating job with invalid symbols in name without description9 ms0044
Scenario: Creating job with long name and valid description9 ms0066
Scenario: Creating job with long name without description15 ms0066
Scenario: Creating job with numbers in name and valid description18 ms0066
Scenario: Creating job with numbers in name without description17 ms0066
Scenario: Creating job with permitted symbols in name without description13 ms0033
Scenario: Creating job with short name and valid job description9 ms0066
Scenario: Creating job with short name without description12 ms0066
Scenario: Creating job with too long name and valid description7 ms0055
Scenario: Creating job with too long name without description25 ms0055
Scenario: Creating job with too short name and valid description9 ms0055
Scenario: Creating job with too short name without description13 ms0055
Scenario: Creating job without name and without description10 ms0055
Scenario: Creating new device and tagging it with specific Tag7 ms001414
Scenario: Creating new device, tagging it with specific Tag and then deleting this Tag9 ms001616
Scenario: Creating non-unique Access Group4 ms0055
Scenario: Creating non-unique Access Group with unique description5 ms0055
Scenario: Creating non-unique job name with valid job description9 ms0077
Scenario: Creating two device with the same clientID14 ms0055
Scenario: Creating two indexes with daily index7 ms001717
Scenario: Creating two indexes with hourly index6 ms001717
Scenario: Creating two indexes with weekly index6 ms001717
Scenario: Creating two roles with the same description2 ms0066
Scenario: Creating two roles with the same name3 ms0077
Scenario: Creating unique Access Group with long description5 ms0055
Scenario: Creating unique Access Group with non-unique description5 ms0066
Scenario: Creating unique Access Group with numbers in description5 ms0055
Scenario: Creating unique Access Group with only numbers in description4 ms0055
Scenario: Creating unique Access Group with short description4 ms0055
Scenario: Creating unique Access Group with special symbols in description17 ms2114
Scenario: Creating unique Access Group with unique description4 ms0055
Scenario: Creating unique job with long description8 ms0066
Scenario: Creating unique job with non-unique description9 ms001010
Scenario: Creating unique job with short description22 ms0066
Scenario: Creating user31 ms0055
Scenario: Creation of access role with neither acess info and role entities10 ms001212
Scenario: Creation of access role without an acess info entity10 ms001212
Scenario: D1 Device publish to CTRL_ACC_REPLY3 ms0099
Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI5 ms0099
Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed5 ms0099
Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed5 ms0077
Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY3 ms0099
Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY6 ms0099
Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account4 ms0099
Scenario: D5 Device subscribe - publish - admin on CTRL_ACC4 ms0099
Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI4 ms0099
Scenario: D7 Device publish to ACL_DATA_ACC is not allowed5 ms0099
Scenario: D8 Device create sub-topic on ACL_DATA_ACC is not allowed3 ms0099
Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed4 ms0088
Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed8 ms0099
Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI3 ms0099
Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed4 ms0099
Scenario: DM13 Data manage subscribe on ACL_CTRL_ACC_NOTIFY is not allowed4 ms0088
Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY4 ms0099
Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY7 ms0099
Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account4 ms0099
Scenario: DM5 Data manage publish to CTRL_ACC is not allowed5 ms0099
Scenario: DM6 Data manage create sub-topic on CTRL_ACC is not allowed5 ms0099
Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed6 ms0088
Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI4 ms0099
Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC8 ms0099
Scenario: DV1 Data view publish to CTRL_ACC_REPLY6 ms0099
Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed6 ms0099
Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed4 ms001010
Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed5 ms0099
Scenario: DV13 Data view create sub-topic on ACL_CTRL_ACC_CLI is not allowed4 ms0099
Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed5 ms0099
Scenario: DV17 Data view subscribe on ACL_CTRL_ACC_NOTIFY is not allowed4 ms0088
Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY6 ms0099
Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY6 ms0099
Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account7 ms0099
Scenario: DV5 Data view publish to CTRL_ACC is not allowed3 ms0099
Scenario: DV6 Data view create sub-topic on CTRL_ACC is not allowed6 ms0099
Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed5 ms0088
Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI5 ms0099
Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed3 ms0099
Scenario: Decreasing MaxNumberChildAccounts When Sub-accounts Are Already Created7 ms001515
Scenario: Delete Kapua system user6 ms0055
Scenario: Delete a access info entity with permissions and roles8 ms001717
Scenario: Delete a connection from the database4 ms0088
Scenario: Delete a group from the database7 ms001010
Scenario: Delete a group from the database - Unknown group ID8 ms0066
Scenario: Delete a job4 ms001111
Scenario: Delete a job execution item4 ms0088
Scenario: Delete a job execution item twice4 ms0099
Scenario: Delete a job twice6 ms001010
Scenario: Delete a non existent event7 ms0077
Scenario: Delete a non existing connection5 ms0077
Scenario: Delete a non existing permission entity8 ms001616
Scenario: Delete a non existing role entry6 ms001111
Scenario: Delete a non-existing step4 ms001212
Scenario: Delete a nonexistent domain11 ms0055
Scenario: Delete a step definition9 ms0088
Scenario: Delete a step definition twice7 ms0077
Scenario: Delete access role from user18 ms001212
Scenario: Delete an access info entity twice15 ms001111
Scenario: Delete an access info entity using the wrong scope ID11 ms001111
Scenario: Delete an existing access info entity38 ms001212
Scenario: Delete an existing access permission entity8 ms001515
Scenario: Delete an existing access role entry9 ms002222
Scenario: Delete an existing account6 ms0055
Scenario: Delete an existing device from the registry22 ms0044
Scenario: Delete an existing event7 ms0099
Scenario: Delete an existing role10 ms001010
Scenario: Delete an existing role twice10 ms001616
Scenario: Delete an existing step3 ms001111
Scenario: Delete items based on query results14 ms008484
Scenario: Delete items by date ranges0.46 sec25773132
Scenario: Delete items by the datastore ID12 ms006666
Scenario: Delete middle child expiration9 ms001515
Scenario: Delete nonexisting account6 ms0044
Scenario: Delete nonexisting role permission8 ms001313
Scenario: Delete parent expiration7 ms001414
Scenario: Delete permissions from role19 ms001818
Scenario: Delete role permissions7 ms001010
Scenario: Delete scheduler7 ms0088
Scenario: Delete scheduler which doesn't exist6 ms0055
Scenario: Delete the Kapua system account8 ms0055
Scenario: Delete the last created domain entry8 ms0088
Scenario: Delete user7 ms0066
Scenario: Delete user that doesn't exist5 ms0055
Scenario: Deleting "Cron Schedule" Triggering6 ms001313
Scenario: Deleting "Device Schedule" Triggering7 ms001111
Scenario: Deleting "Interval Schedule" Triggering6 ms001313
Scenario: Deleting Device With Disabled Status6 ms001010
Scenario: Deleting Device With Enabled Status5 ms001010
Scenario: Deleting Endpoint Domain Name And Leaving it Empty5 ms0088
Scenario: Deleting Endpoint Which Does Not Exist5 ms0066
Scenario: Deleting Existing Group7 ms0088
Scenario: Deleting Existing Group And Creating It Again With Same Name7 ms001212
Scenario: Deleting Existing Tag And Creating It Again With Same Name5 ms0077
Scenario: Deleting Group's Name And Leaving It Empty Without Changing Description6 ms0088
Scenario: Deleting Non-Existent Tag4 ms0077
Scenario: Deleting Tag From Device4 ms0088
Scenario: Deleting Tag's Name And Leaving It Empty Without Description4 ms0055
Scenario: Deleting Unexisitng Group6 ms001111
Scenario: Deleting a Permission12 ms002121
Scenario: Deleting a non-existing Access Group4 ms0066
Scenario: Deleting a role twice4 ms0077
Scenario: Deleting admin role19 ms0077
Scenario: Deleting an existing Access Group3 ms0055
Scenario: Deleting an existing Access Group and creating it again with the same name5 ms0077
Scenario: Deleting an existing role4 ms0066
Scenario: Deleting default permissions from admin role18 ms001212
Scenario: Deleting existing tag12 ms0099
Scenario: Deleting role after adding it to user19 ms001414
Scenario: Deleting role after it has been added to user in child account17 ms001616
Scenario: Deleting user in account that is higher in hierarchy1.3 sec122023
Scenario: Deleting user in account that is lower in hierarchy1.3 sec123024
Scenario: Device connection update4 ms0077
Scenario: Device factory sanity checks4 ms0022
Scenario: Device queries4 ms001010
Scenario: Device query - find by BIOS version5 ms0077
Scenario: Domain entry query9 ms0055
Scenario: Domain with null actions9 ms0055
Scenario: Domain with null name8 ms0055
Scenario: Domains with duplicate names9 ms0088
Scenario: Duplicate group name in root scope9 ms001010
Scenario: Duplicate role names10 ms0077
Scenario: Editing Access Group description to description with numbers4 ms0055
Scenario: Editing Access Group description to description with only numbers4 ms0055
Scenario: Editing Access Group description to description with special symbols4 ms0044
Scenario: Editing Access Group description to long description4 ms0055
Scenario: Editing Access Group description to non-unique one4 ms0055
Scenario: Editing Access Group description to short description3 ms0055
Scenario: Editing Access Group description to unique one4 ms0077
Scenario: Editing Access Group name to a long one4 ms0077
Scenario: Editing Access Group name to a too long one4 ms0055
Scenario: Editing Access Group name to empty name15 ms0055
Scenario: Editing Access Group name to name that contains numbers5 ms0077
Scenario: Editing Access Group name to name that contains only numbers4 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 symbols4 ms0077
Scenario: Editing Access Group name to non-unique one3 ms0066
Scenario: Editing Access Group name to short one3 ms0077
Scenario: Editing Access Group name to too short one3 ms0055
Scenario: Editing Access Group name to valid one5 ms0077
Scenario: Editing Endpoint Domain Name So It Contains Invalid Symbols4 ms0088
Scenario: Editing Endpoint Domain Name So It Contains Only Numbers5 ms0088
Scenario: Editing Endpoint Domain Name So It Has Max Value4 ms0077
Scenario: Editing Endpoint Domain Name So It Has Min Value5 ms0077
Scenario: Editing Endpoint Domain Name To Non-unique Value4 ms0099
Scenario: Editing Endpoint Domain Name To Unique Value4 ms0077
Scenario: Editing Endpoint Port To Non-unique Value5 ms0099
Scenario: Editing Endpoint Port To Unique Value6 ms0077
Scenario: Editing Endpoint Schema And Leaving It Empty3 ms0088
Scenario: Editing Endpoint Schema So It Contains "http://"6 ms0088
Scenario: Editing Endpoint Schema So It Contains "https://"4 ms0088
Scenario: Editing Endpoint Schema So It Contains Invalid Symbols4 ms0088
Scenario: Editing Endpoint Schema So It Contains Only Numbers4 ms0088
Scenario: Editing Endpoint Schema So It Has Max Length5 ms0077
Scenario: Editing Endpoint Schema So It Has Min Length4 ms0077
Scenario: Editing Endpoint Schema To Non-unique Value3 ms0088
Scenario: Editing Endpoint Schema To Unique Value4 ms0077
Scenario: Editing Endpoint Secure Field To Non-unique Value5 ms0099
Scenario: Editing Endpoint Secure Field To Unique Value5 ms0077
Scenario: Editing Endpoint To NULL Values5 ms001414
Scenario: Editing Endpoint To Non-unique Endpoint4 ms001010
Scenario: Editing Group's Name To Contain Numbers Without Changing Description8 ms0077
Scenario: Editing Tag's Name To Contain Numbers Without Description4 ms0077
Scenario: Empty query results are supported6 ms0088
Scenario: Event factory sanity checks5 ms0022
Scenario: Event service domain check6 ms0022
Scenario: Every account must have the default configuration items5 ms0033
Scenario: Execute possible docker steps to show its usage3 ms231033
Scenario: Executing Job And Then Restarting Device3 ms2+233+3310-3545
Scenario: Executing Job When Device Connected After End Date And Time5 ms2+227+2710-2939
Scenario: Executing Job When Device Connected After The Specified Start Date And Time4 ms2+226+2610-2838
Scenario: Executing Job When Device Connected Before End Date And Time6 ms2+227+2710-2939
Scenario: Executing Job When Device Connected Before The Specified Start Date And Time3 ms2+225+2510-2737
Scenario: Executing Job Without Steps3 ms2+228+2810-3040
Scenario: Extra long continuous test with multiple subscenarios with LOOSE default connection mode24 ms0-20-408419+410419
Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode24 ms00397397
Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode and no previously defined devices14 ms00305305
Scenario: Find a connection by its IDs5 ms0066
Scenario: Find a connection by its client ID3 ms0066
Scenario: Find a group entry in the database9 ms0099
Scenario: Find a non existing event7 ms0066
Scenario: Find account by Id7 ms0044
Scenario: Find account by Ids26 ms0044
Scenario: Find account by name7 ms0044
Scenario: Find account by random Id8 ms0033
Scenario: Find all child accounts9 ms0033
Scenario: Find an access info entity28 ms001111
Scenario: Find an access info entity by user ID21 ms001010
Scenario: Find an event by its ID11 ms0066
Scenario: Find an existing access role entity10 ms001313
Scenario: Find by name nonexisting account7 ms0033
Scenario: Find correct number of messages by corresponding metric0.24 sec005858
Scenario: Find device by client ID5 ms0033
Scenario: Find device by registry ID4 ms0044
Scenario: Find last created permission9 ms001212
Scenario: Find multiple users4 ms0055
Scenario: Find role by ID7 ms0077
Scenario: Find self account by id7 ms001111
Scenario: Find self account by id and scope id10 ms001111
Scenario: Find self account by name7 ms001111
Scenario: Find the last created domain entry8 ms0055
Scenario: Find user by id7 ms0055
Scenario: Find user by its email4 ms0066
Scenario: Find user by its phone number5 ms0066
Scenario: Find user by name16 ms0055
Scenario: Find user by name that doesn't exist10 ms0033
Scenario: Find user with id and scope id that doesn't exist8 ms0033
Scenario: Finding all messages by selecting all metrics0.31 sec004040
Scenario: Finding correct number of messages by corresponding two metrics0.41 sec005252
Scenario: Finding messages with incorrect metric parameters0.24 sec007272
Scenario: Finding user by expiration date in the future5 ms0055
Scenario: Finding user by expiration date in the past5 ms0066
Scenario: Finding user by expiration date in the present5 ms0066
Scenario: Generic connection query4 ms0088
Scenario: Get metadata5 ms0033
Scenario: Group with a null name7 ms0077
Scenario: Handle account creation18 ms0033
Scenario: Handle duplicate account names10 ms0055
Scenario: Handle null account name44 ms0044
Scenario: Handling of 2 birth messages6 ms001212
Scenario: Handling of a disconnect message from a non existing device5 ms001010
Scenario: Have Two Devices in The Same Group Without Description7 ms001313
Scenario: I try to find a non-existing connection4 ms0066
Scenario: If user credential expiration date is before today, user can not login6 ms001414
Scenario: If user credential expiration date is today, user can not login it is day inclusive4 ms001414
Scenario: If user credential expiration date is tomorrow, user can login4 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 login3 ms001313
Scenario: If user expiration date is today, user can not login because expiration date was reached4 ms001313
Scenario: If user expiration date is tomorrow, user can login4 ms001212
Scenario: Init Security Context for all scenarios1.9 sec114648
Scenario: Installing a package22 ms001313
Scenario: Interval Job" Schedule With Too Long Name6 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 items4 ms0055
Scenario: Job execution factory sanity checks2 ms0022
Scenario: Job factory sanity checks3 ms0033
Scenario: Job with a duplicate name5 ms0099
Scenario: Job with a null name5 ms0088
Scenario: Job with a null scope ID3 ms0099
Scenario: Job with an empty name3 ms0088
Scenario: List Endpoints Created From Sub-Account5 ms223126
Scenario: List Endpoints From "kapua-sys" Account3 ms24511
Scenario: List Endpoints From Sub-Account Of Another Sub-Account5 ms223126
Scenario: List Endpoints From Sub-account5 ms212115
Scenario: MetricsInfo client ID and topic data based on the client id14 ms003434
Scenario: MetricsInfo last published date12 ms004848
Scenario: Modify a role that was deleted6 ms0099
Scenario: Modify an existing account14 ms0044
Scenario: Modify last child expiration so that it still expires before parent7 ms001414
Scenario: Modify middle child expiration so that it still expires before parent7 ms001414
Scenario: Modify middle child expiration to outlive parent7 ms001515
Scenario: Modify nonexisting account6 ms0066
Scenario: Modify parent expiration so that it still expires after child6 ms001414
Scenario: Modify parent expiration to before child expiration8 ms001515
Scenario: Modifying Sub-account of a different parent account11 ms002525
Scenario: Moving Device From One Group With Description to Another7 ms001414
Scenario: Nameless role entry6 ms0077
Scenario: Negative scenario when client connects twice with same client id10 ms001111
Scenario: New connection with reserved ID8 ms0-20-2334+2534
Scenario: Permission factory sanity checks8 ms0033
Scenario: Positive scenario without stealing link31 ms001212
Scenario: Query based on message ordering12 ms002020
Scenario: Query based on metrics ordering14 ms002020
Scenario: Query before schema search8 ms008282
Scenario: Query for a specific group by name10 ms001616
Scenario: Query for all the access info entities of a specific user11 ms001818
Scenario: Query for all the access info entities of an invalid user9 ms001010
Scenario: Query for executions of a specific job4 ms001818
Scenario: Query for jobs with specified name5 ms0099
Scenario: Query for step definitions9 ms0077
Scenario: Query user5 ms0066
Scenario: Querying Other Items With All Account Permissions12 ms003939
Scenario: Regular connection5 ms0077
Scenario: Regular creation of Access Role entity8 ms001414
Scenario: Regular domain9 ms0055
Scenario: Regular group in random scope8 ms0077
Scenario: Regular group in root scope18 ms0077
Scenario: Regular job creation4 ms001010
Scenario: Regular job execution creation6 ms0077
Scenario: Regular role creation6 ms0099
Scenario: Regular step creation8 ms001111
Scenario: Regular step definition creation7 ms0077
Scenario: Regular step definition with a property list16 ms0044
Scenario: Reset Security Context for all scenarios1.5 sec114648
Scenario: Restarting a job with Asset Write and Bundle Start steps15 ms002828
Scenario: Restarting a job with Command Execution and Bundle Start steps15 ms002828
Scenario: Restarting a job with Configuration Put and Bundle Start steps15 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 times60 ms003333
Scenario: Restarting a job with invalid Configuration Put step two times17 ms003636
Scenario: Restarting a job with invalid Package Install step and multiple devices two times58 ms003131
Scenario: Restarting a job with invalid Package Install step two times19 ms003434
Scenario: Restarting a job with invalid Package Uninstall step and multiple devices two times20 ms003232
Scenario: Restarting a job with invalid Package Uninstall step two times24 ms003434
Scenario: Restarting a job with valid Configuration Put step and multiple devices two times17 ms003333
Scenario: Restarting a job with valid Configuration Put step two times17 ms003636
Scenario: Restarting a job with valid Package Install step and multiple devices two times0.15 sec002929
Scenario: Restarting a job with valid Package Install step two times17 ms003434
Scenario: Restarting a job with valid Package Uninstall step and multiple devices two times19 ms003030
Scenario: Restarting a job with valid Package Uninstall step two times13 ms003232
Scenario: Restarting job With invalid Asset Write and multiple two times16 ms003434
Scenario: Restarting job With valid Asset Write step two times24 ms003636
Scenario: Restarting job with Asset Write and Bundle Start steps and multiple devices14 ms003131
Scenario: Restarting job with Asset Write step16 ms002525
Scenario: Restarting job with Asset Write step and multiple devices14 ms002828
Scenario: Restarting job with Bundle Start step20 ms002525
Scenario: Restarting job with Bundle Start step and multiple devices14 ms002727
Scenario: Restarting job with Bundle Stop and Bundle Start step and multiple devices13 ms003131
Scenario: Restarting job with Bundle Stop and Bundle Start steps15 ms002929
Scenario: Restarting job with Bundle Stop step15 ms002525
Scenario: Restarting job with Bundle Stop step and multiple devices18 ms002727
Scenario: Restarting job with Command Execution and Bundle Start steps and multiple devices16 ms003131
Scenario: Restarting job with Command Execution step23 ms002525
Scenario: Restarting job with Command Execution step and multiple devices18 ms002727
Scenario: Restarting job with Configuration Put and Bundle Start steps and multiple devices13 ms003131
Scenario: Restarting job with Configuration Put step24 ms002525
Scenario: Restarting job with Configuration Put step and multiple devices14 ms002727
Scenario: Restarting job with Package Download/Install and Bundle Start steps and multiple devices38 ms005959
Scenario: Restarting job with Package Download/Install step and multiple devices18 ms002727
Scenario: Restarting job with Package Install step14 ms002525
Scenario: Restarting job with Package Uninstall and Bundle start steps and multiple device17 ms003131
Scenario: Restarting job with Package Uninstall step17 ms002525
Scenario: Restarting job with Package Uninstall step and multiple device15 ms002727
Scenario: Restarting job with invalid Asset Write step two times15 ms003636
Scenario: Restarting job with invalid Bundle Start and Bundle Stop steps and multiple devices two times45 ms004141
Scenario: Restarting job with invalid Bundle Start and Bundle Stop steps two times22 ms004343
Scenario: Restarting job with invalid Bundle Start step and multiple devices two times19 ms003535
Scenario: Restarting job with invalid Bundle Start step two times17 ms003737
Scenario: Restarting job with invalid Bundle Stop step and multiple devices two times47 ms003535
Scenario: Restarting job with invalid Bundle Stop step two times15 ms003737
Scenario: Restarting job with invalid Command Execution and Package Install step two times28 ms003636
Scenario: Restarting job with invalid Command Execution and Package Install steps and multiple devices two times31 ms003737
Scenario: Restarting job with invalid Command Execution step and multiple devices two times65 ms003131
Scenario: Restarting job with invalid Command Execution step two times29 ms003232
Scenario: Restarting job with invalid Configuration Put And Command Execution steps two times16 ms003838
Scenario: Restarting job with invalid Configuration Put and Command Execution steps and multiple devices two times27 ms003737
Scenario: Restarting job with invalid Package Uninstall and Asset Write steps and multiple devices two times20 ms003838
Scenario: Restarting job with invalid Package Uninstall and Asset Write steps two times14 ms004040
Scenario: Restarting job with two Bundle Start steps16 ms002929
Scenario: Restarting job with two Bundle Start steps and multiple devices14 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 times34 ms004343
Scenario: Restarting job with valid Bundle Start and Bundle Stop steps and multiple devices two times28 ms004141
Scenario: Restarting job with valid Bundle Start step and multiple devices two times70 ms003535
Scenario: Restarting job with valid Bundle Start step two times17 ms003737
Scenario: Restarting job with valid Bundle Stop step and multiple devices two times41 ms003535
Scenario: Restarting job with valid Bundle Stop step two times62 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 times16 ms003434
Scenario: Restarting job with valid Command Execution step and multiple devices two times85 ms003131
Scenario: Restarting job with valid Command Execution step two times33 ms003232
Scenario: Restarting job with valid Configuration Put and Command Execution steps and multiple devices two times33 ms003737
Scenario: Restarting job with valid Configuration Put and Command Execution steps two times19 ms003838
Scenario: Restarting job with valid Package Uninstall and Asset Write steps and multiple devices two times21 ms003636
Scenario: Restarting job with valid Package Uninstall and Asset Write steps two times0.18 sec003838
Scenario: Role creator sanity checks4 ms0022
Scenario: Role entry with no actions7 ms0066
Scenario: Role object equality check6 ms0022
Scenario: Role service related objects sanity checks14 ms0044
Scenario: Search By Client ID And Get Multiple Matches17 ms003737
Scenario: Search By Client ID And Get No Matches5 ms001010
Scenario: Search By Client ID And Get One Match5 ms0088
Scenario: Search By Client ID and Display Name5 ms001212
Scenario: Search By Client ID and Serial Number5 ms001212
Scenario: Search By Client ID and Status8 ms001212
Scenario: Search By Client ID, Display Name and Serial Number5 ms001212
Scenario: Search By Client ID, Display Name and Status7 ms001212
Scenario: Search By Client ID, Display Name, Serial Number and Status6 ms001212
Scenario: Search By Device Status And Get No Matches8 ms0088
Scenario: Search By Device's Display Name And Get One Match5 ms0088
Scenario: Search By Display Name and Serial Number6 ms001212
Scenario: Search By Display Name and Status20 ms001212
Scenario: Search By Full Client ID And Get One Match6 ms001010
Scenario: Search By Non-existing Client ID And Get No Matches6 ms0088
Scenario: Search By One Letter Of Display Name7 ms0088
Scenario: Search By One Letter Of Serial Number5 ms001212
Scenario: Search By Serial Number And Get Multiple Matches9 ms001414
Scenario: Search By Serial Number And Get No Matches9 ms001010
Scenario: Search By Serial Number And Get One Match6 ms001111
Scenario: Search By Serial Number and Status6 ms001212
Scenario: Search By Serial Number, Display Name and Status5 ms001212
Scenario: Search By Specific Serial Number5 ms001010
Scenario: Search By Status And Get Multiple Matches6 ms001010
Scenario: Search by Device Status And Get One Match7 ms001010
Scenario: Search for a non existent client ID4 ms0066
Scenario: Search for an access info entity by an incorrect user ID35 ms001111
Scenario: Search the role database for a random ID7 ms0077
Scenario: Send BIRTH message and then DC message15 ms001515
Scenario: Send BIRTH message and then DC message while broker ip is NOT set13 ms0066
Scenario: Send BIRTH message and then DC message while broker ip is set by System14 ms0088
Scenario: Send BIRTH message and then DC message while broker ip is set by config file33 ms0088
Scenario: Set a correct minimum for password length10 ms0033
Scenario: Set an incorrect minimum for password length7 ms0066
Scenario: Set environment variables0.12 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 Created7 ms001515
Scenario: Setting InfiniteChildAccounts To True And Decreasing MaxNumberChildAccounts When Sub-accounts Are Already Created7 ms001414
Scenario: Setting Lockout Duration To 0 Seconds9 ms001515
Scenario: Setting Lockout Duration To Negative Value46 ms0077
Scenario: Setting Max Failures To 08 ms001515
Scenario: Setting Max Failures To 111 ms001515
Scenario: Setting Max Failures To 1008 ms001515
Scenario: Setting Max Failures To Negative Value7 ms0077
Scenario: Setting Reset After Login Counter To 0 Seconds7 ms001717
Scenario: Setting Reset After Login Counter To Negative Value7 ms0077
Scenario: Setting configuration without mandatory items must raise an error5 ms0055
Scenario: Simple Jetty with rest-api war5 ms2316
Scenario: Simple create43 ms001111
Scenario: Simple positive scenario for creating daily index6 ms001414
Scenario: Simple positive scenario for creating default - weekly index10 ms001212
Scenario: Simple positive scenario for creating hourly index6 ms001414
Scenario: Start Jetty server for all scenarios5 ms2002
Scenario: Start broker for all scenarios0.19 sec0-2044+244
Scenario: Start datastore for all scenarios0.26 sec202830
Scenario: Start event broker for all scenarios1.5 sec115052
Scenario: Starting a job with Asset Write and Bundle Start steps14 ms003636
Scenario: Starting a job with Asset Write step17 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 step15 ms003535
Scenario: Starting a job with Command Execution and Bundle Start steps13 ms003737
Scenario: Starting a job with Command Execution step14 ms002525
Scenario: Starting a job with Configuration Put and Bundle Start steps12 ms003737
Scenario: Starting a job with Configuration Put step13 ms002525
Scenario: Starting a job with Package Install and Bundle Start steps16 ms003939
Scenario: Starting a job with Package Install step18 ms003232
Scenario: Starting a job with Package Uninstall and Bundle Start steps15 ms003636
Scenario: Starting a job with Package Uninstall step14 ms003333
Scenario: Starting a job with invalid Asset Write step15 ms003131
Scenario: Starting a job with invalid Asset Write step and multiple targets34 ms002929
Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps26 ms003636
Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps and multiple devices23 ms003535
Scenario: Starting a job with invalid Bundle Start step16 ms0-20-2231+2431
Scenario: Starting a job with invalid Bundle Stop step15 ms003131
Scenario: Starting a job with invalid Bundle Stop step and multiple devices86 ms002929
Scenario: Starting a job with invalid Command Execution step20 ms0-20-1827+2027
Scenario: Starting a job with invalid Configuration Put step23 ms003030
Scenario: Starting a job with invalid Configuration Put step and multiple devices24 ms002828
Scenario: Starting a job with invalid Package Install step14 ms002929
Scenario: Starting a job with invalid Package Install step and multiple devices16 ms002626
Scenario: Starting a job with invalid Package Uninstall and Asset Write steps21 ms003434
Scenario: Starting a job with invalid Package Uninstall and Asset Write steps and multiple devices63 ms003232
Scenario: Starting a job with invalid Package Uninstall step21 ms002929
Scenario: Starting a job with invalid Package Uninstall step and multiple targets15 ms002626
Scenario: Starting a job with two Bundle Start steps17 ms003939
Scenario: Starting a job with valid Asset Write step15 ms003131
Scenario: Starting a job with valid Asset Write step and multiple targets37 ms002929
Scenario: Starting a job with valid Bundle Start and Bundle Stop steps13 ms003636
Scenario: Starting a job with valid Bundle Start and Bundle Stop steps and multiple devices14 ms003434
Scenario: Starting a job with valid Bundle Start step14 ms0-20-2231+2431
Scenario: Starting a job with valid Bundle Stop step49 ms003131
Scenario: Starting a job with valid Bundle Stop step and multiple devices15 ms002929
Scenario: Starting a job with valid Command Execution step21 ms0-20-1827+2027
Scenario: Starting a job with valid Configuration Put step14 ms003131
Scenario: Starting a job with valid Configuration Put step and multiple devices23 ms002626
Scenario: Starting a job with valid Package Install step20 ms002929
Scenario: Starting a job with valid Package Install step and multiple devices14 ms002626
Scenario: Starting a job with valid Package Uninstall and Asset Write steps14 ms003333
Scenario: Starting a job with valid Package Uninstall and Asset Write steps and multiple devices25 ms003232
Scenario: Starting a job with valid Package Uninstall step62 ms003030
Scenario: Starting a job with valid Package Uninstall step and multiple targets17 ms002626
Scenario: Starting and stopping the simulator should create a device entry and properly set its status5 ms002020
Scenario: Starting job with Asset Write and Bundle Start steps and multiple devices15 ms003232
Scenario: Starting job with Asset Write step and multiple devices15 ms002828
Scenario: Starting job with Bundle Start step and multiple devices12 ms002828
Scenario: Starting job with Bundle Stop and Bundle Start step and multiple devices15 ms003232
Scenario: Starting job with Bundle Stop step and multiple devices13 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 devices14 ms003232
Scenario: Starting job with Configuration Put step and multiple devices13 ms002828
Scenario: Starting job with Package Download/Install and Bundle Start steps and multiple devices11 ms003838
Scenario: Starting job with Package Download/Install step and multiple devices63 ms003434
Scenario: Starting job with Package Uninstall and Bundle start steps and multiple device17 ms003232
Scenario: Starting job with Package Uninstall step and multiple device13 ms002727
Scenario: Starting job with invalid Bundle Start step and multiple devices32 ms002929
Scenario: Starting job with invalid Command Execution and Package Install steps14 ms003131
Scenario: Starting job with invalid Command Execution step and multiple devices53 ms002828
Scenario: Starting job with invalid Command Execution, invalid Package Install steps and multiple devices15 ms002929
Scenario: Starting job with invalid Configuration Put and Command Execution steps22 ms003232
Scenario: Starting job with invalid Configuration Put and Command Execution steps and multiple devices40 ms003131
Scenario: Starting job with two Bundle Start steps and multiple devices15 ms003232
Scenario: Starting job with valid Bundle Start step and multiple devices19 ms002929
Scenario: Starting job with valid Command Execution and Package Install steps15 ms003131
Scenario: Starting job with valid Command Execution step and multiple devices95 ms002626
Scenario: Starting job with valid Command Execution, valid Package Install steps and multiple devices19 ms002929
Scenario: Starting job with valid Configuration Put and Command Execution steps23 ms003232
Scenario: Starting job with valid Configuration Put and Command Execution steps and multiple devices18 ms003030
Scenario: Stealing link scenario10 ms002828
Scenario: Step definition factory sanity checks7 ms0022
Scenario: Step definition with a duplicate name7 ms0066
Scenario: Step definition with a null name7 ms0066
Scenario: Step definition with a null scope ID7 ms0066
Scenario: Step definition with an empty name8 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.15 sec004646
Scenario: Stop datastore after all scenarios0.15 sec003030
Scenario: Stop event broker for all scenarios1.6 sec115052
Scenario: Stop job with multiple Asset Write and Package Install steps and one target13 ms003737
Scenario: Stop job with multiple Bundle Start and Package Install steps and one target49 ms003737
Scenario: Stop job with multiple Bundle Stop and Package Uninstall steps and one target18 ms003737
Scenario: Stop job with multiple Command Execution and Package Install steps and one target40 ms003434
Scenario: Stop job with multiple Configuration Put and Package Uninstall steps and one target15 ms003535
Scenario: Stop job with multiple targets and Asset Write and Package Install steps and one target25 ms003737
Scenario: Stop job with multiple targets and Bundle Start and Package Install steps19 ms003636
Scenario: Stop job with multiple targets and Bundle Stop and Package Uninstall steps79 ms003737
Scenario: Stop job with multiple targets and Command Execution and Package Install steps22 ms003434
Scenario: Stop job with multiple targets and Configuration Put and Package Uninstall steps0.11 sec003737
Scenario: Test LOOSE user coupling on single connection7 ms0-30-1328+1528-1
Scenario: Test LOOSE user coupling with 3 connections8 ms0-20-2738+2938
Scenario: Test STRICT user coupling on single connection12 ms0-20-1425+1625
Scenario: Test STRICT user coupling with 3 connections and a reserved user14 ms0-20-5263+5463
Scenario: Test STRICT user coupling with user change allowed on single connection7 ms0-20-2536+2736
Scenario: Test account query4 ms0044
Scenario: Test the message store with server timestamp indexing12 ms002626
Scenario: Test the message store with timestamp indexing13 ms002626
Scenario: The Client ID is case sensitive4 ms0088
Scenario: To be defined5 ms001313
Scenario: Translating "CommandRequestMessage" to "KuraRequestMessage"44 ms0044
Scenario: Translating CommandRequestMessage to null26 ms0044
Scenario: Translating empty message to empty message9 ms0044
Scenario: Translating from "AssetRequestMessage" to "AssetResponseMessage"7 ms0044
Scenario: Translating invalid jms data message with valid channel, body and metrics into kura data message5 ms0055
Scenario: Translating invalid kura data message with valid channel, body and metrics into jms message4 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 metrics4 ms0055
Scenario: Translating kura data message with valid channel and with null payload5 ms0055
Scenario: Translating kura data message with valid channel and without body and metrics into jms message5 ms0055
Scenario: Translating kura data message with valid channel, and with null payload3 ms0055
Scenario: Translating kura data message with valid channel, body and metrics into jms message4 ms0055
Scenario: Translating kura data message with valid channel, metrics and without body into jms message5 ms0055
Scenario: Translating kura data message with valid channel, metrics and without body into mqtt message6 ms0055
Scenario: Translating null to KuraRequestMessage9 ms0044
Scenario: Translating of jms message with empty payload and invalid topic that contain only userName into kura data message4 ms0055
Scenario: Translating of jms message with empty payload and valid topic into kura data message6 ms0066
Scenario: Translating of jms message with invalid payload and valid topic into kura data message5 ms0066
Scenario: Translating of jms message with valid payload and valid topic into kura data message6 ms0066
Scenario: Translating of mqtt message with invalid payload and invalid topic into kura data message6 ms0055
Scenario: Translating of mqtt message with invalid payload and with null topic into kura data message5 ms0055
Scenario: Translation of kura data message with valid channel and without body and metrics into mqtt message10 ms0055
Scenario: Translation of kura data message with valid channel, body and metrics into mqtt message7 ms0055
Scenario: Translation of kura data message with valid channel, metrics and without body into mqtt message6 ms0055
Scenario: Translation of mqtt message with empty payload into kura data message7 ms0066
Scenario: Translation of mqtt message with invalid payload and invalid topic into kura response message6 ms0055
Scenario: Translation of mqtt message with invalid payload and valid topic into kura data message8 ms0066
Scenario: Translation of mqtt message with invalid payload and valid topic into kura response message6 ms0066
Scenario: Translation of mqtt message with valid payload and invalid topic into kura response message5 ms0055
Scenario: Translation of mqtt message with valid payload and valid topic into kura data message6 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 permissions54 ms002121
Scenario: Try to change an existing connection ID4 ms0077
Scenario: Try to create an access into entity with an invalid role id13 ms001212
Scenario: Try to delete a non existing device from the registry4 ms0044
Scenario: Try to find a device with an invalid client ID4 ms0033
Scenario: Try to find a device with an invalid registry ID4 ms0033
Scenario: Try to find users granted to "admin" role18 ms001212
Scenario: Try to find users that have assigned specific role20 ms001212
Scenario: Try to modify the connection client ID4 ms0077
Scenario: Try to update the device client ID4 ms0044
Scenario: Uncorrect Login While Lockout Policy Is Disabled11 ms001717
Scenario: Uncorrect Login While Lockout Policy Is Enabled6 ms001717
Scenario: Update a group entry in the database8 ms0099
Scenario: Update a group entry with a false ID9 ms001010
Scenario: Update a job XML definition3 ms001010
Scenario: Update a job description3 ms001010
Scenario: Update a job name5 ms001010
Scenario: Update a non existing device4 ms0055
Scenario: Update a nonexistent job4 ms001010
Scenario: Update a nonexistent step definition7 ms0077
Scenario: Update a step definition name7 ms0077
Scenario: Update a step definition processor name7 ms0088
Scenario: Update a step definition target type7 ms0088
Scenario: Update existing role name7 ms0088
Scenario: Update job id of an existing execution item4 ms0088
Scenario: Update schedule which doesn't exist7 ms0055
Scenario: Update scheduler end date3 ms2169
Scenario: Update scheduler name10 ms0088
Scenario: Update scheduler start date8 ms0088
Scenario: Update the end time of an existing execution item4 ms0099
Scenario: Update trigger definition5 ms2158
Scenario: Update user7 ms0077
Scenario: Update user that doesn't exist5 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 unlock5 ms001717
Scenario: User login with wrong pass, but with enough time between login failures5 ms001919
Scenario: User not locking itself out by using less than max failed login attempts4 ms001717
Scenario: Validate a device client based search with a null client ID4 ms0055
Scenario: Validate a device client based search with an empty client ID4 ms0055
Scenario: Validate a device client search with null scope5 ms0055
Scenario: Validate a device creator with a null client ID4 ms0066
Scenario: Validate a device creator with a null scope ID3 ms0066
Scenario: Validate a device query with a null Scope ID3 ms0044
Scenario: Validate a device search with a null device ID5 ms0066
Scenario: Validate a device search with a null scope ID3 ms0066
Scenario: Validate a null creator4 ms0055
Scenario: Validate a null device4 ms0055
Scenario: Validate a null device count4 ms0055
Scenario: Validate a null device query4 ms0055
Scenario: Validate a regular creator4 ms0044
Scenario: Validate a regular device client search5 ms0044
Scenario: Validate a regular device count3 ms0044
Scenario: Validate a regular device query4 ms0044
Scenario: Validate a regular device search4 ms0055
Scenario: Validate deleting a device with a null device ID4 ms0066
Scenario: Validate deleting a device with a null scope ID6 ms0066
Scenario: Waiting For Lock Duration Time To Pass10 ms001919
Scenario: Waiting For Reset After Login Counter To Pass6 ms001818
empty) scope1 ms0044