Test Result : (root)

18 failures (+18) , 122 skipped (+122)
16,514 tests (+16058)
Took 23 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 description9 ms1
 Scenario: Creating unique Access Group with special symbols in description.Then I find the group with name "groupName53"9 ms1
 Scenario: Execute possible docker steps to show its usage.Given List images by name "kapua/kapua-broker:1.4.0-SNAPSHOT"3 ms1
 Scenario: Execute possible docker steps to show its usage.Scenario: Execute possible docker steps to show its usage5 ms1
 Scenario: Executing Job And Then Restarting Device.Scenario: Executing Job And Then Restarting Device4 ms1
 Scenario: Executing Job And Then Restarting Device.Then I find 4 device events3 ms1
 Scenario: Executing Job When Device Connected After The Specified Start Date And Time.And I confirm the executed job is finished64 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 Time66 ms1
 Scenario: Executing Job When Device Connected Before End Date And Time.And I confirm the executed job is finished4 ms1
 Scenario: Executing Job When Device Connected Before End Date And Time.Scenario: Executing Job When Device Connected Before End Date And Time6 ms1
 Scenario: List Endpoints Created From Sub-Account.And I create endpoint with schema "Schema1", domain "abc.com" and port 22222 ms1
 Scenario: List Endpoints Created From Sub-Account.Scenario: List Endpoints Created From Sub-Account3 ms1
 Scenario: List Endpoints From "kapua-sys" Account.Scenario: List Endpoints From "kapua-sys" Account2 ms1
 Scenario: List Endpoints From "kapua-sys" Account.Then I find 3 endpoints2 ms1
 Scenario: List Endpoints From Sub-Account Of Another Sub-Account.And I create endpoint with schema "Schema1", domain "abc.com" and port 222211 ms1
 Scenario: List Endpoints From Sub-Account Of Another Sub-Account.Scenario: List Endpoints From Sub-Account Of Another Sub-Account13 ms1
 Scenario: List Endpoints From Sub-account.And I create endpoint with schema "Schema1", domain "abc.com" and port 22222 ms1
 Scenario: List Endpoints From Sub-account.Scenario: List Endpoints From Sub-account4 ms1

All Tests

ClassDurationFail(diff)Skip(diff)Pass(diff)Total(diff)
Scenario: A fresh database must contain 1 default role in the root scope11 ms004+44+4
Scenario: A newly created account must have some metadata4 ms0033
Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic12 ms008+88+8
Scenario: Access info service sanity checks5 ms004+44+4
Scenario: Access service comparison sanity checks5 ms003+33+3
Scenario: Account based ClientInfo data check36 ms0024+2424+24
Scenario: Account exactly on its expiration date8 ms0014+1414+14
Scenario: Account name must not be mutable4 ms0066
Scenario: Account past its expiration date7 ms0014+1414+14
Scenario: Account wide metrics check19 ms0028+2828+28
Scenario: Account with future expiration date12 ms0013+1313+13
Scenario: Account with no expiration date13 ms0013+1313+13
Scenario: Add Access Info domain permissions to new user15 ms0026+2626+26
Scenario: Add Account permissions to the role in child account17 ms0028+2828+28
Scenario: Add Credential domain permissions to new user14 ms0018+1818+18
Scenario: Add Datastore domain permissions to new user0.33 sec0019+1919+19
Scenario: Add Device Connection domain permissions to kapua-sys user11 ms0011+1111+11
Scenario: Add Device Connection domain permissions to new user21 ms0023+2323+23
Scenario: Add Device Event domain permissions to new user11 ms0016+1616+16
Scenario: Add Device domain permissions to new user14 ms0017+1717+17
Scenario: Add Domain domain permissions to kapua-sys user21 ms0017+1717+17
Scenario: Add Domain domain permissions to new user14 ms0032+3232+32
Scenario: Add Endpoint Permission To The User23 ms0030+3030+30
Scenario: Add Endpoint_info permissions to the role in child account17 ms0030+3030+30
Scenario: Add Group domain permissions to new user23 ms0017+1717+17
Scenario: Add Group permissions to the role in child account19 ms0026+2626+26
Scenario: Add Job domain permissions to new user17 ms0019+1919+19
Scenario: Add Role domain permissions to new user20 ms0017+1717+17
Scenario: Add Role permissions to the role in child account19 ms0026+2626+26
Scenario: Add Scheduler Permissions With Job Permissions15 ms0031+3131+31
Scenario: Add Scheduler Permissions Without Job Permissions26 ms0021+2121+21
Scenario: Add Scheduler permissions to the role in child account11 ms0036+3636+36
Scenario: Add Tag domain permissions to new user13 ms0015+1515+15
Scenario: Add Tag permissions to the role in child account10 ms0026+2626+26
Scenario: Add User domain permissions to new user13 ms0020+2020+20
Scenario: Add account permissions to the role12 ms0019+1919+19
Scenario: Add admin role to the user36 ms0044+4444+44
Scenario: Add and delete Account permissions from the "admin" role12 ms0014+1414+14
Scenario: Add and delete Device permissions from the "admin" role11 ms0014+1414+14
Scenario: Add and delete Endpoint_info permissions from the "admin" role26 ms0014+1414+14
Scenario: Add and delete Group permissions from the "admin" role18 ms0014+1414+14
Scenario: Add and delete Job permissions from the "admin" role12 ms0014+1414+14
Scenario: Add and delete Role permissions from the "admin" role9 ms0014+1414+14
Scenario: Add and delete User permissions from the "admin" role14 ms0015+1515+15
Scenario: Add datastore permissions to the role10 ms0027+2727+27
Scenario: Add deleted role again22 ms0010+1010+10
Scenario: Add device event permissions to the role12 ms0032+3232+32
Scenario: Add device permissions to the role13 ms0019+1919+19
Scenario: Add device permissions to the role in child account16 ms0026+2626+26
Scenario: Add domain, user and access_info permissions to the role12 ms0023+2323+23
Scenario: Add endpoint_info permissions to the role21 ms0031+3131+31
Scenario: Add group permissions to the role9 ms0018+1818+18
Scenario: Add job permissions to the role15 ms0019+1919+19
Scenario: Add job permissions to the role in child account17 ms0026+2626+26
Scenario: Add role permissions to the role16 ms0019+1919+19
Scenario: Add same permission twice to the same role17 ms0014+1414+14
Scenario: Add same role to user twice10 ms0013+1313+13
Scenario: Add scheduler permissions to the role23 ms0031+3131+31
Scenario: Add tag permissions to the role21 ms0018+1818+18
Scenario: Add user permissions to the role21 ms0019+1919+19
Scenario: Add user permissions to the role in child account15 ms0026+2626+26
Scenario: Adding "Cron Job" Schedule With All Valid Parameters8 ms0010+1010+10
Scenario: Adding "Cron Job" Schedule With All Valid Parameters And Null Cron Value10 ms0010+1010+10
Scenario: Adding "Cron Job" Schedule With All Valid Parameters Except Cron Format8 ms0011+1111+11
Scenario: Adding "Cron Job" Schedule With End Date Only9 ms0010+1010+10
Scenario: Adding "Cron Job" Schedule With End Time before Start time11 ms0012+1212+12
Scenario: Adding "Cron Job" Schedule With Non-Unique End Date Parameter6 ms0016+1616+16
Scenario: Adding "Cron Job" Schedule With Non-Unique Start Date Parameter8 ms0015+1515+15
Scenario: Adding "Cron Job" Schedule With Start Date Only5 ms0011+1111+11
Scenario: Adding "Cron Job" Schedule With the same Start and End time10 ms0012+1212+12
Scenario: Adding "Cron Job" Schedule Without The Start Date Parameter12 ms0010+1010+10
Scenario: Adding "Device Connect" Schedule With All Valid Parameters17 ms008+88+8
Scenario: Adding "Device Connect" Schedule With End Date Only14 ms0010+1010+10
Scenario: Adding "Device Connect" Schedule With End Time before Start time8 ms0011+1111+11
Scenario: Adding "Device Connect" Schedule With Max Length Name7 ms008+88+8
Scenario: Adding "Device Connect" Schedule With Min Length Name10 ms008+88+8
Scenario: Adding "Device Connect" Schedule With Name Only7 ms009+99+9
Scenario: Adding "Device Connect" Schedule With Non-Unique End Date Parameter8 ms0013+1313+13
Scenario: Adding "Device Connect" Schedule With Non-Unique Name7 ms0013+1313+13
Scenario: Adding "Device Connect" Schedule With Non-Unique Start Date Parameter9 ms0011+1111+11
Scenario: Adding "Device Connect" Schedule With Start Date Only13 ms0010+1010+10
Scenario: Adding "Device Connect" Schedule With the same Start and End time7 ms0011+1111+11
Scenario: Adding "Device Connect" Schedule Without Name5 ms0010+1010+10
Scenario: Adding "Device Connect" Schedule Without The Start Date Parameter5 ms009+99+9
Scenario: Adding "Empty" Tag To Device5 ms005+55+5
Scenario: Adding "Interval Job" Schedule With All Valid Parameters7 ms0010+1010+10
Scenario: Adding "Interval Job" Schedule With End Date Only8 ms0010+1010+10
Scenario: Adding "Interval Job" Schedule With End Time before Start time4 ms0012+1212+12
Scenario: Adding "Interval Job" Schedule With Max Length Name14 ms0010+1010+10
Scenario: Adding "Interval Job" Schedule With Min Length Name13 ms0010+1010+10
Scenario: Adding "Interval Job" Schedule With Name Only5 ms0010+1010+10
Scenario: Adding "Interval Job" Schedule With Non-Unique End Date Parameter10 ms0016+1616+16
Scenario: Adding "Interval Job" Schedule With Non-Unique Name6 ms0015+1515+15
Scenario: Adding "Interval Job" Schedule With Non-Unique Start Date Parameter7 ms0015+1515+15
Scenario: Adding "Interval Job" Schedule With Null Interval Number6 ms0012+1212+12
Scenario: Adding "Interval Job" Schedule With Start Date Only6 ms0011+1111+11
Scenario: Adding "Interval Job" Schedule With the same Start and End time6 ms0012+1212+12
Scenario: Adding "Interval Job" Schedule Without Interval Number7 ms0011+1111+11
Scenario: Adding "Interval Job" Schedule Without The Start Date Parameter6 ms009+99+9
Scenario: Adding "Interval Job" Schedule Without a Name8 ms0011+1111+11
Scenario: Adding "admin" role to a user in a child account13 ms0014+1414+14
Scenario: Adding "admin" role to multiple users10 ms0018+1818+18
Scenario: Adding "admin" role twice10 ms0013+1313+13
Scenario: Adding Account:Delete permission to user in same scope15 ms0025+2525+25
Scenario: Adding Account:Delete permission to user in sub-account scope13 ms0030+3030+30
Scenario: Adding Account:Read and Account:Delete permissions to user in same scope12 ms0021+2121+21
Scenario: Adding Account:Read and Account:Write permissions to user in same scope15 ms0019+1919+19
Scenario: Adding Account:Read permission to user in same scope24 ms0023+2323+23
Scenario: Adding Account:Read permission to user in sub-account scope13 ms0029+2929+29
Scenario: Adding Account:Write and Account:Delete permission to user in same scope21 ms0023+2323+23
Scenario: Adding Account:Write permission to user in same scope9 ms0025+2525+25
Scenario: Adding Account:Write permission to user in sub-account scope10 ms0031+3131+31
Scenario: Adding Multiple Permissions To User14 ms0020+2020+20
Scenario: Adding One Permission To User21 ms0011+1111+11
Scenario: Adding Permissions To Child User12 ms0018+1818+18
Scenario: Adding Permissions To Parallel User15 ms0018+1818+18
Scenario: Adding Previously Deleted Permission23 ms0028+2828+28
Scenario: Adding Previously Deleted Tag From Device Again3 ms0011+1111+11
Scenario: Adding Regular Device to a Group With Description6 ms0010+1010+10
Scenario: Adding Regular Device to a Group Without a Description5 ms0012+1212+12
Scenario: Adding Regular Group Without Description to Device3 ms0010+1010+10
Scenario: Adding Regular Tag Without Description To Device6 ms006+66+6
Scenario: Adding Same Regular Group Without Description to Device6 ms0014+1414+14
Scenario: Adding Tag With Long Name Without Description To Device4 ms006+66+6
Scenario: Adding Tag With Numbers Without Description To Device4 ms006+66+6
Scenario: Adding Tag With Short Name Without Description To Device4 ms006+66+6
Scenario: Adding Tag With Special Symbols Without Description To Device4 ms006+66+6
Scenario: Adding all Account permissions to user in same scope11 ms0017+1717+17
Scenario: Adding all Account permissions to user in sub-account scope25 ms0024+2424+24
Scenario: Adding existing roles to user10 ms0015+1515+15
Scenario: Adding role from child account to user in new child account10 ms0015+1515+15
Scenario: Adding role to multiple users in child account18 ms0018+1818+18
Scenario: Adding same role twice to user in child account10 ms0015+1515+15
Scenario: Adding the same role to user twice in child account17 ms0013+1313+13
Scenario: All device parameters must match the device creator5 ms0033
Scenario: Assign 100 Devices to One Group9 ms0011+1111+11
Scenario: B1 Broker publish to CTRL_ACC_REPLY25 ms009+99+9
Scenario: B10 Broker create sub-topic on ACL_DATA_ACC is not allowed22 ms009+99+9
Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed12 ms008+88+8
Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI17 ms009+99+9
Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed15 ms009+99+9
Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed7 ms008+88+8
Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY29 ms009+99+9
Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY64 ms009+99+9
Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account11 ms009+99+9
Scenario: B5 Broker publish to CTRL_ACC is not allowed15 ms009+99+9
Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed11 ms009+99+9
Scenario: B7 Broker subscribe on CTRL_ACC is not allowed6 ms008+88+8
Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI6 ms009+99+9
Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed10 ms009+99+9
Scenario: Basic Device Event queries11 ms001010
Scenario: Birth and applications event handling8 ms0012+1212+12
Scenario: Birth and death message handling12 ms0012+1212+12
Scenario: Birth and missing event handling10 ms0012+1212+12
Scenario: Birth message handling from a new device8 ms0013+1313+13
Scenario: Birth message handling from an existing device12 ms0012+1212+12
Scenario: Both the parent and child accounts do not expire13 ms0011+1111+11
Scenario: Both the parent and child accounts have the same expiration date8 ms0011+1111+11
Scenario: Captured date based ClientInfo data check28 ms0030+3030+30
Scenario: Case sensitiveness of named device searches4 ms0044
Scenario: Change an existing step name10 ms0011+1111+11
Scenario: Change role name so it is too short3 ms006+66+6
Scenario: Change the account parent path3 ms0055
Scenario: Changing Client ID6 ms009+99+9
Scenario: Changing Description On Group With Long Description11 ms007+77+7
Scenario: Changing Description On Group With Long Name15 ms007+77+7
Scenario: Changing Description On Group With Numbers In Name7 ms0010+1010+10
Scenario: Changing Description On Group With Permitted Symbols8 ms007+77+7
Scenario: Changing Description On Group With Short Description13 ms007+77+7
Scenario: Changing Description On Group With Short Name10 ms007+77+7
Scenario: Changing Description On Tag With Long Description3 ms004+44+4
Scenario: Changing Description On Tag With Long Name4 ms005+55+5
Scenario: Changing Description On Tag With Numbers In Name3 ms006+66+6
Scenario: Changing Description On Tag With Permitted Symbols In Name3 ms004+44+4
Scenario: Changing Description On Tag With Short Description4 ms004+44+4
Scenario: Changing Description On Tag With Short Name3 ms004+44+4
Scenario: Changing Device Status To Disabled15 ms009+99+9
Scenario: Changing Device Status To Enabled5 ms009+99+9
Scenario: Changing Group's Description To Non-Uniqe One7 ms007+77+7
Scenario: Changing Group's Description To Uniqe One6 ms007+77+7
Scenario: Changing Group's Name To Contain Invalid Symbols In Name Without Changing Description7 ms008+88+8
Scenario: Changing Group's Name To Contain Permitted Symbols In Name Without Changing Description6 ms007+77+7
Scenario: Changing Group's Name To Non-Unique One6 ms009+99+9
Scenario: Changing Group's Name To Short One Without Changing Description8 ms007+77+7
Scenario: Changing Group's Name To Unique One6 ms007+77+7
Scenario: Changing Group's Name To a Long One Without Changing Description5 ms007+77+7
Scenario: Changing Group's Name To a Too Long One Without Changing Description3 ms008+88+8
Scenario: Changing Group's Name To a Too Short One Without Changing Description7 ms008+88+8
Scenario: Changing Tag's Description To Non-Unique One4 ms005+55+5
Scenario: Changing Tag's Description To Unique One4 ms007+77+7
Scenario: Changing Tag's Name To Contain Invalid Symbols In Name Without Description3 ms005+55+5
Scenario: Changing Tag's Name To Contain Permitted Symbols In Name Without Description4 ms005+55+5
Scenario: Changing Tag's Name To Non-Unique One7 ms006+66+6
Scenario: Changing Tag's Name To Short One Without Description5 ms007+77+7
Scenario: Changing Tag's Name To Unique One4 ms007+77+7
Scenario: Changing Tag's Name To a Long One Without Description4 ms007+77+7
Scenario: Changing Tag's Name To a Too Long One Without Description3 ms005+55+5
Scenario: Changing Tag's Name To a Too Short One Without Description5 ms005+55+5
Scenario: Changing description of a nonexisting role4 ms007+77+7
Scenario: Changing job description to non-unique one6 ms007+77+7
Scenario: Changing job description to the long one7 ms006+66+6
Scenario: Changing job description to unique one6 ms006+66+6
Scenario: Changing job description to very short one7 ms007+77+7
Scenario: Changing job name to a long one without description7 ms007+77+7
Scenario: Changing job name to a too long one without description8 ms005+55+5
Scenario: Changing job name to a too short one without description8 ms006+66+6
Scenario: Changing job name to contain invalid symbols in name without description6 ms004+44+4
Scenario: Changing job name to contain permitted symbols in name without description10 ms005+55+5
Scenario: Changing job name to non-unique one10 ms008+88+8
Scenario: Changing job name to short one without description9 ms007+77+7
Scenario: Changing job name to unique one10 ms009+99+9
Scenario: Changing name of a nonexisting role2 ms007+77+7
Scenario: Changing role description to a valid one2 ms006+66+6
Scenario: Changing role name so it is too long2 ms006+66+6
Scenario: Changing role name to contain special character3 ms004+44+4
Scenario: Changing role name to null2 ms006+66+6
Scenario: Changing role's name to a valid one3 ms006+66+6
Scenario: Channel info queries based on datastore channel filters29 ms0050+5050+50
Scenario: ChannelInfo client ID and topic data based on the client id26 ms0028+2828+28
Scenario: ChannelInfo client ID based on the account id21 ms0026+2626+26
Scenario: ChannelInfo last published date34 ms0030+3030+30
Scenario: ChannelInfo topic data based on the account id24 ms0026+2626+26
Scenario: Check account properties3 ms0044
Scenario: Check the Device Connection Domain data seetting3 ms0022
Scenario: Check the database cache coherency31 ms0030+3030+30
Scenario: Check the mapping for message semantic topics42 ms0030+3030+30
Scenario: Check the message store42 ms0020+2020+20
Scenario: Check the sanity of the Device Connection Domain data initialization3 ms0022
Scenario: Child account expires after parent10 ms009+99+9
Scenario: Child account expires before parent10 ms0011+1111+11
Scenario: Child account has null expiration date10 ms009+99+9
Scenario: Client Id based ClientInfo data check24 ms0028+2828+28
Scenario: Compare domain entries5 ms003+33+3
Scenario: Connect to the system and publish some data0.18 sec0022+2222+22
Scenario: Connection Service factory sanity checks2 ms0022
Scenario: Count access info entities in a specific scope17 ms0024+2424+24
Scenario: Count access role entities by scope6 ms0039+3939+39
Scenario: Count connections in empty scope3 ms0044
Scenario: Count connections in scope4 ms0055
Scenario: Count devices with a specific BIOS version3 ms0066
Scenario: Count domains in a blank database7 ms004+44+4
Scenario: Count domains in the database9 ms007+77+7
Scenario: Count events in empty scope9 ms0066
Scenario: Count groups4 ms0014+1414+14
Scenario: Count groups in a blank database6 ms005+55+5
Scenario: Count job items3 ms007+77+7
Scenario: Count job items in wrong - empty - scope12 ms008+88+8
Scenario: Count role permissions in specific scopes15 ms0018+1818+18
Scenario: Count roles in specific scopes7 ms0015+1515+15
Scenario: Count step definition items8 ms004+44+4
Scenario: Count step definitions in wrong (empty) scope14 ms001+11+1
Scenario: Count steps in the database6 ms0014+1414+14
Scenario: Count user8 ms006+66+6
Scenario: Counting created roles items in the DB3 ms005+55+5
Scenario: Create a regular event22 ms0088
Scenario: Create a single device with an empty string for clientID4 ms0044
Scenario: Create a single device with null clientID value4 ms0044
Scenario: Create a valid job entry49 ms006+66+6
Scenario: Create an event with a null scope ID8 ms0077
Scenario: Create and count several execution items for a job4 ms0011+1111+11
Scenario: Create index with specific prefix16 ms0012+1212+12
Scenario: Create multiple users3 ms005+55+5
Scenario: Create regular access permissions8 ms0020+2020+20
Scenario: Create same user in different accounts22 ms0015+1515+15
Scenario: Create scheduler with correct end date7 ms008+88+8
Scenario: Create scheduler with empty schedule name12 ms008+88+8
Scenario: Create scheduler with end date before start date11 ms009+99+9
Scenario: Create scheduler with invalid Retry Interval property10 ms009+99+9
Scenario: Create scheduler with invalid cron job trigger property7 ms009+99+9
Scenario: Create scheduler with invalid schedule name15 ms008+88+8
Scenario: Create scheduler with short schedule name11 ms008+88+8
Scenario: Create scheduler with too long schedule name8 ms008+88+8
Scenario: Create scheduler with valid Retry Interval property7 ms007+77+7
Scenario: Create scheduler with valid cron job trigger property10 ms007+77+7
Scenario: Create scheduler with valid schedule name29 ms006+66+6
Scenario: Create scheduler without Cron Job Trigger property8 ms009+99+9
Scenario: Create scheduler without Retry Interval property6 ms009+99+9
Scenario: Create scheduler without start date8 ms007+77+7
Scenario: Create some regular role permissions8 ms009+99+9
Scenario: Create user that already exist4 ms007+77+7
Scenario: Create user that has more than DB allowed length8 ms005+55+5
Scenario: Create user with short name11 ms005+55+5
Scenario: Create user with special characters in his name6 ms005+55+5
Scenario: Create with permissions5 ms0014+1414+14
Scenario: Create with permissions and a role4 ms0017+1717+17
Scenario: Create with permissions and a role in the wrong scope5 ms0015+1515+15
Scenario: Creating 100 Sub-accounts While InfiniteChildAccounts Is Set To True7 ms007+77+7
Scenario: Creating A Device With Disabled Status10 ms007+77+7
Scenario: Creating A Device With Enabled Status11 ms007+77+7
Scenario: Creating A Device With Long Display Name13 ms007+77+7
Scenario: Creating A Device With Long Name9 ms007+77+7
Scenario: Creating A Device With Name Containing Invalid Symbols15 ms008+88+8
Scenario: Creating A Device With Name Containing Permitted Symbols13 ms007+77+7
Scenario: Creating A Device With No Name6 ms008+88+8
Scenario: Creating A Device With Non-unique Display Name10 ms007+77+7
Scenario: Creating A Device With Non-unique Name16 ms0010+1010+10
Scenario: Creating A Device With Short Display Name10 ms007+77+7
Scenario: Creating A Device With Short Name10 ms007+77+7
Scenario: Creating A Device With Too Long Display Name6 ms008+88+8
Scenario: Creating A Device With Too Long Name8 ms008+88+8
Scenario: Creating A Device With Unique Name11 ms009+99+9
Scenario: Creating A Valid Account7 ms005+55+5
Scenario: Creating An Account With Long Name11 ms005+55+5
Scenario: Creating An Account With Long Organization Name7 ms005+55+5
Scenario: Creating An Account With Non-unique Name8 ms008+88+8
Scenario: Creating An Account With Numbers And Valid Symbols In Name10 ms005+55+5
Scenario: Creating An Account With Short Name7 ms005+55+5
Scenario: Creating An Account With Short Organization Name7 ms005+55+5
Scenario: Creating An Account With Special Symbols In Organization Name8 ms005+55+5
Scenario: Creating An Account With Too Long Organization Name4 ms006+66+6
Scenario: Creating An Account With Unique Name8 ms007+77+7
Scenario: Creating An Account With Wrong TLD Format In Email8 ms0010+1010+10
Scenario: Creating An Account Without Email12 ms006+66+6
Scenario: Creating An Account Without Name10 ms006+66+6
Scenario: Creating An Account Without Ogranization Name5 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 Devices13 ms0012+1212+12
Scenario: Creating Devices And Then Changing Device Service Values10 ms0010+1010+10
Scenario: Creating Devices Under Account That Allows Infinite Child Devices7 ms0010+1010+10
Scenario: Creating Devices Under Account That Does Not Allow Devices12 ms009+99+9
Scenario: Creating Devices Under Account That Has Limited Child Devices7 ms0013+1313+13
Scenario: Creating Endpoint Non-Unique "Domain Name"4 ms008+88+8
Scenario: Creating Endpoint Non-Unique "Port"14 ms008+88+8
Scenario: Creating Endpoint Non-Unique "Schema"6 ms009+99+9
Scenario: Creating Endpoint With "Domain Name" Only4 ms006+66+6
Scenario: Creating Endpoint With "Port" Only13 ms006+66+6
Scenario: Creating Endpoint With "Schema" Only5 ms006+66+6
Scenario: Creating Endpoint With Disabled Secure Field5 ms006+66+6
Scenario: Creating Endpoint With Enabled Secure Field11 ms006+66+6
Scenario: Creating Endpoint With Invalid "Domain Name"5 ms006+66+6
Scenario: Creating Endpoint With Invalid "Schema" containing symbols5 ms006+66+6
Scenario: Creating Endpoint With Long "Domain Name"4 ms005+55+5
Scenario: Creating Endpoint With Max Length "Port"10 ms005+55+5
Scenario: Creating Endpoint With NULL parameters2 ms006+66+6
Scenario: Creating Endpoint With Schema Containing "http://"7 ms006+66+6
Scenario: Creating Endpoint With Schema Containing "https://"4 ms006+66+6
Scenario: Creating Endpoint With Short "Domain Name"4 ms006+66+6
Scenario: Creating Endpoint With Short "Schema"10 ms006+66+6
Scenario: Creating Endpoint With Small Number "Port"15 ms006+66+6
Scenario: Creating Endpoint With Too Big "Port"7 ms006+66+6
Scenario: Creating Endpoint With Too Long "Domain Name"5 ms006+66+6
Scenario: Creating Endpoint With Too Long "Schema"3 ms006+66+6
Scenario: Creating Endpoint Without "Domain Name"14 ms006+66+6
Scenario: Creating Endpoint Without "Port"4 ms006+66+6
Scenario: Creating Endpoint Without "Schema"4 ms006+66+6
Scenario: Creating Endpoint Without Long "Schema"4 ms005+55+5
Scenario: Creating Endpoint with invalid "Schema" which contains only numbers6 ms006+66+6
Scenario: Creating Group Invalid Symbols In Name Without Description3 ms007+77+7
Scenario: Creating Group With Invalid Symbols In Name With Valid Description17 ms007+77+7
Scenario: Creating Group With Long Name With Valid Description5 ms006+66+6
Scenario: Creating Group With Long Name Without Description4 ms006+66+6
Scenario: Creating Group With Numbers In Name With Valid Description5 ms008+88+8
Scenario: Creating Group With Permitted Symbols And Numbers In Name Without Description16 ms006+66+6
Scenario: Creating Group With Permitted Symbols In Name With Valid Description6 ms006+66+6
Scenario: Creating Group With Short Name With Valid Description5 ms006+66+6
Scenario: Creating Group With Short Name Without Description8 ms006+66+6
Scenario: Creating Group With Too Long Name With Valid Description5 ms007+77+7
Scenario: Creating Group With Too Long Name Without Description17 ms007+77+7
Scenario: Creating Group With Too Short Name With Valid Description6 ms007+77+7
Scenario: Creating Group With Too Short Name Without Description6 ms007+77+7
Scenario: Creating Group Without a Name And With Valid Description14 ms007+77+7
Scenario: Creating Group Without a Name And Without Description7 ms007+77+7
Scenario: Creating Groups And Than Setting Group Service So It Does Not Allow Groups4 ms0011+1111+11
Scenario: Creating Groups And Then Changing InfiniteChildGroups To False And Set MaxNumberChildGroups12 ms0010+1010+10
Scenario: Creating Groups Under Account That Allows Infinite Child Groups7 ms009+99+9
Scenario: Creating Groups Under Account That Does Not Allow Groups10 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 Jobs10 ms0012+1212+12
Scenario: Creating Jobs And Then Changing Job Service Values10 ms0010+1010+10
Scenario: Creating Jobs Under Account That Allows Infinite Child Devices7 ms0010+1010+10
Scenario: Creating Jobs Under Account That Does Not Allow Jobs9 ms009+99+9
Scenario: Creating Jobs Under Account That Has Limited Child Jobs6 ms0013+1313+13
Scenario: Creating Non-Unique Group With Valid Description5 ms008+88+8
Scenario: Creating Non-Unique Tag With Valid Description4 ms005+55+5
Scenario: Creating Non-unique Group Without Description6 ms008+88+8
Scenario: Creating Non-unique Tag Without Description11 ms004+44+4
Scenario: Creating Roles And Than Setting Role Service So It Does Not Allow Roles8 ms0011+1111+11
Scenario: Creating Roles And Then Changing Role Service Values7 ms0010+1010+10
Scenario: Creating Roles Under Account That Allows Infinite Child Roles7 ms0010+1010+10
Scenario: Creating Roles Under Account That Does Not Allow Roles10 ms009+99+9
Scenario: Creating Roles Under Account That Has Limited Child Roles7 ms0012+1212+12
Scenario: Creating Sub-accounts When InfiniteChildAccoounts Is Set To False And maxNumberChildAccounts Is Set6 ms0013+1313+13
Scenario: Creating Sub-accounts When InfiniteChildAccoounts Is Set To True And maxNumberChildAccounts Is Set7 ms0014+1414+14
Scenario: Creating Sub-accounts When InfiniteChildAccounts Is Set To False8 ms009+99+9
Scenario: Creating Sub-accounts when InfiniteChildAccounts Is Set To True10 ms0012+1212+12
Scenario: Creating Tag With Invalid Symbols In Name With Valid Description4 ms004+44+4
Scenario: Creating Tag With Invalid Symbols In Name Without Description4 ms004+44+4
Scenario: Creating Tag With Long Name With Valid Description4 ms004+44+4
Scenario: Creating Tag With Long Name Without Description8 ms004+44+4
Scenario: Creating Tag With Numbers In Name With Valid Description3 ms004+44+4
Scenario: Creating Tag With Numbers In Name Without Description5 ms004+44+4
Scenario: Creating Tag With Permitted Symbols In Name With Valid Description4 ms004+44+4
Scenario: Creating Tag With Permitted Symbols In Name Without Description7 ms004+44+4
Scenario: Creating Tag With Short Name With Valid Description7 ms004+44+4
Scenario: Creating Tag With Short Name Without Description7 ms004+44+4
Scenario: Creating Tag With Too Long Name With Valid Description3 ms004+44+4
Scenario: Creating Tag With Too Long Name Without Description6 ms004+44+4
Scenario: Creating Tag With Too Short Name With Valid Description5 ms004+44+4
Scenario: Creating Tag With Too Short Name Without Description6 ms004+44+4
Scenario: Creating Tag Without a Name And With Valid Description4 ms004+44+4
Scenario: Creating Tag Without a Name And Without Description5 ms004+44+4
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 Values13 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 Tags12 ms009+99+9
Scenario: Creating Tags Under Account That Has Limited Child Tags11 ms0012+1212+12
Scenario: Creating Unique Group With Long Description14 ms006+66+6
Scenario: Creating Unique Group With Non-unique Description7 ms007+77+7
Scenario: Creating Unique Group With Short Description4 ms006+66+6
Scenario: Creating Unique Group With Unique Description14 ms006+66+6
Scenario: Creating Unique Group Without Description7 ms006+66+6
Scenario: Creating Unique Tag With Long Description4 ms004+44+4
Scenario: Creating Unique Tag With Non-unique Description4 ms005+55+5
Scenario: Creating Unique Tag With Short Description3 ms004+44+4
Scenario: Creating Unique Tag With Unique Description4 ms004+44+4
Scenario: Creating Unique Tag Without Description27 ms004+44+4
Scenario: Creating Users And Than Setting User Service So It Does Not Allow Users7 ms0011+1111+11
Scenario: Creating Users And Then Changing User Service Values13 ms0010+1010+10
Scenario: Creating Users Under Account That Allows Infinite Child Users11 ms0010+1010+10
Scenario: Creating Users Under Account That Does Not Allow Users10 ms009+99+9
Scenario: Creating Users Under Account That Has Limited Child Users10 ms0012+1212+12
Scenario: Creating Valid Endpoint4 ms006+66+6
Scenario: Creating a Access Group with invalid special symbols in name0 ms004+44+4
Scenario: Creating a Device With Permitted Symbols in its Display Name15 ms007+77+7
Scenario: Creating a Device With Unique Display Name8 ms008+88+8
Scenario: Creating a job with name only16 ms006+66+6
Scenario: Creating a job with null name26 ms005+55+5
Scenario: Creating a job without name with valid description3 ms005+55+5
Scenario: Creating a new PASSWORD Credential meeting a custom length requirement5 ms004+44+4
Scenario: Creating a new PASSWORD Credential meeting the standard length requirement28 ms003+33+3
Scenario: Creating a new PASSWORD Credential not meeting a custom length requirement9 ms005+55+5
Scenario: Creating a new PASSWORD Credential not meeting the standard length requirement12 ms004+44+4
Scenario: Creating a role name with allowed symbols in its name3 ms005+55+5
Scenario: Creating a role with 255 characters long description3 ms005+55+5
Scenario: Creating a role with a name and description that contain digits only3 ms005+55+5
Scenario: Creating a role with forbidden symbols in its name0 ms004+44+4
Scenario: Creating a role with name only3 ms005+55+5
Scenario: Creating a role with null name3 ms005+55+5
Scenario: Creating a role with regular name and very short description" as description cannot be too short, as even one character is enough3 ms005+55+5
Scenario: Creating a role with special characters in the description4 ms004+44+4
Scenario: Creating a role with the name that contains digits5 ms005+55+5
Scenario: Creating a role with too long name1 ms005+55+5
Scenario: Creating a role with too short name3 ms005+55+5
Scenario: Creating a role with valid name and with too long description6 ms003+33+3
Scenario: Creating a role wtih 255 characters long name3 ms005+55+5
Scenario: Creating a single device with case sensitive clientID4 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 characters3 ms0044
Scenario: Creating a single device with spaces in clientID6 ms0055
Scenario: Creating a single device with valid clientID5 ms0055
Scenario: Creating a valid Access Group with numbers in name4 ms005+55+5
Scenario: Creating a valid Access Group with only numbers in name5 ms005+55+5
Scenario: Creating a valid Access Group with unique name7 ms005+55+5
Scenario: Creating a valid Access Group with valid special symbols in name3 ms005+55+5
Scenario: Creating a valid role5 ms005+55+5
Scenario: Creating an Access Group with empty name5 ms004+44+4
Scenario: Creating an Access Group with long name4 ms005+55+5
Scenario: Creating an Access Group with short name8 ms005+55+5
Scenario: Creating an Access Group with too long name6 ms004+44+4
Scenario: Creating an Access Group with too short name4 ms004+44+4
Scenario: Creating an Access Group without name and with description2 ms004+44+4
Scenario: Creating and Deleting Endpoint Two Times19 ms0025+2525+25
Scenario: Creating index with regular user18 ms0025+2525+25
Scenario: Creating job with invalid symbols in name without description0 ms004+44+4
Scenario: Creating job with long name and valid description8 ms006+66+6
Scenario: Creating job with long name without description10 ms006+66+6
Scenario: Creating job with numbers in name and valid description6 ms006+66+6
Scenario: Creating job with numbers in name without description7 ms006+66+6
Scenario: Creating job with permitted symbols in name without description7 ms003+33+3
Scenario: Creating job with short name and valid job description13 ms006+66+6
Scenario: Creating job with short name without description16 ms006+66+6
Scenario: Creating job with too long name and valid description5 ms005+55+5
Scenario: Creating job with too long name without description9 ms005+55+5
Scenario: Creating job with too short name and valid description9 ms005+55+5
Scenario: Creating job with too short name without description15 ms005+55+5
Scenario: Creating job without name and without description6 ms005+55+5
Scenario: Creating new device and tagging it with specific Tag10 ms0014+1414+14
Scenario: Creating new device, tagging it with specific Tag and then deleting this Tag8 ms0016+1616+16
Scenario: Creating non-unique Access Group5 ms005+55+5
Scenario: Creating non-unique Access Group with unique description3 ms005+55+5
Scenario: Creating non-unique job name with valid job description6 ms007+77+7
Scenario: Creating two device with the same clientID8 ms0055
Scenario: Creating two indexes with daily index20 ms0017+1717+17
Scenario: Creating two indexes with hourly index20 ms0017+1717+17
Scenario: Creating two indexes with weekly index18 ms0017+1717+17
Scenario: Creating two roles with the same description3 ms006+66+6
Scenario: Creating two roles with the same name3 ms007+77+7
Scenario: Creating unique Access Group with long description4 ms005+55+5
Scenario: Creating unique Access Group with non-unique description3 ms006+66+6
Scenario: Creating unique Access Group with numbers in description4 ms005+55+5
Scenario: Creating unique Access Group with only numbers in description10 ms005+55+5
Scenario: Creating unique Access Group with short description4 ms005+55+5
Scenario: Creating unique Access Group with special symbols in description18 ms2+21+11+14+4
Scenario: Creating unique Access Group with unique description4 ms005+55+5
Scenario: Creating unique job with long description7 ms006+66+6
Scenario: Creating unique job with non-unique description7 ms0010+1010+10
Scenario: Creating unique job with short description7 ms006+66+6
Scenario: Creating user15 ms005+55+5
Scenario: Creation of access role with neither acess info and role entities9 ms0012+1212+12
Scenario: Creation of access role without an acess info entity16 ms0012+1212+12
Scenario: D1 Device publish to CTRL_ACC_REPLY13 ms009+99+9
Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI15 ms009+99+9
Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed17 ms009+99+9
Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed19 ms007+77+7
Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY16 ms009+99+9
Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY11 ms009+99+9
Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account10 ms009+99+9
Scenario: D5 Device subscribe - publish - admin on CTRL_ACC15 ms009+99+9
Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI11 ms009+99+9
Scenario: D7 Device publish to ACL_DATA_ACC is not allowed7 ms009+99+9
Scenario: D8 Device create sub-topic on ACL_DATA_ACC is not allowed18 ms009+99+9
Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed15 ms008+88+8
Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed19 ms009+99+9
Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI11 ms009+99+9
Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed20 ms009+99+9
Scenario: DM13 Data manage subscribe on ACL_CTRL_ACC_NOTIFY is not allowed9 ms008+88+8
Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY19 ms009+99+9
Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY24 ms009+99+9
Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account6 ms009+99+9
Scenario: DM5 Data manage publish to CTRL_ACC is not allowed19 ms009+99+9
Scenario: DM6 Data manage create sub-topic on CTRL_ACC is not allowed14 ms009+99+9
Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed6 ms008+88+8
Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI20 ms009+99+9
Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC13 ms009+99+9
Scenario: DV1 Data view publish to CTRL_ACC_REPLY17 ms009+99+9
Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed21 ms009+99+9
Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed4 ms0010+1010+10
Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed19 ms009+99+9
Scenario: DV13 Data view create sub-topic on ACL_CTRL_ACC_CLI is not allowed18 ms009+99+9
Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed16 ms009+99+9
Scenario: DV17 Data view subscribe on ACL_CTRL_ACC_NOTIFY is not allowed11 ms008+88+8
Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY13 ms009+99+9
Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY14 ms009+99+9
Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account6 ms009+99+9
Scenario: DV5 Data view publish to CTRL_ACC is not allowed17 ms009+99+9
Scenario: DV6 Data view create sub-topic on CTRL_ACC is not allowed28 ms009+99+9
Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed8 ms008+88+8
Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI17 ms009+99+9
Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed16 ms009+99+9
Scenario: Decreasing MaxNumberChildAccounts When Sub-accounts Are Already Created8 ms0015+1515+15
Scenario: Delete Kapua system user4 ms005+55+5
Scenario: Delete a access info entity with permissions and roles6 ms0017+1717+17
Scenario: Delete a connection from the database5 ms0088
Scenario: Delete a group from the database5 ms0010+1010+10
Scenario: Delete a group from the database - Unknown group ID4 ms006+66+6
Scenario: Delete a job3 ms0011+1111+11
Scenario: Delete a job execution item3 ms008+88+8
Scenario: Delete a job execution item twice3 ms009+99+9
Scenario: Delete a job twice9 ms0010+1010+10
Scenario: Delete a non existent event10 ms0077
Scenario: Delete a non existing connection3 ms0077
Scenario: Delete a non existing permission entity7 ms0016+1616+16
Scenario: Delete a non existing role entry5 ms0011+1111+11
Scenario: Delete a non-existing step5 ms0012+1212+12
Scenario: Delete a nonexistent domain8 ms005+55+5
Scenario: Delete a step definition11 ms008+88+8
Scenario: Delete a step definition twice6 ms007+77+7
Scenario: Delete access role from user9 ms0012+1212+12
Scenario: Delete an access info entity twice9 ms0011+1111+11
Scenario: Delete an access info entity using the wrong scope ID19 ms0011+1111+11
Scenario: Delete an existing access info entity6 ms0012+1212+12
Scenario: Delete an existing access permission entity19 ms0015+1515+15
Scenario: Delete an existing access role entry7 ms0022+2222+22
Scenario: Delete an existing account5 ms0055
Scenario: Delete an existing device from the registry3 ms0044
Scenario: Delete an existing event6 ms0099
Scenario: Delete an existing role5 ms0010+1010+10
Scenario: Delete an existing role twice6 ms0016+1616+16
Scenario: Delete an existing step3 ms0011+1111+11
Scenario: Delete items based on query results46 ms0084+8484+84
Scenario: Delete items by date ranges1.3 sec00132+132132+132
Scenario: Delete items by the datastore ID46 ms0066+6666+66
Scenario: Delete middle child expiration8 ms0015+1515+15
Scenario: Delete nonexisting account3 ms0044
Scenario: Delete nonexisting role permission13 ms0013+1313+13
Scenario: Delete parent expiration7 ms0014+1414+14
Scenario: Delete permissions from role11 ms0018+1818+18
Scenario: Delete role permissions13 ms0010+1010+10
Scenario: Delete scheduler7 ms008+88+8
Scenario: Delete scheduler which doesn't exist6 ms005+55+5
Scenario: Delete the Kapua system account3 ms0055
Scenario: Delete the last created domain entry5 ms008+88+8
Scenario: Delete user7 ms006+66+6
Scenario: Delete user that doesn't exist4 ms005+55+5
Scenario: Deleting "Cron Schedule" Triggering8 ms0013+1313+13
Scenario: Deleting "Device Schedule" Triggering6 ms0011+1111+11
Scenario: Deleting "Interval Schedule" Triggering12 ms0013+1313+13
Scenario: Deleting Device With Disabled Status6 ms0010+1010+10
Scenario: Deleting Device With Enabled Status14 ms0010+1010+10
Scenario: Deleting Endpoint Domain Name And Leaving it Empty4 ms008+88+8
Scenario: Deleting Endpoint Which Does Not Exist7 ms006+66+6
Scenario: Deleting Existing Group6 ms008+88+8
Scenario: Deleting Existing Group And Creating It Again With Same Name5 ms0012+1212+12
Scenario: Deleting Existing Tag And Creating It Again With Same Name4 ms007+77+7
Scenario: Deleting Group's Name And Leaving It Empty Without Changing Description10 ms008+88+8
Scenario: Deleting Non-Existent Tag3 ms007+77+7
Scenario: Deleting Tag From Device5 ms008+88+8
Scenario: Deleting Tag's Name And Leaving It Empty Without Description3 ms005+55+5
Scenario: Deleting Unexisitng Group15 ms0011+1111+11
Scenario: Deleting a Permission11 ms0021+2121+21
Scenario: Deleting a non-existing Access Group3 ms006+66+6
Scenario: Deleting a role twice3 ms007+77+7
Scenario: Deleting admin role11 ms007+77+7
Scenario: Deleting an existing Access Group3 ms005+55+5
Scenario: Deleting an existing Access Group and creating it again with the same name5 ms007+77+7
Scenario: Deleting an existing role4 ms006+66+6
Scenario: Deleting default permissions from admin role10 ms0012+1212+12
Scenario: Deleting existing tag4 ms009+99+9
Scenario: Deleting role after adding it to user15 ms0014+1414+14
Scenario: Deleting role after it has been added to user in child account14 ms0016+1616+16
Scenario: Deleting user in account that is higher in hierarchy22 ms0023+2323+23
Scenario: Deleting user in account that is lower in hierarchy22 ms0024+2424+24
Scenario: Device connection update4 ms0077
Scenario: Device factory sanity checks2 ms0022
Scenario: Device queries6 ms001010
Scenario: Device query - find by BIOS version4 ms0077
Scenario: Domain entry query7 ms005+55+5
Scenario: Domain with null actions4 ms005+55+5
Scenario: Domain with null name6 ms005+55+5
Scenario: Domains with duplicate names6 ms008+88+8
Scenario: Duplicate group name in root scope6 ms0010+1010+10
Scenario: Duplicate role names7 ms007+77+7
Scenario: Editing Access Group description to description with numbers3 ms005+55+5
Scenario: Editing Access Group description to description with only numbers4 ms005+55+5
Scenario: Editing Access Group description to description with special symbols3 ms004+44+4
Scenario: Editing Access Group description to long description3 ms005+55+5
Scenario: Editing Access Group description to non-unique one3 ms005+55+5
Scenario: Editing Access Group description to short description4 ms005+55+5
Scenario: Editing Access Group description to unique one6 ms007+77+7
Scenario: Editing Access Group name to a long one4 ms007+77+7
Scenario: Editing Access Group name to a too long one3 ms005+55+5
Scenario: Editing Access Group name to empty name5 ms005+55+5
Scenario: Editing Access Group name to name that contains numbers3 ms007+77+7
Scenario: Editing Access Group name to name that contains only numbers3 ms007+77+7
Scenario: Editing Access Group name to name with invalid special symbols in name0 ms005+55+5
Scenario: Editing Access Group name to name with valid special symbols3 ms007+77+7
Scenario: Editing Access Group name to non-unique one4 ms006+66+6
Scenario: Editing Access Group name to short one3 ms007+77+7
Scenario: Editing Access Group name to too short one4 ms005+55+5
Scenario: Editing Access Group name to valid one4 ms007+77+7
Scenario: Editing Endpoint Domain Name So It Contains Invalid Symbols4 ms008+88+8
Scenario: Editing Endpoint Domain Name So It Contains Only Numbers4 ms008+88+8
Scenario: Editing Endpoint Domain Name So It Has Max Value4 ms007+77+7
Scenario: Editing Endpoint Domain Name So It Has Min Value6 ms007+77+7
Scenario: Editing Endpoint Domain Name To Non-unique Value13 ms009+99+9
Scenario: Editing Endpoint Domain Name To Unique Value4 ms007+77+7
Scenario: Editing Endpoint Port To Non-unique Value6 ms009+99+9
Scenario: Editing Endpoint Port To Unique Value7 ms007+77+7
Scenario: Editing Endpoint Schema And Leaving It Empty5 ms008+88+8
Scenario: Editing Endpoint Schema So It Contains "http://"3 ms008+88+8
Scenario: Editing Endpoint Schema So It Contains "https://"5 ms008+88+8
Scenario: Editing Endpoint Schema So It Contains Invalid Symbols22 ms008+88+8
Scenario: Editing Endpoint Schema So It Contains Only Numbers11 ms008+88+8
Scenario: Editing Endpoint Schema So It Has Max Length6 ms007+77+7
Scenario: Editing Endpoint Schema So It Has Min Length5 ms007+77+7
Scenario: Editing Endpoint Schema To Non-unique Value10 ms008+88+8
Scenario: Editing Endpoint Schema To Unique Value14 ms007+77+7
Scenario: Editing Endpoint Secure Field To Non-unique Value5 ms009+99+9
Scenario: Editing Endpoint Secure Field To Unique Value4 ms007+77+7
Scenario: Editing Endpoint To NULL Values4 ms0014+1414+14
Scenario: Editing Endpoint To Non-unique Endpoint5 ms0010+1010+10
Scenario: Editing Group's Name To Contain Numbers Without Changing Description8 ms007+77+7
Scenario: Editing Tag's Name To Contain Numbers Without Description7 ms007+77+7
Scenario: Empty query results are supported6 ms008+88+8
Scenario: Event factory sanity checks3 ms0022
Scenario: Event service domain check4 ms0022
Scenario: Every account must have the default configuration items5 ms0033
Scenario: Execute possible docker steps to show its usage7 ms2+231+31033+33
Scenario: Executing Job And Then Restarting Device7 ms2+216+1627+2745+45
Scenario: Executing Job When Device Connected After End Date And Time34 ms0038+3838+38
Scenario: Executing Job When Device Connected After The Specified Start Date And Time0.13 sec2+26+630+3038+38
Scenario: Executing Job When Device Connected Before End Date And Time17 ms2+26+631+3139+39
Scenario: Executing Job When Device Connected Before The Specified Start Date And Time26 ms0037+3737+37
Scenario: Executing Job Without Steps25 ms0040+4040+40
Scenario: Extra long continuous test with multiple subscenarios with LOOSE default connection mode37 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 devices26 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 ms009+99+9
Scenario: Find a non existing event9 ms0066
Scenario: Find account by Id4 ms0044
Scenario: Find account by Ids5 ms0044
Scenario: Find account by name4 ms0044
Scenario: Find account by random Id5 ms0033
Scenario: Find all child accounts8 ms0033
Scenario: Find an access info entity7 ms0011+1111+11
Scenario: Find an access info entity by user ID6 ms0010+1010+10
Scenario: Find an event by its ID7 ms0066
Scenario: Find an existing access role entity6 ms0013+1313+13
Scenario: Find by name nonexisting account5 ms0033
Scenario: Find correct number of messages by corresponding metric0.54 sec0058+5858+58
Scenario: Find device by client ID4 ms0033
Scenario: Find device by registry ID4 ms0044
Scenario: Find last created permission16 ms0012+1212+12
Scenario: Find multiple users4 ms005+55+5
Scenario: Find role by ID7 ms007+77+7
Scenario: Find self account by id9 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 ms005+55+5
Scenario: Find user by id9 ms005+55+5
Scenario: Find user by its email3 ms006+66+6
Scenario: Find user by its phone number4 ms006+66+6
Scenario: Find user by name9 ms005+55+5
Scenario: Find user by name that doesn't exist5 ms003+33+3
Scenario: Find user with id and scope id that doesn't exist3 ms003+33+3
Scenario: Finding all messages by selecting all metrics0.43 sec0040+4040+40
Scenario: Finding correct number of messages by corresponding two metrics3.3 sec0052+5252+52
Scenario: Finding messages with incorrect metric parameters0.6 sec0072+7272+72
Scenario: Finding user by expiration date in the future5 ms005+55+5
Scenario: Finding user by expiration date in the past3 ms006+66+6
Scenario: Finding user by expiration date in the present6 ms006+66+6
Scenario: Generic connection query3 ms0088
Scenario: Get metadata3 ms003+33+3
Scenario: Group with a null name13 ms007+77+7
Scenario: Handle account creation21 ms0033
Scenario: Handle duplicate account names6 ms0055
Scenario: Handle null account name7 ms0044
Scenario: Handling of 2 birth messages12 ms0012+1212+12
Scenario: Handling of a disconnect message from a non existing device14 ms0010+1010+10
Scenario: Have Two Devices in The Same Group Without Description5 ms0013+1313+13
Scenario: I try to find a non-existing connection4 ms0066
Scenario: If user credential expiration date is before today, user can not login9 ms0014+1414+14
Scenario: If user credential expiration date is today, user can not login it is day inclusive7 ms0014+1414+14
Scenario: If user credential expiration date is tomorrow, user can login2 ms0013+1313+13
Scenario: If user credential is in state disabled, user can not login8 ms0014+1414+14
Scenario: If user credential is in state enabled, user can login5 ms0013+1313+13
Scenario: If user expiration date is before today, user can not login4 ms0013+1313+13
Scenario: If user expiration date is today, user can not login because expiration date was reached8 ms0013+1313+13
Scenario: If user expiration date is tomorrow, user can login4 ms0012+1212+12
Scenario: Init Security Context for all scenarios0.19 sec0048+4848+48
Scenario: Installing a package25 ms0013+1313+13
Scenario: Interval Job" Schedule With Too Long Name14 ms0011+1111+11
Scenario: It must be possible to query for specific entries in the role database14 ms008+88+8
Scenario: It should not be possible to change the configuration items4 ms0055
Scenario: Job execution factory sanity checks4 ms002+22+2
Scenario: Job factory sanity checks3 ms003+33+3
Scenario: Job with a duplicate name3 ms009+99+9
Scenario: Job with a null name9 ms008+88+8
Scenario: Job with a null scope ID9 ms009+99+9
Scenario: Job with an empty name11 ms008+88+8
Scenario: List Endpoints Created From Sub-Account5 ms2+223+231+126+26
Scenario: List Endpoints From "kapua-sys" Account4 ms2+24+45+511+11
Scenario: List Endpoints From Sub-Account Of Another Sub-Account24 ms2+223+231+126+26
Scenario: List Endpoints From Sub-account6 ms2+212+121+115+15
Scenario: MetricsInfo client ID and topic data based on the client id37 ms0034+3434+34
Scenario: MetricsInfo last published date22 ms0048+4848+48
Scenario: Modify a role that was deleted6 ms009+99+9
Scenario: Modify an existing account4 ms0044
Scenario: Modify last child expiration so that it still expires before parent13 ms0014+1414+14
Scenario: Modify middle child expiration so that it still expires before parent6 ms0014+1414+14
Scenario: Modify middle child expiration to outlive parent7 ms0015+1515+15
Scenario: Modify nonexisting account7 ms0066
Scenario: Modify parent expiration so that it still expires after child15 ms0014+1414+14
Scenario: Modify parent expiration to before child expiration9 ms0015+1515+15
Scenario: Modifying Sub-account of a different parent account17 ms0025+2525+25
Scenario: Moving Device From One Group With Description to Another7 ms0014+1414+14
Scenario: Nameless role entry6 ms007+77+7
Scenario: Negative scenario when client connects twice with same client id26 ms0011+1111+11
Scenario: New connection with reserved ID19 ms0034+3434+34
Scenario: Permission factory sanity checks5 ms003+33+3
Scenario: Positive scenario without stealing link27 ms0012+1212+12
Scenario: Query based on message ordering37 ms0020+2020+20
Scenario: Query based on metrics ordering36 ms0020+2020+20
Scenario: Query before schema search21 ms0082+8282+82
Scenario: Query for a specific group by name5 ms0016+1616+16
Scenario: Query for all the access info entities of a specific user7 ms0018+1818+18
Scenario: Query for all the access info entities of an invalid user5 ms0010+1010+10
Scenario: Query for executions of a specific job3 ms0018+1818+18
Scenario: Query for jobs with specified name5 ms009+99+9
Scenario: Query for step definitions8 ms007+77+7
Scenario: Query user4 ms006+66+6
Scenario: Querying Other Items With All Account Permissions11 ms0039+3939+39
Scenario: Regular connection7 ms0077
Scenario: Regular creation of Access Role entity8 ms0014+1414+14
Scenario: Regular domain6 ms005+55+5
Scenario: Regular group in random scope7 ms007+77+7
Scenario: Regular group in root scope7 ms007+77+7
Scenario: Regular job creation6 ms0010+1010+10
Scenario: Regular job execution creation3 ms007+77+7
Scenario: Regular role creation6 ms009+99+9
Scenario: Regular step creation6 ms0011+1111+11
Scenario: Regular step definition creation7 ms007+77+7
Scenario: Regular step definition with a property list7 ms004+44+4
Scenario: Reset Security Context for all scenarios0.16 sec0048+4848+48
Scenario: Restarting a job with Asset Write and Bundle Start steps25 ms0028+2828+28
Scenario: Restarting a job with Command Execution and Bundle Start steps29 ms0028+2828+28
Scenario: Restarting a job with Configuration Put and Bundle Start steps27 ms0028+2828+28
Scenario: Restarting a job with Package Uninstall and Bundle Start steps20 ms0028+2828+28
Scenario: Restarting a job with invalid Configuration Put and multiple devices two times66 ms0033+3333+33
Scenario: Restarting a job with invalid Configuration Put step two times38 ms0036+3636+36
Scenario: Restarting a job with invalid Package Install step and multiple devices two times46 ms0031+3131+31
Scenario: Restarting a job with invalid Package Install step two times44 ms0034+3434+34
Scenario: Restarting a job with invalid Package Uninstall step and multiple devices two times33 ms0032+3232+32
Scenario: Restarting a job with invalid Package Uninstall step two times37 ms0034+3434+34
Scenario: Restarting a job with valid Configuration Put step and multiple devices two times23 ms0033+3333+33
Scenario: Restarting a job with valid Configuration Put step two times41 ms0036+3636+36
Scenario: Restarting a job with valid Package Install step and multiple devices two times22 ms0029+2929+29
Scenario: Restarting a job with valid Package Install step two times31 ms0034+3434+34
Scenario: Restarting a job with valid Package Uninstall step and multiple devices two times23 ms0030+3030+30
Scenario: Restarting a job with valid Package Uninstall step two times21 ms0032+3232+32
Scenario: Restarting job With invalid Asset Write and multiple two times26 ms0034+3434+34
Scenario: Restarting job With valid Asset Write step two times31 ms0036+3636+36
Scenario: Restarting job with Asset Write and Bundle Start steps and multiple devices25 ms0031+3131+31
Scenario: Restarting job with Asset Write step18 ms0025+2525+25
Scenario: Restarting job with Asset Write step and multiple devices21 ms0028+2828+28
Scenario: Restarting job with Bundle Start step28 ms0025+2525+25
Scenario: Restarting job with Bundle Start step and multiple devices29 ms0027+2727+27
Scenario: Restarting job with Bundle Stop and Bundle Start step and multiple devices19 ms0031+3131+31
Scenario: Restarting job with Bundle Stop and Bundle Start steps22 ms0029+2929+29
Scenario: Restarting job with Bundle Stop step23 ms0025+2525+25
Scenario: Restarting job with Bundle Stop step and multiple devices23 ms0027+2727+27
Scenario: Restarting job with Command Execution and Bundle Start steps and multiple devices26 ms0031+3131+31
Scenario: Restarting job with Command Execution step22 ms0025+2525+25
Scenario: Restarting job with Command Execution step and multiple devices21 ms0027+2727+27
Scenario: Restarting job with Configuration Put and Bundle Start steps and multiple devices31 ms0031+3131+31
Scenario: Restarting job with Configuration Put step24 ms0025+2525+25
Scenario: Restarting job with Configuration Put step and multiple devices27 ms0027+2727+27
Scenario: Restarting job with Package Download/Install and Bundle Start steps and multiple devices41 ms0059+5959+59
Scenario: Restarting job with Package Download/Install step and multiple devices24 ms0027+2727+27
Scenario: Restarting job with Package Install step22 ms0025+2525+25
Scenario: Restarting job with Package Uninstall and Bundle start steps and multiple device23 ms0031+3131+31
Scenario: Restarting job with Package Uninstall step17 ms0025+2525+25
Scenario: Restarting job with Package Uninstall step and multiple device20 ms0027+2727+27
Scenario: Restarting job with invalid Asset Write step two times31 ms0036+3636+36
Scenario: Restarting job with invalid Bundle Start and Bundle Stop steps and multiple devices two times40 ms0041+4141+41
Scenario: Restarting job with invalid Bundle Start and Bundle Stop steps two times23 ms0043+4343+43
Scenario: Restarting job with invalid Bundle Start step and multiple devices two times34 ms0035+3535+35
Scenario: Restarting job with invalid Bundle Start step two times24 ms0037+3737+37
Scenario: Restarting job with invalid Bundle Stop step and multiple devices two times39 ms0035+3535+35
Scenario: Restarting job with invalid Bundle Stop step two times38 ms0037+3737+37
Scenario: Restarting job with invalid Command Execution and Package Install step two times34 ms0036+3636+36
Scenario: Restarting job with invalid Command Execution and Package Install steps and multiple devices two times38 ms0037+3737+37
Scenario: Restarting job with invalid Command Execution step and multiple devices two times48 ms0031+3131+31
Scenario: Restarting job with invalid Command Execution step two times50 ms0032+3232+32
Scenario: Restarting job with invalid Configuration Put And Command Execution steps two times34 ms0038+3838+38
Scenario: Restarting job with invalid Configuration Put and Command Execution steps and multiple devices two times44 ms0037+3737+37
Scenario: Restarting job with invalid Package Uninstall and Asset Write steps and multiple devices two times35 ms0038+3838+38
Scenario: Restarting job with invalid Package Uninstall and Asset Write steps two times29 ms0040+4040+40
Scenario: Restarting job with two Bundle Start steps21 ms0029+2929+29
Scenario: Restarting job with two Bundle Start steps and multiple devices21 ms0031+3131+31
Scenario: Restarting job with valid Asset Write step and multiple devices two times31 ms0034+3434+34
Scenario: Restarting job with valid Bundle Start And Bundle Stop steps two times25 ms0043+4343+43
Scenario: Restarting job with valid Bundle Start and Bundle Stop steps and multiple devices two times36 ms0041+4141+41
Scenario: Restarting job with valid Bundle Start step and multiple devices two times31 ms0035+3535+35
Scenario: Restarting job with valid Bundle Start step two times39 ms0037+3737+37
Scenario: Restarting job with valid Bundle Stop step and multiple devices two times23 ms0035+3535+35
Scenario: Restarting job with valid Bundle Stop step two times31 ms0037+3737+37
Scenario: Restarting job with valid Command Execution and Package Install steps and multiple devices two times36 ms0033+3333+33
Scenario: Restarting job with valid Command Execution and Package Install steps two times46 ms0034+3434+34
Scenario: Restarting job with valid Command Execution step and multiple devices two times59 ms0031+3131+31
Scenario: Restarting job with valid Command Execution step two times42 ms0032+3232+32
Scenario: Restarting job with valid Configuration Put and Command Execution steps and multiple devices two times44 ms0037+3737+37
Scenario: Restarting job with valid Configuration Put and Command Execution steps two times36 ms0038+3838+38
Scenario: Restarting job with valid Package Uninstall and Asset Write steps and multiple devices two times36 ms0036+3636+36
Scenario: Restarting job with valid Package Uninstall and Asset Write steps two times22 ms0038+3838+38
Scenario: Role creator sanity checks5 ms002+22+2
Scenario: Role entry with no actions13 ms006+66+6
Scenario: Role object equality check6 ms002+22+2
Scenario: Role service related objects sanity checks5 ms004+44+4
Scenario: Search By Client ID And Get Multiple Matches31 ms0037+3737+37
Scenario: Search By Client ID And Get No Matches15 ms0010+1010+10
Scenario: Search By Client ID And Get One Match34 ms008+88+8
Scenario: Search By Client ID and Display Name6 ms0012+1212+12
Scenario: Search By Client ID and Serial Number6 ms0012+1212+12
Scenario: Search By Client ID and Status6 ms0012+1212+12
Scenario: Search By Client ID, Display Name and Serial Number17 ms0012+1212+12
Scenario: Search By Client ID, Display Name and Status7 ms0012+1212+12
Scenario: Search By Client ID, Display Name, Serial Number and Status12 ms0012+1212+12
Scenario: Search By Device Status And Get No Matches5 ms008+88+8
Scenario: Search By Device's Display Name And Get One Match7 ms008+88+8
Scenario: Search By Display Name and Serial Number5 ms0012+1212+12
Scenario: Search By Display Name and Status5 ms0012+1212+12
Scenario: Search By Full Client ID And Get One Match5 ms0010+1010+10
Scenario: Search By Non-existing Client ID And Get No Matches7 ms008+88+8
Scenario: Search By One Letter Of Display Name6 ms008+88+8
Scenario: Search By One Letter Of Serial Number12 ms0012+1212+12
Scenario: Search By Serial Number And Get Multiple Matches14 ms0014+1414+14
Scenario: Search By Serial Number And Get No Matches4 ms0010+1010+10
Scenario: Search By Serial Number And Get One Match12 ms0011+1111+11
Scenario: Search By Serial Number and Status13 ms0012+1212+12
Scenario: Search By Serial Number, Display Name and Status10 ms0012+1212+12
Scenario: Search By Specific Serial Number6 ms0010+1010+10
Scenario: Search By Status And Get Multiple Matches5 ms0010+1010+10
Scenario: Search by Device Status And Get One Match4 ms0010+1010+10
Scenario: Search for a non existent client ID3 ms0066
Scenario: Search for an access info entity by an incorrect user ID7 ms0011+1111+11
Scenario: Search the role database for a random ID13 ms007+77+7
Scenario: Send BIRTH message and then DC message31 ms0015+1515+15
Scenario: Send BIRTH message and then DC message while broker ip is NOT set29 ms006+66+6
Scenario: Send BIRTH message and then DC message while broker ip is set by System56 ms008+88+8
Scenario: Send BIRTH message and then DC message while broker ip is set by config file47 ms008+88+8
Scenario: Set a correct minimum for password length11 ms003+33+3
Scenario: Set an incorrect minimum for password length7 ms006+66+6
Scenario: Set environment variables0.14 sec0061+6161+61
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 Created8 ms0015+1515+15
Scenario: Setting InfiniteChildAccounts To True And Decreasing MaxNumberChildAccounts When Sub-accounts Are Already Created7 ms0014+1414+14
Scenario: Setting Lockout Duration To 0 Seconds8 ms0015+1515+15
Scenario: Setting Lockout Duration To Negative Value11 ms007+77+7
Scenario: Setting Max Failures To 010 ms0015+1515+15
Scenario: Setting Max Failures To 112 ms0015+1515+15
Scenario: Setting Max Failures To 10014 ms0015+1515+15
Scenario: Setting Max Failures To Negative Value9 ms007+77+7
Scenario: Setting Reset After Login Counter To 0 Seconds13 ms0017+1717+17
Scenario: Setting Reset After Login Counter To Negative Value5 ms007+77+7
Scenario: Setting configuration without mandatory items must raise an error3 ms0055
Scenario: Simple create4 ms0011+1111+11
Scenario: Simple positive scenario for creating daily index19 ms0014+1414+14
Scenario: Simple positive scenario for creating default - weekly index18 ms0012+1212+12
Scenario: Simple positive scenario for creating hourly index21 ms0014+1414+14
Scenario: Start broker for all scenarios0.42 sec0044+4444+44
Scenario: Start datastore for all scenarios0.64 sec0030+3030+30
Scenario: Start event broker for all scenarios0.42 sec0050+5050+50
Scenario: Starting a job with Asset Write and Bundle Start steps30 ms0036+3636+36
Scenario: Starting a job with Asset Write step27 ms0025+2525+25
Scenario: Starting a job with Bundle Start step23 ms0034+3434+34
Scenario: Starting a job with Bundle Stop and Bundle Start steps12 ms0039+3939+39
Scenario: Starting a job with Bundle Stop step22 ms0035+3535+35
Scenario: Starting a job with Command Execution and Bundle Start steps19 ms0037+3737+37
Scenario: Starting a job with Command Execution step20 ms0025+2525+25
Scenario: Starting a job with Configuration Put and Bundle Start steps28 ms0037+3737+37
Scenario: Starting a job with Configuration Put step27 ms0025+2525+25
Scenario: Starting a job with Package Install and Bundle Start steps26 ms0039+3939+39
Scenario: Starting a job with Package Install step31 ms0032+3232+32
Scenario: Starting a job with Package Uninstall and Bundle Start steps23 ms0036+3636+36
Scenario: Starting a job with Package Uninstall step32 ms0033+3333+33
Scenario: Starting a job with invalid Asset Write step28 ms0031+3131+31
Scenario: Starting a job with invalid Asset Write step and multiple targets35 ms0029+2929+29
Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps33 ms0036+3636+36
Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps and multiple devices31 ms0035+3535+35
Scenario: Starting a job with invalid Bundle Start step26 ms0031+3131+31
Scenario: Starting a job with invalid Bundle Stop step22 ms0031+3131+31
Scenario: Starting a job with invalid Bundle Stop step and multiple devices34 ms0029+2929+29
Scenario: Starting a job with invalid Command Execution step44 ms0027+2727+27
Scenario: Starting a job with invalid Configuration Put step31 ms0030+3030+30
Scenario: Starting a job with invalid Configuration Put step and multiple devices36 ms0028+2828+28
Scenario: Starting a job with invalid Package Install step38 ms0029+2929+29
Scenario: Starting a job with invalid Package Install step and multiple devices44 ms0026+2626+26
Scenario: Starting a job with invalid Package Uninstall and Asset Write steps32 ms0034+3434+34
Scenario: Starting a job with invalid Package Uninstall and Asset Write steps and multiple devices47 ms0032+3232+32
Scenario: Starting a job with invalid Package Uninstall step31 ms0029+2929+29
Scenario: Starting a job with invalid Package Uninstall step and multiple targets55 ms0026+2626+26
Scenario: Starting a job with two Bundle Start steps15 ms0039+3939+39
Scenario: Starting a job with valid Asset Write step33 ms0031+3131+31
Scenario: Starting a job with valid Asset Write step and multiple targets46 ms0029+2929+29
Scenario: Starting a job with valid Bundle Start and Bundle Stop steps24 ms0036+3636+36
Scenario: Starting a job with valid Bundle Start and Bundle Stop steps and multiple devices43 ms0034+3434+34
Scenario: Starting a job with valid Bundle Start step36 ms0031+3131+31
Scenario: Starting a job with valid Bundle Stop step28 ms0031+3131+31
Scenario: Starting a job with valid Bundle Stop step and multiple devices57 ms0029+2929+29
Scenario: Starting a job with valid Command Execution step50 ms0027+2727+27
Scenario: Starting a job with valid Configuration Put step29 ms0031+3131+31
Scenario: Starting a job with valid Configuration Put step and multiple devices42 ms0026+2626+26
Scenario: Starting a job with valid Package Install step38 ms0029+2929+29
Scenario: Starting a job with valid Package Install step and multiple devices59 ms0026+2626+26
Scenario: Starting a job with valid Package Uninstall and Asset Write steps23 ms0033+3333+33
Scenario: Starting a job with valid Package Uninstall and Asset Write steps and multiple devices42 ms0032+3232+32
Scenario: Starting a job with valid Package Uninstall step31 ms0030+3030+30
Scenario: Starting a job with valid Package Uninstall step and multiple targets69 ms0026+2626+26
Scenario: Starting and stopping the simulator should create a device entry and properly set its status9 ms0020+2020+20
Scenario: Starting job with Asset Write and Bundle Start steps and multiple devices19 ms0032+3232+32
Scenario: Starting job with Asset Write step and multiple devices19 ms0028+2828+28
Scenario: Starting job with Bundle Start step and multiple devices30 ms0028+2828+28
Scenario: Starting job with Bundle Stop and Bundle Start step and multiple devices26 ms0032+3232+32
Scenario: Starting job with Bundle Stop step and multiple devices28 ms0028+2828+28
Scenario: Starting job with Command Execution and Bundle Start steps and multiple devices23 ms0032+3232+32
Scenario: Starting job with Command Execution step and multiple devices20 ms0028+2828+28
Scenario: Starting job with Configuration Put and Bundle Start steps and multiple devices24 ms0032+3232+32
Scenario: Starting job with Configuration Put step and multiple devices18 ms0028+2828+28
Scenario: Starting job with Package Download/Install and Bundle Start steps and multiple devices27 ms0038+3838+38
Scenario: Starting job with Package Download/Install step and multiple devices54 ms0034+3434+34
Scenario: Starting job with Package Uninstall and Bundle start steps and multiple device25 ms0032+3232+32
Scenario: Starting job with Package Uninstall step and multiple device25 ms0027+2727+27
Scenario: Starting job with invalid Bundle Start step and multiple devices61 ms0029+2929+29
Scenario: Starting job with invalid Command Execution and Package Install steps22 ms0031+3131+31
Scenario: Starting job with invalid Command Execution step and multiple devices53 ms0028+2828+28
Scenario: Starting job with invalid Command Execution, invalid Package Install steps and multiple devices30 ms0029+2929+29
Scenario: Starting job with invalid Configuration Put and Command Execution steps45 ms0032+3232+32
Scenario: Starting job with invalid Configuration Put and Command Execution steps and multiple devices41 ms0031+3131+31
Scenario: Starting job with two Bundle Start steps and multiple devices28 ms0032+3232+32
Scenario: Starting job with valid Bundle Start step and multiple devices46 ms0029+2929+29
Scenario: Starting job with valid Command Execution and Package Install steps26 ms0031+3131+31
Scenario: Starting job with valid Command Execution step and multiple devices47 ms0026+2626+26
Scenario: Starting job with valid Command Execution, valid Package Install steps and multiple devices44 ms0029+2929+29
Scenario: Starting job with valid Configuration Put and Command Execution steps30 ms0032+3232+32
Scenario: Starting job with valid Configuration Put and Command Execution steps and multiple devices68 ms0030+3030+30
Scenario: Stealing link scenario23 ms0028+2828+28
Scenario: Step definition factory sanity checks2 ms002+22+2
Scenario: Step definition with a duplicate name13 ms006+66+6
Scenario: Step definition with a null name12 ms006+66+6
Scenario: Step definition with a null scope ID10 ms006+66+6
Scenario: Step definition with an empty name6 ms005+55+5
Scenario: Step factory sanity checks3 ms002+22+2
Scenario: Step with a null scope ID4 ms0011+1111+11
Scenario: Stop broker after all scenarios0.32 sec0046+4646+46
Scenario: Stop datastore after all scenarios0.22 sec0030+3030+30
Scenario: Stop event broker for all scenarios0.43 sec0050+5050+50
Scenario: Stop job with multiple Asset Write and Package Install steps and one target29 ms0037+3737+37
Scenario: Stop job with multiple Bundle Start and Package Install steps and one target48 ms0037+3737+37
Scenario: Stop job with multiple Bundle Stop and Package Uninstall steps and one target47 ms0037+3737+37
Scenario: Stop job with multiple Command Execution and Package Install steps and one target33 ms0034+3434+34
Scenario: Stop job with multiple Configuration Put and Package Uninstall steps and one target40 ms0035+3535+35
Scenario: Stop job with multiple targets and Asset Write and Package Install steps and one target49 ms0037+3737+37
Scenario: Stop job with multiple targets and Bundle Start and Package Install steps40 ms0036+3636+36
Scenario: Stop job with multiple targets and Bundle Stop and Package Uninstall steps38 ms0037+3737+37
Scenario: Stop job with multiple targets and Command Execution and Package Install steps69 ms0034+3434+34
Scenario: Stop job with multiple targets and Configuration Put and Package Uninstall steps90 ms0037+3737+37
Scenario: Test LOOSE user coupling on single connection15 ms0028+2828+28
Scenario: Test LOOSE user coupling with 3 connections12 ms0038+3838+38
Scenario: Test STRICT user coupling on single connection24 ms0025+2525+25
Scenario: Test STRICT user coupling with 3 connections and a reserved user27 ms0063+6363+63
Scenario: Test STRICT user coupling with user change allowed on single connection17 ms0036+3636+36
Scenario: Test account query4 ms0044
Scenario: Test the message store with server timestamp indexing30 ms0026+2626+26
Scenario: Test the message store with timestamp indexing30 ms0026+2626+26
Scenario: The Client ID is case sensitive3 ms0088
Scenario: To be defined4 ms0013+1313+13
Scenario: Translating "CommandRequestMessage" to "KuraRequestMessage"24 ms004+44+4
Scenario: Translating CommandRequestMessage to null7 ms004+44+4
Scenario: Translating empty message to empty message6 ms004+44+4
Scenario: Translating from "AssetRequestMessage" to "AssetResponseMessage"5 ms004+44+4
Scenario: Translating invalid jms data message with valid channel, body and metrics into kura data message3 ms005+55+5
Scenario: Translating invalid kura data message with valid channel, body and metrics into jms message3 ms005+55+5
Scenario: Translating invalid kura data message with valid channel, body and metrics into mqtt message5 ms005+55+5
Scenario: Translating kura data message with null channel, and payload without body and with metrics3 ms005+55+5
Scenario: Translating kura data message with valid channel and with null payload3 ms005+55+5
Scenario: Translating kura data message with valid channel and without body and metrics into jms message3 ms005+55+5
Scenario: Translating kura data message with valid channel, and with null payload3 ms005+55+5
Scenario: Translating kura data message with valid channel, body and metrics into jms message2 ms005+55+5
Scenario: Translating kura data message with valid channel, metrics and without body into jms message3 ms005+55+5
Scenario: Translating kura data message with valid channel, metrics and without body into mqtt message3 ms005+55+5
Scenario: Translating null to KuraRequestMessage6 ms004+44+4
Scenario: Translating of jms message with empty payload and invalid topic that contain only userName into kura data message1 ms005+55+5
Scenario: Translating of jms message with empty payload and valid topic into kura data message3 ms006+66+6
Scenario: Translating of jms message with invalid payload and valid topic into kura data message2 ms006+66+6
Scenario: Translating of jms message with valid payload and valid topic into kura data message4 ms006+66+6
Scenario: Translating of mqtt message with invalid payload and invalid topic into kura data message3 ms005+55+5
Scenario: Translating of mqtt message with invalid payload and with null topic into kura data message3 ms005+55+5
Scenario: Translation of kura data message with valid channel and without body and metrics into mqtt message4 ms005+55+5
Scenario: Translation of kura data message with valid channel, body and metrics into mqtt message4 ms005+55+5
Scenario: Translation of kura data message with valid channel, metrics and without body into mqtt message3 ms005+55+5
Scenario: Translation of mqtt message with empty payload into kura data message6 ms006+66+6
Scenario: Translation of mqtt message with invalid payload and invalid topic into kura response message5 ms005+55+5
Scenario: Translation of mqtt message with invalid payload and valid topic into kura data message5 ms006+66+6
Scenario: Translation of mqtt message with invalid payload and valid topic into kura response message3 ms006+66+6
Scenario: Translation of mqtt message with valid payload and invalid topic into kura response message5 ms005+55+5
Scenario: Translation of mqtt message with valid payload and valid topic into kura data message6 ms006+66+6
Scenario: Translation of mqtt message with valid payload and valid topic into kura response message4 ms006+66+6
Scenario: Try to add two different roles with same permissions12 ms0021+2121+21
Scenario: Try to change an existing connection ID3 ms0077
Scenario: Try to create an access into entity with an invalid role id6 ms0012+1212+12
Scenario: Try to delete a non existing device from the registry2 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" role15 ms0012+1212+12
Scenario: Try to find users that have assigned specific role10 ms0012+1212+12
Scenario: Try to modify the connection client ID3 ms0077
Scenario: Try to update the device client ID3 ms0044
Scenario: Uncorrect Login While Lockout Policy Is Disabled11 ms0017+1717+17
Scenario: Uncorrect Login While Lockout Policy Is Enabled11 ms0017+1717+17
Scenario: Update a group entry in the database9 ms009+99+9
Scenario: Update a group entry with a false ID18 ms0010+1010+10
Scenario: Update a job XML definition8 ms0010+1010+10
Scenario: Update a job description7 ms0010+1010+10
Scenario: Update a job name3 ms0010+1010+10
Scenario: Update a non existing device3 ms0055
Scenario: Update a nonexistent job3 ms0010+1010+10
Scenario: Update a nonexistent step definition6 ms007+77+7
Scenario: Update a step definition name7 ms007+77+7
Scenario: Update a step definition processor name6 ms008+88+8
Scenario: Update a step definition target type7 ms008+88+8
Scenario: Update existing role name14 ms008+88+8
Scenario: Update job id of an existing execution item3 ms008+88+8
Scenario: Update schedule which doesn't exist5 ms005+55+5
Scenario: Update scheduler end date6 ms009+99+9
Scenario: Update scheduler name12 ms008+88+8
Scenario: Update scheduler start date7 ms008+88+8
Scenario: Update the end time of an existing execution item6 ms009+99+9
Scenario: Update trigger definition12 ms008+88+8
Scenario: Update user6 ms007+77+7
Scenario: Update user that doesn't exist4 ms005+55+5
Scenario: User locking itself out by using out login attempts10 ms0016+1616+16
Scenario: User locking itself out with failed attempts and not waiting to unlock4 ms0017+1717+17
Scenario: User locking itself out with failed attempts and waiting to unlock13 ms0017+1717+17
Scenario: User login with wrong pass, but with enough time between login failures14 ms0019+1919+19
Scenario: User not locking itself out by using less than max failed login attempts9 ms0017+1717+17
Scenario: Validate a device client based search with a null client ID6 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 ID5 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 ID3 ms0066
Scenario: Validate a device search with a null scope ID3 ms0066
Scenario: Validate a null creator4 ms0055
Scenario: Validate a null device7 ms0055
Scenario: Validate a null device count4 ms0055
Scenario: Validate a null device query3 ms0055
Scenario: Validate a regular creator4 ms0044
Scenario: Validate a regular device client search5 ms0044
Scenario: Validate a regular device count4 ms0044
Scenario: Validate a regular device query3 ms0044
Scenario: Validate a regular device search3 ms0055
Scenario: Validate deleting a device with a null device ID4 ms0066
Scenario: Validate deleting a device with a null scope ID5 ms0066
Scenario: Waiting For Lock Duration Time To Pass15 ms0019+1919+19
Scenario: Waiting For Reset After Login Counter To Pass13 ms0018+1818+18
empty) scope0 ms004+44+4