Test Result : (root)

18 failures (+2) , 122 skipped (+31)
16,502 tests (+2653)
Took 17 sec.

All Failed Tests

Test NameDurationAge
 Scenario: Creating unique Access Group with special symbols in description.Scenario: Creating unique Access Group with special symbols in description8 ms2
 Scenario: Creating unique Access Group with special symbols in description.Then I find the group with name "groupName53"8 ms2
 Scenario: Execute possible docker steps to show its usage.Given List images by name "kapua/kapua-broker:1.3.0-SNAPSHOT"2 ms1
 Scenario: Execute possible docker steps to show its usage.Scenario: Execute possible docker steps to show its usage3 ms1
 Scenario: Executing Job And Then Restarting Device.Scenario: Executing Job And Then Restarting Device6 ms2
 Scenario: Executing Job And Then Restarting Device.Then I find 4 device events5 ms2
 Scenario: Executing Job When Device Connected After The Specified Start Date And Time.And I confirm the executed job is finished31 ms2
 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 Time33 ms2
 Scenario: Executing Job When Device Connected Before End Date And Time.And I confirm the executed job is finished6 ms2
 Scenario: Executing Job When Device Connected Before End Date And Time.Scenario: Executing Job When Device Connected Before End Date And Time8 ms2
 Scenario: List Endpoints Created From Sub-Account.And I create endpoint with schema "Schema1", domain "abc.com" and port 22222 ms2
 Scenario: List Endpoints Created From Sub-Account.Scenario: List Endpoints Created From Sub-Account3 ms2
 Scenario: List Endpoints From "kapua-sys" Account.Scenario: List Endpoints From "kapua-sys" Account2 ms2
 Scenario: List Endpoints From "kapua-sys" Account.Then I find 3 endpoints1 ms2
 Scenario: List Endpoints From Sub-Account Of Another Sub-Account.And I create endpoint with schema "Schema1", domain "abc.com" and port 22222 ms2
 Scenario: List Endpoints From Sub-Account Of Another Sub-Account.Scenario: List Endpoints From Sub-Account Of Another Sub-Account3 ms2
 Scenario: List Endpoints From Sub-account.And I create endpoint with schema "Schema1", domain "abc.com" and port 22222 ms2
 Scenario: List Endpoints From Sub-account.Scenario: List Endpoints From Sub-account9 ms2

All Tests

ClassDurationFail(diff)Skip(diff)Pass(diff)Total(diff)
Scenario: A fresh database must contain 1 default role in the root scope9 ms0044
Scenario: A newly created account must have some metadata4 ms0033
Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic11 ms0088
Scenario: Access info service sanity checks6 ms0044
Scenario: Access service comparison sanity checks7 ms0033
Scenario: Account based ClientInfo data check28 ms002424
Scenario: Account exactly on its expiration date6 ms0014+1414+14
Scenario: Account name must not be mutable3 ms0066
Scenario: Account past its expiration date15 ms0014+1414+14
Scenario: Account wide metrics check25 ms002828
Scenario: Account with future expiration date9 ms0013+1313+13
Scenario: Account with no expiration date13 ms0013+1313+13
Scenario: Add Access Info domain permissions to new user12 ms002626
Scenario: Add Account permissions to the role in child account11 ms002828
Scenario: Add Credential domain permissions to new user13 ms001818
Scenario: Add Datastore domain permissions to new user0.12 sec001919
Scenario: Add Device Connection domain permissions to kapua-sys user8 ms001111
Scenario: Add Device Connection domain permissions to new user11 ms002323
Scenario: Add Device Event domain permissions to new user15 ms001616
Scenario: Add Device domain permissions to new user10 ms001717
Scenario: Add Domain domain permissions to kapua-sys user15 ms001717
Scenario: Add Domain domain permissions to new user18 ms003232
Scenario: Add Endpoint Permission To The User13 ms003030
Scenario: Add Endpoint_info permissions to the role in child account11 ms003030
Scenario: Add Group domain permissions to new user14 ms001717
Scenario: Add Group permissions to the role in child account20 ms002626
Scenario: Add Job domain permissions to new user12 ms001919
Scenario: Add Role domain permissions to new user18 ms001717
Scenario: Add Role permissions to the role in child account15 ms002626
Scenario: Add Scheduler Permissions With Job Permissions18 ms003131
Scenario: Add Scheduler Permissions Without Job Permissions29 ms002121
Scenario: Add Scheduler permissions to the role in child account15 ms003636
Scenario: Add Tag domain permissions to new user15 ms001515
Scenario: Add Tag permissions to the role in child account11 ms002626
Scenario: Add User domain permissions to new user17 ms002020
Scenario: Add account permissions to the role15 ms001919
Scenario: Add admin role to the user16 ms004444
Scenario: Add and delete Account permissions from the "admin" role11 ms001414
Scenario: Add and delete Device permissions from the "admin" role13 ms001414
Scenario: Add and delete Endpoint_info permissions from the "admin" role26 ms001414
Scenario: Add and delete Group permissions from the "admin" role10 ms001414
Scenario: Add and delete Job permissions from the "admin" role15 ms001414
Scenario: Add and delete Role permissions from the "admin" role12 ms001414
Scenario: Add and delete User permissions from the "admin" role14 ms001515
Scenario: Add datastore permissions to the role14 ms002727
Scenario: Add deleted role again11 ms001010
Scenario: Add device event permissions to the role19 ms003232
Scenario: Add device permissions to the role10 ms001919
Scenario: Add device permissions to the role in child account15 ms002626
Scenario: Add domain, user and access_info permissions to the role9 ms002323
Scenario: Add endpoint_info permissions to the role10 ms003131
Scenario: Add group permissions to the role13 ms001818
Scenario: Add job permissions to the role10 ms001919
Scenario: Add job permissions to the role in child account10 ms002626
Scenario: Add role permissions to the role15 ms001919
Scenario: Add same permission twice to the same role12 ms001414
Scenario: Add same role to user twice10 ms001313
Scenario: Add scheduler permissions to the role11 ms003131
Scenario: Add tag permissions to the role15 ms001818
Scenario: Add user permissions to the role13 ms001919
Scenario: Add user permissions to the role in child account10 ms002626
Scenario: Adding "Cron Job" Schedule With All Valid Parameters7 ms001010
Scenario: Adding "Cron Job" Schedule With All Valid Parameters And Null Cron Value7 ms001010
Scenario: Adding "Cron Job" Schedule With All Valid Parameters Except Cron Format6 ms001111
Scenario: Adding "Cron Job" Schedule With End Date Only12 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 Parameter11 ms001515
Scenario: Adding "Cron Job" Schedule With Start Date Only10 ms001111
Scenario: Adding "Cron Job" Schedule With the same Start and End time13 ms001212
Scenario: Adding "Cron Job" Schedule Without The Start Date Parameter8 ms001010
Scenario: Adding "Device Connect" Schedule With All Valid Parameters9 ms0088
Scenario: Adding "Device Connect" Schedule With End Date Only4 ms001010
Scenario: Adding "Device Connect" Schedule With End Time before Start time10 ms001111
Scenario: Adding "Device Connect" Schedule With Max Length Name8 ms0088
Scenario: Adding "Device Connect" Schedule With Min Length Name6 ms0088
Scenario: Adding "Device Connect" Schedule With Name Only7 ms0099
Scenario: Adding "Device Connect" Schedule With Non-Unique End Date Parameter5 ms001313
Scenario: Adding "Device Connect" Schedule With Non-Unique Name9 ms001313
Scenario: Adding "Device Connect" Schedule With Non-Unique Start Date Parameter9 ms001111
Scenario: Adding "Device Connect" Schedule With Start Date Only6 ms001010
Scenario: Adding "Device Connect" Schedule With the same Start and End time6 ms001111
Scenario: Adding "Device Connect" Schedule Without Name7 ms001010
Scenario: Adding "Device Connect" Schedule Without The Start Date Parameter6 ms0099
Scenario: Adding "Empty" Tag To Device5 ms0055
Scenario: Adding "Interval Job" Schedule With All Valid Parameters9 ms001010
Scenario: Adding "Interval Job" Schedule With End Date Only16 ms001010
Scenario: Adding "Interval Job" Schedule With End Time before Start time5 ms001212
Scenario: Adding "Interval Job" Schedule With Max Length Name6 ms001010
Scenario: Adding "Interval Job" Schedule With Min Length Name7 ms001010
Scenario: Adding "Interval Job" Schedule With Name Only7 ms001010
Scenario: Adding "Interval Job" Schedule With Non-Unique End Date Parameter12 ms001616
Scenario: Adding "Interval Job" Schedule With Non-Unique Name6 ms001515
Scenario: Adding "Interval Job" Schedule With Non-Unique Start Date Parameter4 ms001515
Scenario: Adding "Interval Job" Schedule With Null Interval Number6 ms001212
Scenario: Adding "Interval Job" Schedule With Start Date Only23 ms001111
Scenario: Adding "Interval Job" Schedule With the same Start and End time14 ms001212
Scenario: Adding "Interval Job" Schedule Without Interval Number8 ms001111
Scenario: Adding "Interval Job" Schedule Without The Start Date Parameter10 ms0099
Scenario: Adding "Interval Job" Schedule Without a Name10 ms001111
Scenario: Adding "admin" role to a user in a child account8 ms001414
Scenario: Adding "admin" role to multiple users19 ms001818
Scenario: Adding "admin" role twice13 ms001313
Scenario: Adding Account:Delete permission to user in same scope15 ms002525
Scenario: Adding Account:Delete permission to user in sub-account scope10 ms003030
Scenario: Adding Account:Read and Account:Delete permissions to user in same scope15 ms002121
Scenario: Adding Account:Read and Account:Write permissions to user in same scope11 ms001919
Scenario: Adding Account:Read permission to user in same scope10 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 scope7 ms002323
Scenario: Adding Account:Write permission to user in same scope12 ms002525
Scenario: Adding Account:Write permission to user in sub-account scope14 ms003131
Scenario: Adding Multiple Permissions To User9 ms002020
Scenario: Adding One Permission To User15 ms001111
Scenario: Adding Permissions To Child User52 ms001818
Scenario: Adding Permissions To Parallel User13 ms001818
Scenario: Adding Previously Deleted Permission11 ms002828
Scenario: Adding Previously Deleted Tag From Device Again6 ms001111
Scenario: Adding Regular Device to a Group With Description6 ms001010
Scenario: Adding Regular Device to a Group Without a Description6 ms001212
Scenario: Adding Regular Group Without Description to Device11 ms001010
Scenario: Adding Regular Tag Without Description To Device6 ms0066
Scenario: Adding Same Regular Group Without Description to Device10 ms001414
Scenario: Adding Tag With Long Name Without Description To Device5 ms0066
Scenario: Adding Tag With Numbers Without Description To Device6 ms0066
Scenario: Adding Tag With Short Name Without Description To Device4 ms0066
Scenario: Adding Tag With Special Symbols Without Description To Device3 ms0066
Scenario: Adding all Account permissions to user in same scope8 ms001717
Scenario: Adding all Account permissions to user in sub-account scope9 ms002424
Scenario: Adding existing roles to user10 ms001515
Scenario: Adding role from child account to user in new child account7 ms001515
Scenario: Adding role to multiple users in child account12 ms001818
Scenario: Adding same role twice to user in child account12 ms001515
Scenario: Adding the same role to user twice in child account18 ms001313
Scenario: All device parameters must match the device creator3 ms0033
Scenario: Assign 100 Devices to One Group9 ms001111
Scenario: B1 Broker publish to CTRL_ACC_REPLY22 ms0099
Scenario: B10 Broker create sub-topic on ACL_DATA_ACC is not allowed15 ms0099
Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed6 ms0088
Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI11 ms0099
Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed24 ms0099
Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed8 ms0088
Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY21 ms0099
Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY17 ms0099
Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account12 ms0099
Scenario: B5 Broker publish to CTRL_ACC is not allowed15 ms0099
Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed13 ms0099
Scenario: B7 Broker subscribe on CTRL_ACC is not allowed8 ms0088
Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI18 ms0099
Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed11 ms0099
Scenario: Basic Device Event queries5 ms001010
Scenario: Birth and applications event handling4 ms001212
Scenario: Birth and death message handling7 ms001212
Scenario: Birth and missing event handling5 ms001212
Scenario: Birth message handling from a new device5 ms001313
Scenario: Birth message handling from an existing device7 ms001212
Scenario: Both the parent and child accounts do not expire10 ms0011+1111+11
Scenario: Both the parent and child accounts have the same expiration date9 ms0011+1111+11
Scenario: Captured date based ClientInfo data check36 ms003030
Scenario: Case sensitiveness of named device searches3 ms0044
Scenario: Change an existing step name9 ms0012+1212+12
Scenario: Change role name so it is too short4 ms0066
Scenario: Change the account parent path3 ms0055
Scenario: Changing Client ID7 ms0099
Scenario: Changing Description On Group With Long Description5 ms0077
Scenario: Changing Description On Group With Long Name8 ms0077
Scenario: Changing Description On Group With Numbers In Name5 ms001010
Scenario: Changing Description On Group With Permitted Symbols6 ms0077
Scenario: Changing Description On Group With Short Description6 ms0077
Scenario: Changing Description On Group With Short Name11 ms0077
Scenario: Changing Description On Tag With Long Description5 ms0044
Scenario: Changing Description On Tag With Long Name5 ms0055
Scenario: Changing Description On Tag With Numbers In Name5 ms0066
Scenario: Changing Description On Tag With Permitted Symbols In Name3 ms0044
Scenario: Changing Description On Tag With Short Description5 ms0044
Scenario: Changing Description On Tag With Short Name4 ms0044
Scenario: Changing Device Status To Disabled8 ms0099
Scenario: Changing Device Status To Enabled6 ms0099
Scenario: Changing Group's Description To Non-Uniqe One5 ms0077
Scenario: Changing Group's Description To Uniqe One6 ms0077
Scenario: Changing Group's Name To Contain Invalid Symbols In Name Without Changing Description6 ms0088
Scenario: Changing Group's Name To Contain Permitted Symbols In Name Without Changing Description4 ms0077
Scenario: Changing Group's Name To Non-Unique One12 ms0099
Scenario: Changing Group's Name To Short One Without Changing Description6 ms0077
Scenario: Changing Group's Name To Unique One4 ms0077
Scenario: Changing Group's Name To a Long One Without Changing Description7 ms0077
Scenario: Changing Group's Name To a Too Long One Without Changing Description4 ms0088
Scenario: Changing Group's Name To a Too Short One Without Changing Description6 ms0088
Scenario: Changing Tag's Description To Non-Unique One6 ms0055
Scenario: Changing Tag's Description To Unique One5 ms0077
Scenario: Changing Tag's Name To Contain Invalid Symbols In Name Without Description4 ms0055
Scenario: Changing Tag's Name To Contain Permitted Symbols In Name Without Description5 ms0055
Scenario: Changing Tag's Name To Non-Unique One7 ms0066
Scenario: Changing Tag's Name To Short One Without Description5 ms0077
Scenario: Changing Tag's Name To Unique One8 ms0077
Scenario: Changing Tag's Name To a Long One Without Description5 ms0077
Scenario: Changing Tag's Name To a Too Long One Without Description0 ms0055
Scenario: Changing Tag's Name To a Too Short One Without Description3 ms0055
Scenario: Changing description of a nonexisting role4 ms0077
Scenario: Changing job description to non-unique one5 ms0077
Scenario: Changing job description to the long one4 ms0066
Scenario: Changing job description to unique one7 ms0066
Scenario: Changing job description to very short one8 ms0077
Scenario: Changing job name to a long one without description8 ms0077
Scenario: Changing job name to a too long one without description6 ms0055
Scenario: Changing job name to a too short one without description7 ms0066
Scenario: Changing job name to contain invalid symbols in name without description5 ms0044
Scenario: Changing job name to contain permitted symbols in name without description6 ms0055
Scenario: Changing job name to non-unique one24 ms0088
Scenario: Changing job name to short one without description6 ms0077
Scenario: Changing job name to unique one11 ms0099
Scenario: Changing name of a nonexisting role6 ms0077
Scenario: Changing role description to a valid one2 ms0066
Scenario: Changing role name so it is too long15 ms0066
Scenario: Changing role name to contain special character0 ms0044
Scenario: Changing role name to null2 ms0066
Scenario: Changing role's name to a valid one2 ms0066
Scenario: Channel info queries based on datastore channel filters23 ms005050
Scenario: ChannelInfo client ID and topic data based on the client id26 ms002828
Scenario: ChannelInfo client ID based on the account id29 ms002626
Scenario: ChannelInfo last published date27 ms003030
Scenario: ChannelInfo topic data based on the account id40 ms002626
Scenario: Check account properties4 ms0044
Scenario: Check the Device Connection Domain data seetting5 ms0022
Scenario: Check the database cache coherency26 ms003030
Scenario: Check the mapping for message semantic topics27 ms003030
Scenario: Check the message store29 ms002020
Scenario: Check the sanity of the Device Connection Domain data initialization2 ms0022
Scenario: Child account expires after parent7 ms009+99+9
Scenario: Child account expires before parent7 ms0011+1111+11
Scenario: Child account has null expiration date9 ms009+99+9
Scenario: Client Id based ClientInfo data check27 ms002828
Scenario: Compare domain entries12 ms0033
Scenario: Connect to the system and publish some data79 ms002222
Scenario: Connection Service factory sanity checks1 ms0022
Scenario: Count access info entities in a specific scope8 ms002424
Scenario: Count access role entities by scope9 ms003939
Scenario: Count connections in empty scope3 ms0044
Scenario: Count connections in scope4 ms0055
Scenario: Count devices with a specific BIOS version4 ms0066
Scenario: Count domains in a blank database5 ms0044
Scenario: Count domains in the database13 ms0077
Scenario: Count events in empty scope5 ms0066
Scenario: Count groups6 ms001414
Scenario: Count groups in a blank database8 ms0055
Scenario: Count job items10 ms007+77+7
Scenario: Count job items in wrong - empty - scope7 ms008+88+8
Scenario: Count role permissions in specific scopes6 ms001818
Scenario: Count roles in specific scopes4 ms001515
Scenario: Count step definition items6 ms0044
Scenario: Count step definitions in wrong (empty) scope8 ms0011
Scenario: Count steps in the database4 ms0015+1515+15
Scenario: Count user4 ms0066
Scenario: Counting created roles items in the DB5 ms0055
Scenario: Create a regular event20 ms0088
Scenario: Create a single device with an empty string for clientID5 ms0044
Scenario: Create a single device with null clientID value3 ms0044
Scenario: Create a valid job entry53 ms0066
Scenario: Create an event with a null scope ID9 ms0077
Scenario: Create and count several execution items for a job4 ms0012+1212+12
Scenario: Create index with specific prefix7 ms001212
Scenario: Create multiple users3 ms0055
Scenario: Create regular access permissions5 ms002020
Scenario: Create same user in different accounts16 ms001515
Scenario: Create scheduler with correct end date7 ms0088
Scenario: Create scheduler with empty schedule name13 ms0088
Scenario: Create scheduler with end date before start date10 ms0099
Scenario: Create scheduler with invalid Retry Interval property7 ms0099
Scenario: Create scheduler with invalid cron job trigger property7 ms0099
Scenario: Create scheduler with invalid schedule name19 ms0088
Scenario: Create scheduler with short schedule name10 ms0088
Scenario: Create scheduler with too long schedule name12 ms0088
Scenario: Create scheduler with valid Retry Interval property7 ms0077
Scenario: Create scheduler with valid cron job trigger property9 ms0077
Scenario: Create scheduler with valid schedule name27 ms0066
Scenario: Create scheduler without Cron Job Trigger property5 ms0099
Scenario: Create scheduler without Retry Interval property7 ms0099
Scenario: Create scheduler without start date14 ms0077
Scenario: Create some regular role permissions9 ms0099
Scenario: Create user that already exist4 ms0077
Scenario: Create user that has more than DB allowed length7 ms0055
Scenario: Create user with short name10 ms0055
Scenario: Create user with special characters in his name6 ms0055
Scenario: Create with permissions10 ms001414
Scenario: Create with permissions and a role7 ms001717
Scenario: Create with permissions and a role in the wrong scope5 ms001515
Scenario: Creating 100 Sub-accounts While InfiniteChildAccounts Is Set To True10 ms007+77+7
Scenario: Creating A Device With Disabled Status4 ms0077
Scenario: Creating A Device With Enabled Status6 ms0077
Scenario: Creating A Device With Long Display Name4 ms0077
Scenario: Creating A Device With Long Name6 ms0077
Scenario: Creating A Device With Name Containing Invalid Symbols6 ms0088
Scenario: Creating A Device With Name Containing Permitted Symbols6 ms0077
Scenario: Creating A Device With No Name6 ms0088
Scenario: Creating A Device With Non-unique Display Name8 ms0077
Scenario: Creating A Device With Non-unique Name5 ms001010
Scenario: Creating A Device With Short Display Name5 ms0077
Scenario: Creating A Device With Short Name7 ms0077
Scenario: Creating A Device With Too Long Display Name8 ms0088
Scenario: Creating A Device With Too Long Name4 ms0088
Scenario: Creating A Device With Unique Name5 ms0099
Scenario: Creating A Valid Account12 ms005+55+5
Scenario: Creating An Account With Long Name9 ms005+55+5
Scenario: Creating An Account With Long Organization Name7 ms005+55+5
Scenario: Creating An Account With Non-unique Name7 ms008+88+8
Scenario: Creating An Account With Numbers And Valid Symbols In Name7 ms005+55+5
Scenario: Creating An Account With Short Name5 ms005+55+5
Scenario: Creating An Account With Short Organization Name7 ms005+55+5
Scenario: Creating An Account With Special Symbols In Organization Name9 ms005+55+5
Scenario: Creating An Account With Too Long Organization Name7 ms006+66+6
Scenario: Creating An Account With Unique Name7 ms007+77+7
Scenario: Creating An Account With Wrong TLD Format In Email10 ms0010+1010+10
Scenario: Creating An Account Without Email7 ms006+66+6
Scenario: Creating An Account Without Name9 ms006+66+6
Scenario: Creating An Account Without Ogranization Name6 ms006+66+6
Scenario: Creating And Account Without "@" In Email9 ms006+66+6
Scenario: Creating Devices And Than Setting Device Service So It Does Not Allow Devices8 ms0012+1212+12
Scenario: Creating Devices And Then Changing Device Service Values11 ms0010+1010+10
Scenario: Creating Devices Under Account That Allows Infinite Child Devices8 ms0010+1010+10
Scenario: Creating Devices Under Account That Does Not Allow Devices7 ms009+99+9
Scenario: Creating Devices Under Account That Has Limited Child Devices12 ms0013+1313+13
Scenario: Creating Endpoint Non-Unique "Domain Name"5 ms0088
Scenario: Creating Endpoint Non-Unique "Port"4 ms0088
Scenario: Creating Endpoint Non-Unique "Schema"4 ms0099
Scenario: Creating Endpoint With "Domain Name" Only3 ms0066
Scenario: Creating Endpoint With "Port" Only6 ms0066
Scenario: Creating Endpoint With "Schema" Only5 ms0066
Scenario: Creating Endpoint With Disabled Secure Field5 ms0066
Scenario: Creating Endpoint With Enabled Secure Field5 ms0066
Scenario: Creating Endpoint With Invalid "Domain Name"4 ms0066
Scenario: Creating Endpoint With Invalid "Schema" containing symbols1 ms0066
Scenario: Creating Endpoint With Long "Domain Name"3 ms0055
Scenario: Creating Endpoint With Max Length "Port"10 ms0055
Scenario: Creating Endpoint With NULL parameters4 ms0066
Scenario: Creating Endpoint With Schema Containing "http://"4 ms0066
Scenario: Creating Endpoint With Schema Containing "https://"8 ms0066
Scenario: Creating Endpoint With Short "Domain Name"4 ms0066
Scenario: Creating Endpoint With Short "Schema"10 ms0066
Scenario: Creating Endpoint With Small Number "Port"8 ms0066
Scenario: Creating Endpoint With Too Big "Port"4 ms0066
Scenario: Creating Endpoint With Too Long "Domain Name"5 ms0066
Scenario: Creating Endpoint With Too Long "Schema"5 ms0066
Scenario: Creating Endpoint Without "Domain Name"5 ms0066
Scenario: Creating Endpoint Without "Port"4 ms0066
Scenario: Creating Endpoint Without "Schema"3 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 Description5 ms0077
Scenario: Creating Group With Invalid Symbols In Name With Valid Description6 ms0077
Scenario: Creating Group With Long Name With Valid Description10 ms0066
Scenario: Creating Group With Long Name Without Description12 ms0066
Scenario: Creating Group With Numbers In Name With Valid Description8 ms0088
Scenario: Creating Group With Permitted Symbols And Numbers In Name Without Description5 ms0066
Scenario: Creating Group With Permitted Symbols In Name With Valid Description5 ms0066
Scenario: Creating Group With Short Name With Valid Description7 ms0066
Scenario: Creating Group With Short Name Without Description5 ms0066
Scenario: Creating Group With Too Long Name With Valid Description12 ms0077
Scenario: Creating Group With Too Long Name Without Description8 ms0077
Scenario: Creating Group With Too Short Name With Valid Description8 ms0077
Scenario: Creating Group With Too Short Name Without Description6 ms0077
Scenario: Creating Group Without a Name And With Valid Description11 ms0077
Scenario: Creating Group Without a Name And Without Description10 ms0077
Scenario: Creating Groups And Than Setting Group Service So It Does Not Allow Groups7 ms0011+1111+11
Scenario: Creating Groups And Then Changing InfiniteChildGroups To False And Set MaxNumberChildGroups11 ms0010+1010+10
Scenario: Creating Groups Under Account That Allows Infinite Child Groups9 ms009+99+9
Scenario: Creating Groups Under Account That Does Not Allow Groups8 ms009+99+9
Scenario: Creating Groups Under Account That Has Limited Child Groups7 ms0012+1212+12
Scenario: Creating Jobs And Than Setting Job Service So It Does Not Allow Jobs6 ms0012+1212+12
Scenario: Creating Jobs And Then Changing Job Service Values7 ms0010+1010+10
Scenario: Creating Jobs Under Account That Allows Infinite Child Devices8 ms0010+1010+10
Scenario: Creating Jobs Under Account That Does Not Allow Jobs10 ms009+99+9
Scenario: Creating Jobs Under Account That Has Limited Child Jobs6 ms0013+1313+13
Scenario: Creating Non-Unique Group With Valid Description13 ms0088
Scenario: Creating Non-Unique Tag With Valid Description5 ms0055
Scenario: Creating Non-unique Group Without Description11 ms0088
Scenario: Creating Non-unique Tag Without Description12 ms0044
Scenario: Creating Roles And Than Setting Role Service So It Does Not Allow Roles7 ms0011+1111+11
Scenario: Creating Roles And Then Changing Role Service Values8 ms0010+1010+10
Scenario: Creating Roles Under Account That Allows Infinite Child Roles4 ms0010+1010+10
Scenario: Creating Roles Under Account That Does Not Allow Roles7 ms009+99+9
Scenario: Creating Roles Under Account That Has Limited Child Roles8 ms0012+1212+12
Scenario: Creating Sub-accounts When InfiniteChildAccoounts Is Set To False And maxNumberChildAccounts Is Set7 ms0013+1313+13
Scenario: Creating Sub-accounts When InfiniteChildAccoounts Is Set To True And maxNumberChildAccounts Is Set9 ms0014+1414+14
Scenario: Creating Sub-accounts When InfiniteChildAccounts Is Set To False7 ms009+99+9
Scenario: Creating Sub-accounts when InfiniteChildAccounts Is Set To True7 ms0012+1212+12
Scenario: Creating Tag With Invalid Symbols In Name With Valid Description4 ms0044
Scenario: Creating Tag With Invalid Symbols In Name Without Description3 ms0044
Scenario: Creating Tag With Long Name With Valid Description6 ms0044
Scenario: Creating Tag With Long Name Without Description9 ms0044
Scenario: Creating Tag With Numbers In Name With Valid Description4 ms0044
Scenario: Creating Tag With Numbers In Name Without Description6 ms0044
Scenario: Creating Tag With Permitted Symbols In Name With Valid Description3 ms0044
Scenario: Creating Tag With Permitted Symbols In Name Without Description5 ms0044
Scenario: Creating Tag With Short Name With Valid Description2 ms0044
Scenario: Creating Tag With Short Name Without Description6 ms0044
Scenario: Creating Tag With Too Long Name With Valid Description0 ms0044
Scenario: Creating Tag With Too Long Name Without Description7 ms0044
Scenario: Creating Tag With Too Short Name With Valid Description4 ms0044
Scenario: Creating Tag With Too Short Name Without Description7 ms0044
Scenario: Creating Tag Without a Name And With Valid Description9 ms0044
Scenario: Creating Tag Without a Name And Without Description8 ms0044
Scenario: Creating Tags And Than Setting Tag Service So It Does Not Allow Tags7 ms0011+1111+11
Scenario: Creating Tags And Then Changing Tag Service Values7 ms0010+1010+10
Scenario: Creating Tags Under Account That Allows Infinite Child Devices8 ms0010+1010+10
Scenario: Creating Tags Under Account That Does Not Allow Tags10 ms009+99+9
Scenario: Creating Tags Under Account That Has Limited Child Tags6 ms0012+1212+12
Scenario: Creating Unique Group With Long Description11 ms0066
Scenario: Creating Unique Group With Non-unique Description9 ms0077
Scenario: Creating Unique Group With Short Description10 ms0066
Scenario: Creating Unique Group With Unique Description11 ms0066
Scenario: Creating Unique Group Without Description6 ms0066
Scenario: Creating Unique Tag With Long Description4 ms0044
Scenario: Creating Unique Tag With Non-unique Description4 ms0055
Scenario: Creating Unique Tag With Short Description4 ms0044
Scenario: Creating Unique Tag With Unique Description4 ms0044
Scenario: Creating Unique Tag Without Description22 ms0044
Scenario: Creating Users And Than Setting User Service So It Does Not Allow Users12 ms0011+1111+11
Scenario: Creating Users And Then Changing User Service Values10 ms0010+1010+10
Scenario: Creating Users Under Account That Allows Infinite Child Users6 ms0010+1010+10
Scenario: Creating Users Under Account That Does Not Allow Users9 ms009+99+9
Scenario: Creating Users Under Account That Has Limited Child Users7 ms0012+1212+12
Scenario: Creating Valid Endpoint5 ms0066
Scenario: Creating a Access Group with invalid special symbols in name0 ms0044
Scenario: Creating a Device With Permitted Symbols in its Display Name11 ms0077
Scenario: Creating a Device With Unique Display Name7 ms0088
Scenario: Creating a job with name only10 ms0066
Scenario: Creating a job with null name17 ms0055
Scenario: Creating a job without name with valid description2 ms0055
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 only2 ms0055
Scenario: Creating a role with forbidden symbols in its name5 ms0044
Scenario: Creating a role with name only3 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 enough3 ms0055
Scenario: Creating a role with special characters in the description2 ms0044
Scenario: Creating a role with the name that contains digits3 ms0055
Scenario: Creating a role with too long name0 ms0055
Scenario: Creating a role with too short name3 ms0055
Scenario: Creating a role with valid name and with too long description3 ms0033
Scenario: Creating a role wtih 255 characters long name2 ms0055
Scenario: Creating a single device with case sensitive clientID4 ms0055
Scenario: Creating a single device with clientID that contains 255 characters4 ms0055
Scenario: Creating a single device with clientID that contains 256 characters3 ms0044
Scenario: Creating a single device with clientID that contains invalid character4 ms0044
Scenario: Creating a single device with clientID that contains invalid characters1 ms0044
Scenario: Creating a single device with spaces in clientID4 ms0055
Scenario: Creating a single device with valid clientID5 ms0055
Scenario: Creating a valid Access Group with numbers in name3 ms0055
Scenario: Creating a valid Access Group with only numbers in name4 ms0055
Scenario: Creating a valid Access Group with unique name15 ms0055
Scenario: Creating a valid Access Group with valid special symbols in name5 ms0055
Scenario: Creating a valid role3 ms0055
Scenario: Creating an Access Group with empty name8 ms0044
Scenario: Creating an Access Group with long name4 ms0055
Scenario: Creating an Access Group with short name7 ms0055
Scenario: Creating an Access Group with too long name4 ms0044
Scenario: Creating an Access Group with too short name5 ms0044
Scenario: Creating an Access Group without name and with description3 ms0044
Scenario: Creating and Deleting Endpoint Two Times8 ms002525
Scenario: Creating index with regular user14 ms002525
Scenario: Creating job with invalid symbols in name without description0 ms0044
Scenario: Creating job with long name and valid description6 ms0066
Scenario: Creating job with long name without description8 ms0066
Scenario: Creating job with numbers in name and valid description8 ms0066
Scenario: Creating job with numbers in name without description6 ms0066
Scenario: Creating job with permitted symbols in name without description9 ms0033
Scenario: Creating job with short name and valid job description6 ms0066
Scenario: Creating job with short name without description12 ms0066
Scenario: Creating job with too long name and valid description2 ms0055
Scenario: Creating job with too long name without description7 ms0055
Scenario: Creating job with too short name and valid description6 ms0055
Scenario: Creating job with too short name without description8 ms0055
Scenario: Creating job without name and without description10 ms0055
Scenario: Creating new device and tagging it with specific Tag6 ms001414
Scenario: Creating new device, tagging it with specific Tag and then deleting this Tag10 ms001616
Scenario: Creating non-unique Access Group6 ms0055
Scenario: Creating non-unique Access Group with unique description4 ms0055
Scenario: Creating non-unique job name with valid job description9 ms0077
Scenario: Creating two device with the same clientID4 ms0055
Scenario: Creating two indexes with daily index12 ms001717
Scenario: Creating two indexes with hourly index14 ms001717
Scenario: Creating two indexes with weekly index11 ms001717
Scenario: Creating two roles with the same description2 ms0066
Scenario: Creating two roles with the same name2 ms0077
Scenario: Creating unique Access Group with long description2 ms0055
Scenario: Creating unique Access Group with non-unique description3 ms0066
Scenario: Creating unique Access Group with numbers in description3 ms0055
Scenario: Creating unique Access Group with only numbers in description4 ms0055
Scenario: Creating unique Access Group with short description3 ms0055
Scenario: Creating unique Access Group with special symbols in description16 ms2114
Scenario: Creating unique Access Group with unique description4 ms0055
Scenario: Creating unique job with long description6 ms0066
Scenario: Creating unique job with non-unique description6 ms001010
Scenario: Creating unique job with short description5 ms0066
Scenario: Creating user15 ms0055
Scenario: Creation of access role with neither acess info and role entities9 ms001212
Scenario: Creation of access role without an acess info entity12 ms001212
Scenario: D1 Device publish to CTRL_ACC_REPLY17 ms0099
Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI8 ms0099
Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed20 ms0099
Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed14 ms0077
Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY13 ms0099
Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY18 ms0099
Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account10 ms0099
Scenario: D5 Device subscribe - publish - admin on CTRL_ACC19 ms0099
Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI22 ms0099
Scenario: D7 Device publish to ACL_DATA_ACC is not allowed18 ms0099
Scenario: D8 Device create sub-topic on ACL_DATA_ACC is not allowed18 ms0099
Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed12 ms0088
Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed31 ms0099
Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI16 ms0099
Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed14 ms0099
Scenario: DM13 Data manage subscribe on ACL_CTRL_ACC_NOTIFY is not allowed9 ms0088
Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY23 ms0099
Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY19 ms0099
Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account8 ms0099
Scenario: DM5 Data manage publish to CTRL_ACC is not allowed29 ms0099
Scenario: DM6 Data manage create sub-topic on CTRL_ACC is not allowed16 ms0099
Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed12 ms0088
Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI15 ms0099
Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC16 ms0099
Scenario: DV1 Data view publish to CTRL_ACC_REPLY20 ms0099
Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed18 ms0099
Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed11 ms001010
Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed20 ms0099
Scenario: DV13 Data view create sub-topic on ACL_CTRL_ACC_CLI is not allowed12 ms0099
Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed15 ms0099
Scenario: DV17 Data view subscribe on ACL_CTRL_ACC_NOTIFY is not allowed12 ms0088
Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY19 ms0099
Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY16 ms0099
Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account10 ms0099
Scenario: DV5 Data view publish to CTRL_ACC is not allowed17 ms0099
Scenario: DV6 Data view create sub-topic on CTRL_ACC is not allowed15 ms0099
Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed8 ms0088
Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI12 ms0099
Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed20 ms0099
Scenario: Decreasing MaxNumberChildAccounts When Sub-accounts Are Already Created7 ms0015+1515+15
Scenario: Delete Kapua system user7 ms0055
Scenario: Delete a access info entity with permissions and roles8 ms001717
Scenario: Delete a connection from the database3 ms0088
Scenario: Delete a group from the database6 ms001010
Scenario: Delete a group from the database - Unknown group ID6 ms0066
Scenario: Delete a job9 ms0011+1111+11
Scenario: Delete a job execution item4 ms009+99+9
Scenario: Delete a job execution item twice3 ms0010+1010+10
Scenario: Delete a job twice4 ms0010+1010+10
Scenario: Delete a non existent event6 ms0077
Scenario: Delete a non existing connection3 ms0077
Scenario: Delete a non existing permission entity4 ms001616
Scenario: Delete a non existing role entry7 ms001111
Scenario: Delete a non-existing step4 ms0013+1313+13
Scenario: Delete a nonexistent domain8 ms0055
Scenario: Delete a step definition7 ms0088
Scenario: Delete a step definition twice5 ms0077
Scenario: Delete access role from user8 ms001212
Scenario: Delete an access info entity twice10 ms001111
Scenario: Delete an access info entity using the wrong scope ID10 ms001111
Scenario: Delete an existing access info entity12 ms001212
Scenario: Delete an existing access permission entity7 ms001515
Scenario: Delete an existing access role entry9 ms002222
Scenario: Delete an existing account5 ms0055
Scenario: Delete an existing device from the registry3 ms0044
Scenario: Delete an existing event5 ms0099
Scenario: Delete an existing role12 ms001010
Scenario: Delete an existing role twice11 ms001616
Scenario: Delete an existing step3 ms0012+1212+12
Scenario: Delete items based on query results34 ms008484
Scenario: Delete items by date ranges0.26 sec00132132
Scenario: Delete items by the datastore ID56 ms006666
Scenario: Delete middle child expiration7 ms0015+1515+15
Scenario: Delete nonexisting account7 ms0044
Scenario: Delete nonexisting role permission6 ms001313
Scenario: Delete parent expiration8 ms0014+1414+14
Scenario: Delete permissions from role29 ms001818
Scenario: Delete role permissions9 ms001010
Scenario: Delete scheduler6 ms0088
Scenario: Delete scheduler which doesn't exist6 ms0055
Scenario: Delete the Kapua system account4 ms0055
Scenario: Delete the last created domain entry12 ms0088
Scenario: Delete user5 ms0066
Scenario: Delete user that doesn't exist3 ms0055
Scenario: Deleting "Cron Schedule" Triggering7 ms001313
Scenario: Deleting "Device Schedule" Triggering11 ms001111
Scenario: Deleting "Interval Schedule" Triggering7 ms001313
Scenario: Deleting Device With Disabled Status5 ms001010
Scenario: Deleting Device With Enabled Status4 ms001010
Scenario: Deleting Endpoint Domain Name And Leaving it Empty4 ms0088
Scenario: Deleting Endpoint Which Does Not Exist4 ms0066
Scenario: Deleting Existing Group6 ms0088
Scenario: Deleting Existing Group And Creating It Again With Same Name6 ms001212
Scenario: Deleting Existing Tag And Creating It Again With Same Name4 ms0077
Scenario: Deleting Group's Name And Leaving It Empty Without Changing Description5 ms0088
Scenario: Deleting Non-Existent Tag5 ms0077
Scenario: Deleting Tag From Device3 ms0088
Scenario: Deleting Tag's Name And Leaving It Empty Without Description4 ms0055
Scenario: Deleting Unexisitng Group6 ms001111
Scenario: Deleting a Permission9 ms002121
Scenario: Deleting a non-existing Access Group2 ms0066
Scenario: Deleting a role twice2 ms0077
Scenario: Deleting admin role10 ms0077
Scenario: Deleting an existing Access Group3 ms0055
Scenario: Deleting an existing Access Group and creating it again with the same name3 ms0077
Scenario: Deleting an existing role2 ms0066
Scenario: Deleting default permissions from admin role10 ms001212
Scenario: Deleting existing tag15 ms0099
Scenario: Deleting role after adding it to user7 ms001414
Scenario: Deleting role after it has been added to user in child account15 ms001616
Scenario: Deleting user in account that is higher in hierarchy17 ms002323
Scenario: Deleting user in account that is lower in hierarchy14 ms002424
Scenario: Device connection update3 ms0077
Scenario: Device factory sanity checks1 ms0022
Scenario: Device queries6 ms001010
Scenario: Device query - find by BIOS version4 ms0077
Scenario: Domain entry query4 ms0055
Scenario: Domain with null actions6 ms0055
Scenario: Domain with null name5 ms0055
Scenario: Domains with duplicate names7 ms0088
Scenario: Duplicate group name in root scope9 ms001010
Scenario: Duplicate role names4 ms0077
Scenario: Editing Access Group description to description with numbers3 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 description3 ms0055
Scenario: Editing Access Group description to non-unique one2 ms0055
Scenario: Editing Access Group description to short description3 ms0055
Scenario: Editing Access Group description to unique one3 ms0077
Scenario: Editing Access Group name to a long one2 ms0077
Scenario: Editing Access Group name to a too long one4 ms0055
Scenario: Editing Access Group name to empty name3 ms0055
Scenario: Editing Access Group name to name that contains numbers2 ms0077
Scenario: Editing Access Group name to name that contains only numbers3 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 symbols3 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 one3 ms0077
Scenario: Editing Endpoint Domain Name So It Contains Invalid Symbols6 ms0088
Scenario: Editing Endpoint Domain Name So It Contains Only Numbers6 ms0088
Scenario: Editing Endpoint Domain Name So It Has Max Value5 ms0077
Scenario: Editing Endpoint Domain Name So It Has Min Value3 ms0077
Scenario: Editing Endpoint Domain Name To Non-unique Value3 ms0099
Scenario: Editing Endpoint Domain Name To Unique Value4 ms0077
Scenario: Editing Endpoint Port To Non-unique Value4 ms0099
Scenario: Editing Endpoint Port To Unique Value7 ms0077
Scenario: Editing Endpoint Schema And Leaving It Empty5 ms0088
Scenario: Editing Endpoint Schema So It Contains "http://"8 ms0088
Scenario: Editing Endpoint Schema So It Contains "https://"3 ms0088
Scenario: Editing Endpoint Schema So It Contains Invalid Symbols4 ms0088
Scenario: Editing Endpoint Schema So It Contains Only Numbers5 ms0088
Scenario: Editing Endpoint Schema So It Has Max Length7 ms0077
Scenario: Editing Endpoint Schema So It Has Min Length10 ms0077
Scenario: Editing Endpoint Schema To Non-unique Value4 ms0088
Scenario: Editing Endpoint Schema To Unique Value5 ms0077
Scenario: Editing Endpoint Secure Field To Non-unique Value7 ms0099
Scenario: Editing Endpoint Secure Field To Unique Value2 ms0077
Scenario: Editing Endpoint To NULL Values4 ms001414
Scenario: Editing Endpoint To Non-unique Endpoint7 ms001010
Scenario: Editing Group's Name To Contain Numbers Without Changing Description7 ms0077
Scenario: Editing Tag's Name To Contain Numbers Without Description8 ms0077
Scenario: Empty query results are supported9 ms0088
Scenario: Event factory sanity checks4 ms0022
Scenario: Event service domain check4 ms0022
Scenario: Every account must have the default configuration items4 ms0033
Scenario: Execute possible docker steps to show its usage5 ms2+231+31033+33
Scenario: Executing Job And Then Restarting Device12 ms2162745
Scenario: Executing Job When Device Connected After End Date And Time25 ms003838
Scenario: Executing Job When Device Connected After The Specified Start Date And Time65 ms263038
Scenario: Executing Job When Device Connected Before End Date And Time14 ms263139
Scenario: Executing Job When Device Connected Before The Specified Start Date And Time32 ms003737
Scenario: Executing Job Without Steps35 ms004040
Scenario: Extra long continuous test with multiple subscenarios with LOOSE default connection mode43 ms00419+419419+419
Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode26 ms00397+397397+397
Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode and no previously defined devices23 ms00305+305305+305
Scenario: Find a connection by its IDs3 ms0066
Scenario: Find a connection by its client ID3 ms0066
Scenario: Find a group entry in the database5 ms0099
Scenario: Find a non existing event6 ms0066
Scenario: Find account by Id5 ms0044
Scenario: Find account by Ids5 ms0044
Scenario: Find account by name5 ms0044
Scenario: Find account by random Id6 ms0033
Scenario: Find all child accounts9 ms0033
Scenario: Find an access info entity10 ms001111
Scenario: Find an access info entity by user ID18 ms001010
Scenario: Find an event by its ID7 ms0066
Scenario: Find an existing access role entity9 ms001313
Scenario: Find by name nonexisting account4 ms0033
Scenario: Find correct number of messages by corresponding metric0.18 sec005858
Scenario: Find device by client ID3 ms0033
Scenario: Find device by registry ID3 ms0044
Scenario: Find last created permission4 ms001212
Scenario: Find multiple users3 ms0055
Scenario: Find role by ID6 ms0077
Scenario: Find self account by id11 ms0011+1111+11
Scenario: Find self account by id and scope id15 ms0011+1111+11
Scenario: Find self account by name7 ms0011+1111+11
Scenario: Find the last created domain entry6 ms0055
Scenario: Find user by id3 ms0055
Scenario: Find user by its email3 ms0066
Scenario: Find user by its phone number3 ms0066
Scenario: Find user by name3 ms0055
Scenario: Find user by name that doesn't exist3 ms0033
Scenario: Find user with id and scope id that doesn't exist4 ms0033
Scenario: Finding all messages by selecting all metrics0.21 sec004040
Scenario: Finding correct number of messages by corresponding two metrics0.65 sec005252
Scenario: Finding messages with incorrect metric parameters0.16 sec007272
Scenario: Finding user by expiration date in the future6 ms0055
Scenario: Finding user by expiration date in the past3 ms0066
Scenario: Finding user by expiration date in the present3 ms0066
Scenario: Generic connection query3 ms0088
Scenario: Get metadata4 ms0033
Scenario: Group with a null name9 ms0077
Scenario: Handle account creation24 ms0033
Scenario: Handle duplicate account names7 ms0055
Scenario: Handle null account name7 ms0044
Scenario: Handling of 2 birth messages8 ms001212
Scenario: Handling of a disconnect message from a non existing device6 ms001010
Scenario: Have Two Devices in The Same Group Without Description11 ms001313
Scenario: I try to find a non-existing connection4 ms0066
Scenario: If user credential expiration date is before today, user can not login7 ms001414
Scenario: If user credential expiration date is today, user can not login it is day inclusive9 ms001414
Scenario: If user credential expiration date is tomorrow, user can login6 ms001313
Scenario: If user credential is in state disabled, user can not login7 ms001414
Scenario: If user credential is in state enabled, user can login4 ms001313
Scenario: If user expiration date is before today, user can not login12 ms001313
Scenario: If user expiration date is today, user can not login because expiration date was reached9 ms001313
Scenario: If user expiration date is tomorrow, user can login4 ms001212
Scenario: Init Security Context for all scenarios0.19 sec0048+2648+26
Scenario: Installing a package20 ms001313
Scenario: Interval Job" Schedule With Too Long Name7 ms001111
Scenario: It must be possible to query for specific entries in the role database8 ms0088
Scenario: It should not be possible to change the configuration items3 ms0055
Scenario: Job execution factory sanity checks4 ms002+22+2
Scenario: Job factory sanity checks4 ms003+33+3
Scenario: Job with a duplicate name7 ms009+99+9
Scenario: Job with a null name8 ms008+88+8
Scenario: Job with a null scope ID4 ms009+99+9
Scenario: Job with an empty name7 ms008+88+8
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-account11 ms212115
Scenario: MetricsInfo client ID and topic data based on the client id55 ms003434
Scenario: MetricsInfo last published date27 ms004848
Scenario: Modify a role that was deleted15 ms0099
Scenario: Modify an existing account4 ms0044
Scenario: Modify last child expiration so that it still expires before parent6 ms0014+1414+14
Scenario: Modify middle child expiration so that it still expires before parent9 ms0014+1414+14
Scenario: Modify middle child expiration to outlive parent6 ms0015+1515+15
Scenario: Modify nonexisting account4 ms0066
Scenario: Modify parent expiration so that it still expires after child8 ms0014+1414+14
Scenario: Modify parent expiration to before child expiration7 ms0015+1515+15
Scenario: Modifying Sub-account of a different parent account10 ms002525
Scenario: Moving Device From One Group With Description to Another6 ms001414
Scenario: Nameless role entry7 ms0077
Scenario: Negative scenario when client connects twice with same client id22 ms001111
Scenario: New connection with reserved ID11 ms0034+3434+34
Scenario: Permission factory sanity checks7 ms0033
Scenario: Positive scenario without stealing link27 ms001212
Scenario: Query based on message ordering23 ms002020
Scenario: Query based on metrics ordering34 ms002020
Scenario: Query before schema search30 ms008282
Scenario: Query for a specific group by name7 ms001616
Scenario: Query for all the access info entities of a specific user5 ms001818
Scenario: Query for all the access info entities of an invalid user6 ms001010
Scenario: Query for executions of a specific job5 ms0019+1919+19
Scenario: Query for jobs with specified name4 ms009+99+9
Scenario: Query for step definitions6 ms0077
Scenario: Query user4 ms0066
Scenario: Querying Other Items With All Account Permissions13 ms003939
Scenario: Regular connection4 ms0077
Scenario: Regular creation of Access Role entity8 ms001414
Scenario: Regular domain6 ms0055
Scenario: Regular group in random scope10 ms0077
Scenario: Regular group in root scope26 ms0077
Scenario: Regular job creation4 ms0010+1010+10
Scenario: Regular job execution creation4 ms008+88+8
Scenario: Regular role creation5 ms0099
Scenario: Regular step creation4 ms0012+1212+12
Scenario: Regular step definition creation6 ms0077
Scenario: Regular step definition with a property list6 ms0044
Scenario: Reset Security Context for all scenarios0.15 sec0048+2648+26
Scenario: Restarting a job with Asset Write and Bundle Start steps22 ms002828
Scenario: Restarting a job with Command Execution and Bundle Start steps24 ms002828
Scenario: Restarting a job with Configuration Put and Bundle Start steps27 ms002828
Scenario: Restarting a job with Package Uninstall and Bundle Start steps21 ms002828
Scenario: Restarting a job with invalid Configuration Put and multiple devices two times58 ms003333
Scenario: Restarting a job with invalid Configuration Put step two times41 ms003636
Scenario: Restarting a job with invalid Package Install step and multiple devices two times22 ms003131
Scenario: Restarting a job with invalid Package Install step two times23 ms003434
Scenario: Restarting a job with invalid Package Uninstall step and multiple devices two times33 ms003232
Scenario: Restarting a job with invalid Package Uninstall step two times35 ms003434
Scenario: Restarting a job with valid Configuration Put step and multiple devices two times32 ms003333
Scenario: Restarting a job with valid Configuration Put step two times33 ms003636
Scenario: Restarting a job with valid Package Install step and multiple devices two times38 ms002929
Scenario: Restarting a job with valid Package Install step two times32 ms003434
Scenario: Restarting a job with valid Package Uninstall step and multiple devices two times26 ms003030
Scenario: Restarting a job with valid Package Uninstall step two times22 ms003232
Scenario: Restarting job With invalid Asset Write and multiple two times40 ms003434
Scenario: Restarting job With valid Asset Write step two times30 ms003636
Scenario: Restarting job with Asset Write and Bundle Start steps and multiple devices23 ms003131
Scenario: Restarting job with Asset Write step24 ms002525
Scenario: Restarting job with Asset Write step and multiple devices24 ms002828
Scenario: Restarting job with Bundle Start step22 ms002525
Scenario: Restarting job with Bundle Start step and multiple devices21 ms002727
Scenario: Restarting job with Bundle Stop and Bundle Start step and multiple devices15 ms003131
Scenario: Restarting job with Bundle Stop and Bundle Start steps21 ms002929
Scenario: Restarting job with Bundle Stop step21 ms002525
Scenario: Restarting job with Bundle Stop step and multiple devices23 ms002727
Scenario: Restarting job with Command Execution and Bundle Start steps and multiple devices23 ms003131
Scenario: Restarting job with Command Execution step22 ms002525
Scenario: Restarting job with Command Execution step and multiple devices32 ms002727
Scenario: Restarting job with Configuration Put and Bundle Start steps and multiple devices21 ms003131
Scenario: Restarting job with Configuration Put step23 ms002525
Scenario: Restarting job with Configuration Put step and multiple devices27 ms002727
Scenario: Restarting job with Package Download/Install and Bundle Start steps and multiple devices53 ms005959
Scenario: Restarting job with Package Download/Install step and multiple devices23 ms002727
Scenario: Restarting job with Package Install step20 ms002525
Scenario: Restarting job with Package Uninstall and Bundle start steps and multiple device49 ms003131
Scenario: Restarting job with Package Uninstall step21 ms002525
Scenario: Restarting job with Package Uninstall step and multiple device22 ms002727
Scenario: Restarting job with invalid Asset Write step two times52 ms003636
Scenario: Restarting job with invalid Bundle Start and Bundle Stop steps and multiple devices two times41 ms004141
Scenario: Restarting job with invalid Bundle Start and Bundle Stop steps two times21 ms004343
Scenario: Restarting job with invalid Bundle Start step and multiple devices two times38 ms003535
Scenario: Restarting job with invalid Bundle Start step two times28 ms003737
Scenario: Restarting job with invalid Bundle Stop step and multiple devices two times33 ms003535
Scenario: Restarting job with invalid Bundle Stop step two times40 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 times30 ms003737
Scenario: Restarting job with invalid Command Execution step and multiple devices two times42 ms003131
Scenario: Restarting job with invalid Command Execution step two times51 ms003232
Scenario: Restarting job with invalid Configuration Put And Command Execution steps two times34 ms003838
Scenario: Restarting job with invalid Configuration Put and Command Execution steps and multiple devices two times46 ms003737
Scenario: Restarting job with invalid Package Uninstall and Asset Write steps and multiple devices two times29 ms003838
Scenario: Restarting job with invalid Package Uninstall and Asset Write steps two times44 ms004040
Scenario: Restarting job with two Bundle Start steps23 ms002929
Scenario: Restarting job with two Bundle Start steps and multiple devices24 ms003131
Scenario: Restarting job with valid Asset Write step and multiple devices two times38 ms003434
Scenario: Restarting job with valid Bundle Start And Bundle Stop steps two times24 ms004343
Scenario: Restarting job with valid Bundle Start and Bundle Stop steps and multiple devices two times70 ms004141
Scenario: Restarting job with valid Bundle Start step and multiple devices two times44 ms003535
Scenario: Restarting job with valid Bundle Start step two times42 ms003737
Scenario: Restarting job with valid Bundle Stop step and multiple devices two times28 ms003535
Scenario: Restarting job with valid Bundle Stop step two times29 ms003737
Scenario: Restarting job with valid Command Execution and Package Install steps and multiple devices two times55 ms003333
Scenario: Restarting job with valid Command Execution and Package Install steps two times35 ms003434
Scenario: Restarting job with valid Command Execution step and multiple devices two times85 ms003131
Scenario: Restarting job with valid Command Execution step two times48 ms003232
Scenario: Restarting job with valid Configuration Put and Command Execution steps and multiple devices two times44 ms003737
Scenario: Restarting job with valid Configuration Put and Command Execution steps two times31 ms003838
Scenario: Restarting job with valid Package Uninstall and Asset Write steps and multiple devices two times59 ms003636
Scenario: Restarting job with valid Package Uninstall and Asset Write steps two times38 ms003838
Scenario: Role creator sanity checks5 ms0022
Scenario: Role entry with no actions6 ms0066
Scenario: Role object equality check5 ms0022
Scenario: Role service related objects sanity checks7 ms0044
Scenario: Search By Client ID And Get Multiple Matches18 ms003737
Scenario: Search By Client ID And Get No Matches4 ms001010
Scenario: Search By Client ID And Get One Match10 ms0088
Scenario: Search By Client ID and Display Name4 ms001212
Scenario: Search By Client ID and Serial Number25 ms001212
Scenario: Search By Client ID and Status7 ms001212
Scenario: Search By Client ID, Display Name and Serial Number4 ms001212
Scenario: Search By Client ID, Display Name and Status5 ms001212
Scenario: Search By Client ID, Display Name, Serial Number and Status4 ms001212
Scenario: Search By Device Status And Get No Matches5 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 Status8 ms001212
Scenario: Search By Full Client ID And Get One Match5 ms001010
Scenario: Search By Non-existing Client ID And Get No Matches6 ms0088
Scenario: Search By One Letter Of Display Name8 ms0088
Scenario: Search By One Letter Of Serial Number6 ms001212
Scenario: Search By Serial Number And Get Multiple Matches7 ms001414
Scenario: Search By Serial Number And Get No Matches6 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 Match11 ms001010
Scenario: Search for a non existent client ID6 ms0066
Scenario: Search for an access info entity by an incorrect user ID6 ms001111
Scenario: Search the role database for a random ID12 ms0077
Scenario: Send BIRTH message and then DC message24 ms001515
Scenario: Send BIRTH message and then DC message while broker ip is NOT set32 ms0066
Scenario: Send BIRTH message and then DC message while broker ip is set by System24 ms0088
Scenario: Send BIRTH message and then DC message while broker ip is set by config file45 ms0088
Scenario: Set environment variables0.13 sec006161
Scenario: Setting InfiniteChildAccounts To False And Increasing MaxNumberChildAccounts When Sub-accounts Are Already Created14 ms0014+1414+14
Scenario: Setting InfiniteChildAccounts To False When Sub-accounts Are Already Created5 ms0015+1515+15
Scenario: Setting InfiniteChildAccounts To True And Decreasing MaxNumberChildAccounts When Sub-accounts Are Already Created8 ms0014+1414+14
Scenario: Setting Lockout Duration To 0 Seconds9 ms0015+1515+15
Scenario: Setting Lockout Duration To Negative Value8 ms007+77+7
Scenario: Setting Max Failures To 011 ms0015+1515+15
Scenario: Setting Max Failures To 18 ms0015+1515+15
Scenario: Setting Max Failures To 10014 ms0015+1515+15
Scenario: Setting Max Failures To Negative Value16 ms007+77+7
Scenario: Setting Reset After Login Counter To 0 Seconds11 ms0017+1717+17
Scenario: Setting Reset After Login Counter To Negative Value18 ms007+77+7
Scenario: Setting configuration without mandatory items must raise an error5 ms0055
Scenario: Simple create7 ms001111
Scenario: Simple positive scenario for creating daily index11 ms001414
Scenario: Simple positive scenario for creating default - weekly index12 ms001212
Scenario: Simple positive scenario for creating hourly index21 ms001414
Scenario: Start broker for all scenarios0.35 sec0044+244+2
Scenario: Start datastore for all scenarios0.81 sec003030
Scenario: Start event broker for all scenarios0.42 sec0050+250+2
Scenario: Starting a job with Asset Write and Bundle Start steps64 ms003636
Scenario: Starting a job with Asset Write step28 ms002525
Scenario: Starting a job with Bundle Start step20 ms003434
Scenario: Starting a job with Bundle Stop and Bundle Start steps21 ms003939
Scenario: Starting a job with Bundle Stop step26 ms003535
Scenario: Starting a job with Command Execution and Bundle Start steps25 ms003737
Scenario: Starting a job with Command Execution step28 ms002525
Scenario: Starting a job with Configuration Put and Bundle Start steps20 ms003737
Scenario: Starting a job with Configuration Put step22 ms002525
Scenario: Starting a job with Package Install and Bundle Start steps27 ms003939
Scenario: Starting a job with Package Install step28 ms003232
Scenario: Starting a job with Package Uninstall and Bundle Start steps26 ms003636
Scenario: Starting a job with Package Uninstall step24 ms003333
Scenario: Starting a job with invalid Asset Write step29 ms003131
Scenario: Starting a job with invalid Asset Write step and multiple targets69 ms002929
Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps25 ms003636
Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps and multiple devices35 ms003535
Scenario: Starting a job with invalid Bundle Start step59 ms003131
Scenario: Starting a job with invalid Bundle Stop step24 ms003131
Scenario: Starting a job with invalid Bundle Stop step and multiple devices36 ms002929
Scenario: Starting a job with invalid Command Execution step35 ms002727
Scenario: Starting a job with invalid Configuration Put step57 ms003030
Scenario: Starting a job with invalid Configuration Put step and multiple devices32 ms002828
Scenario: Starting a job with invalid Package Install step33 ms002929
Scenario: Starting a job with invalid Package Install step and multiple devices24 ms002626
Scenario: Starting a job with invalid Package Uninstall and Asset Write steps22 ms003434
Scenario: Starting a job with invalid Package Uninstall and Asset Write steps and multiple devices51 ms003232
Scenario: Starting a job with invalid Package Uninstall step27 ms002929
Scenario: Starting a job with invalid Package Uninstall step and multiple targets34 ms002626
Scenario: Starting a job with two Bundle Start steps23 ms003939
Scenario: Starting a job with valid Asset Write step45 ms003131
Scenario: Starting a job with valid Asset Write step and multiple targets26 ms002929
Scenario: Starting a job with valid Bundle Start and Bundle Stop steps18 ms003636
Scenario: Starting a job with valid Bundle Start and Bundle Stop steps and multiple devices32 ms003434
Scenario: Starting a job with valid Bundle Start step31 ms003131
Scenario: Starting a job with valid Bundle Stop step30 ms003131
Scenario: Starting a job with valid Bundle Stop step and multiple devices34 ms002929
Scenario: Starting a job with valid Command Execution step44 ms002727
Scenario: Starting a job with valid Configuration Put step30 ms003131
Scenario: Starting a job with valid Configuration Put step and multiple devices19 ms002626
Scenario: Starting a job with valid Package Install step41 ms002929
Scenario: Starting a job with valid Package Install step and multiple devices42 ms002626
Scenario: Starting a job with valid Package Uninstall and Asset Write steps20 ms003333
Scenario: Starting a job with valid Package Uninstall and Asset Write steps and multiple devices53 ms003232
Scenario: Starting a job with valid Package Uninstall step35 ms003030
Scenario: Starting a job with valid Package Uninstall step and multiple targets55 ms002626
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 devices24 ms003232
Scenario: Starting job with Asset Write step and multiple devices23 ms002828
Scenario: Starting job with Bundle Start step and multiple devices21 ms002828
Scenario: Starting job with Bundle Stop and Bundle Start step and multiple devices29 ms003232
Scenario: Starting job with Bundle Stop step and multiple devices24 ms002828
Scenario: Starting job with Command Execution and Bundle Start steps and multiple devices28 ms003232
Scenario: Starting job with Command Execution step and multiple devices22 ms002828
Scenario: Starting job with Configuration Put and Bundle Start steps and multiple devices22 ms003232
Scenario: Starting job with Configuration Put step and multiple devices22 ms002828
Scenario: Starting job with Package Download/Install and Bundle Start steps and multiple devices34 ms003838
Scenario: Starting job with Package Download/Install step and multiple devices33 ms003434
Scenario: Starting job with Package Uninstall and Bundle start steps and multiple device25 ms003232
Scenario: Starting job with Package Uninstall step and multiple device35 ms002727
Scenario: Starting job with invalid Bundle Start step and multiple devices38 ms002929
Scenario: Starting job with invalid Command Execution and Package Install steps42 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 devices46 ms002929
Scenario: Starting job with invalid Configuration Put and Command Execution steps37 ms003232
Scenario: Starting job with invalid Configuration Put and Command Execution steps and multiple devices39 ms003131
Scenario: Starting job with two Bundle Start steps and multiple devices21 ms003232
Scenario: Starting job with valid Bundle Start step and multiple devices37 ms002929
Scenario: Starting job with valid Command Execution and Package Install steps32 ms003131
Scenario: Starting job with valid Command Execution step and multiple devices52 ms002626
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 steps21 ms003232
Scenario: Starting job with valid Configuration Put and Command Execution steps and multiple devices43 ms003030
Scenario: Stealing link scenario16 ms002828
Scenario: Step definition factory sanity checks3 ms0022
Scenario: Step definition with a duplicate name6 ms0066
Scenario: Step definition with a null name5 ms0066
Scenario: Step definition with a null scope ID5 ms0066
Scenario: Step definition with an empty name6 ms0055
Scenario: Step factory sanity checks4 ms002+22+2
Scenario: Step with a null scope ID4 ms0012+1212+12
Scenario: Stop broker after all scenarios0.32 sec0046+246+2
Scenario: Stop datastore after all scenarios0.21 sec003030
Scenario: Stop event broker for all scenarios0.38 sec0050+250+2
Scenario: Stop job with multiple Asset Write and Package Install steps and one target22 ms003737
Scenario: Stop job with multiple Bundle Start and Package Install steps and one target36 ms003737
Scenario: Stop job with multiple Bundle Stop and Package Uninstall steps and one target28 ms003737
Scenario: Stop job with multiple Command Execution and Package Install steps and one target25 ms003434
Scenario: Stop job with multiple Configuration Put and Package Uninstall steps and one target57 ms003535
Scenario: Stop job with multiple targets and Asset Write and Package Install steps and one target38 ms003737
Scenario: Stop job with multiple targets and Bundle Start and Package Install steps28 ms003636
Scenario: Stop job with multiple targets and Bundle Stop and Package Uninstall steps39 ms003737
Scenario: Stop job with multiple targets and Command Execution and Package Install steps86 ms003434
Scenario: Stop job with multiple targets and Configuration Put and Package Uninstall steps27 ms003737
Scenario: Test LOOSE user coupling on single connection10 ms0028+2828+28
Scenario: Test LOOSE user coupling with 3 connections10 ms0038+3838+38
Scenario: Test STRICT user coupling on single connection19 ms0025+2525+25
Scenario: Test STRICT user coupling with 3 connections and a reserved user20 ms0063+6363+63
Scenario: Test STRICT user coupling with user change allowed on single connection11 ms0036+3636+36
Scenario: Test account query5 ms0044
Scenario: Test the message store with server timestamp indexing21 ms002626
Scenario: Test the message store with timestamp indexing28 ms002626
Scenario: The Client ID is case sensitive3 ms0088
Scenario: To be defined5 ms001313
Scenario: Translating "CommandRequestMessage" to "KuraRequestMessage"31 ms0044
Scenario: Translating CommandRequestMessage to null9 ms0044
Scenario: Translating empty message to empty message7 ms0044
Scenario: Translating from "AssetRequestMessage" to "AssetResponseMessage"5 ms0044
Scenario: Translating invalid jms data message with valid channel, body and metrics into kura data message2 ms0055
Scenario: Translating invalid kura data message with valid channel, body and metrics into jms message2 ms0055
Scenario: Translating invalid kura data message with valid channel, body and metrics into mqtt message3 ms0055
Scenario: Translating kura data message with null channel, and payload without body and with metrics3 ms0055
Scenario: Translating kura data message with valid channel and with null payload3 ms0055
Scenario: Translating kura data message with valid channel and without body and metrics into jms message3 ms0055
Scenario: Translating kura data message with valid channel, and with null payload2 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 message3 ms0055
Scenario: Translating kura data message with valid channel, metrics and without body into mqtt message4 ms0055
Scenario: Translating null to KuraRequestMessage6 ms0044
Scenario: Translating of jms message with empty payload and invalid topic that contain only userName into kura data message3 ms0055
Scenario: Translating of jms message with empty payload and valid topic into kura data message2 ms0066
Scenario: Translating of jms message with invalid payload and valid topic into kura data message3 ms0066
Scenario: Translating of jms message with valid payload and valid topic into kura data message2 ms0066
Scenario: Translating of mqtt message with invalid payload and invalid topic into kura data message3 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 message3 ms0055
Scenario: Translation of kura data message with valid channel, body and metrics into mqtt message3 ms0055
Scenario: Translation of kura data message with valid channel, metrics and without body into mqtt message2 ms0055
Scenario: Translation of mqtt message with empty payload into kura data message5 ms0066
Scenario: Translation of mqtt message with invalid payload and invalid topic into kura response message3 ms0055
Scenario: Translation of mqtt message with invalid payload and valid topic into kura data message5 ms0066
Scenario: Translation of mqtt message with invalid payload and valid topic into kura response message4 ms0066
Scenario: Translation of mqtt message with valid payload and invalid topic into kura response message4 ms0055
Scenario: Translation of mqtt message with valid payload and valid topic into kura data message5 ms0066
Scenario: Translation of mqtt message with valid payload and valid topic into kura response message3 ms0066
Scenario: Try to add two different roles with same permissions12 ms002121
Scenario: Try to change an existing connection ID3 ms0077
Scenario: Try to create an access into entity with an invalid role id5 ms001212
Scenario: Try to delete a non existing device from the registry3 ms0044
Scenario: Try to find a device with an invalid client ID3 ms0033
Scenario: Try to find a device with an invalid registry ID3 ms0033
Scenario: Try to find users granted to "admin" role12 ms001212
Scenario: Try to find users that have assigned specific role7 ms001212
Scenario: Try to modify the connection client ID3 ms0077
Scenario: Try to update the device client ID4 ms0044
Scenario: Uncorrect Login While Lockout Policy Is Disabled8 ms0017+1717+17
Scenario: Uncorrect Login While Lockout Policy Is Enabled12 ms0017+1717+17
Scenario: Update a group entry in the database8 ms0099
Scenario: Update a group entry with a false ID5 ms001010
Scenario: Update a job XML definition7 ms0010+1010+10
Scenario: Update a job description3 ms0010+1010+10
Scenario: Update a job name10 ms0010+1010+10
Scenario: Update a non existing device3 ms0055
Scenario: Update a nonexistent job4 ms0010+1010+10
Scenario: Update a nonexistent step definition11 ms0077
Scenario: Update a step definition name7 ms0077
Scenario: Update a step definition processor name4 ms0088
Scenario: Update a step definition target type5 ms0088
Scenario: Update existing role name9 ms0088
Scenario: Update job id of an existing execution item3 ms009+99+9
Scenario: Update schedule which doesn't exist6 ms0055
Scenario: Update scheduler end date10 ms0099
Scenario: Update scheduler name6 ms0088
Scenario: Update scheduler start date5 ms0088
Scenario: Update the end time of an existing execution item4 ms0010+1010+10
Scenario: Update trigger definition6 ms0088
Scenario: Update user10 ms0077
Scenario: Update user that doesn't exist3 ms0055
Scenario: User locking itself out by using out login attempts8 ms001616
Scenario: User locking itself out with failed attempts and not waiting to unlock8 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 failures8 ms001919
Scenario: User not locking itself out by using less than max failed login attempts7 ms001717
Scenario: Validate a device client based search with a null client ID3 ms0055
Scenario: Validate a device client based search with an empty client ID2 ms0055
Scenario: Validate a device client search with null scope3 ms0055
Scenario: Validate a device creator with a null client ID2 ms0066
Scenario: Validate a device creator with a null scope ID3 ms0066
Scenario: Validate a device query with a null Scope ID4 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 creator3 ms0055
Scenario: Validate a null device2 ms0055
Scenario: Validate a null device count2 ms0055
Scenario: Validate a null device query3 ms0055
Scenario: Validate a regular creator4 ms0044
Scenario: Validate a regular device client search4 ms0044
Scenario: Validate a regular device count3 ms0044
Scenario: Validate a regular device query3 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 ID4 ms0066
Scenario: Waiting For Lock Duration Time To Pass14 ms0019+1919+19
Scenario: Waiting For Reset After Login Counter To Pass8 ms0018+1818+18
empty) scope0 ms0044