Test Result : (root)

18 failures (+16) , 122 skipped (+121)
16,527 tests (+12878)
Took 20 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 description16 ms24
 Scenario: Creating unique Access Group with special symbols in description.Then I find the group with name "groupName53"16 ms24
 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 usage4 ms1
 Scenario: Executing Job And Then Restarting Device.Scenario: Executing Job And Then Restarting Device5 ms1
 Scenario: Executing Job And Then Restarting Device.Then I find 4 device events4 ms1
 Scenario: Executing Job When Device Connected After The Specified Start Date And Time.And I confirm the executed job is finished25 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 Time26 ms1
 Scenario: Executing Job When Device Connected Before End Date And Time.And I confirm the executed job is finished5 ms1
 Scenario: Executing Job When Device Connected Before End Date And Time.Scenario: Executing Job When Device Connected Before End Date And Time7 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-Account13 ms1
 Scenario: List Endpoints From "kapua-sys" Account.Scenario: List Endpoints From "kapua-sys" Account14 ms1
 Scenario: List Endpoints From "kapua-sys" Account.Then I find 3 endpoints14 ms1
 Scenario: List Endpoints From Sub-Account Of Another Sub-Account.And I create endpoint with schema "Schema1", domain "abc.com" and port 22224 ms1
 Scenario: List Endpoints From Sub-Account Of Another Sub-Account.Scenario: List Endpoints From Sub-Account Of Another Sub-Account6 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-account3 ms1

All Tests

ClassDurationFail(diff)Skip(diff)Pass(diff)Total(diff)
Scenario: A fresh database must contain 1 default role in the root scope10 ms004+44+4
Scenario: A newly created account must have some metadata5 ms0033
Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic11 ms0088
Scenario: Access info service sanity checks5 ms004+44+4
Scenario: Access service comparison sanity checks8 ms003+33+3
Scenario: Account based ClientInfo data check36 ms002424
Scenario: Account exactly on its expiration date5 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 date11 ms0013+1313+13
Scenario: Account with no expiration date11 ms0013+1313+13
Scenario: Add Access Info domain permissions to new user11 ms0026+2626+26
Scenario: Add Account permissions to the role in child account11 ms0028+2828+28
Scenario: Add Credential domain permissions to new user19 ms0018+1818+18
Scenario: Add Datastore domain permissions to new user0.36 sec0019+1919+19
Scenario: Add Device Connection domain permissions to kapua-sys user12 ms0011+1111+11
Scenario: Add Device Connection domain permissions to new user12 ms0023+2323+23
Scenario: Add Device Event domain permissions to new user16 ms0016+1616+16
Scenario: Add Device domain permissions to new user13 ms0017+1717+17
Scenario: Add Domain domain permissions to kapua-sys user12 ms0017+1717+17
Scenario: Add Domain domain permissions to new user12 ms0032+3232+32
Scenario: Add Endpoint Permission To The User14 ms0030+3030+30
Scenario: Add Endpoint_info permissions to the role in child account17 ms0030+3030+30
Scenario: Add Group domain permissions to new user11 ms0017+1717+17
Scenario: Add Group permissions to the role in child account13 ms0026+2626+26
Scenario: Add Job domain permissions to new user13 ms0019+1919+19
Scenario: Add Role domain permissions to new user11 ms0017+1717+17
Scenario: Add Role permissions to the role in child account15 ms0026+2626+26
Scenario: Add Scheduler Permissions With Job Permissions21 ms0031+3131+31
Scenario: Add Scheduler Permissions Without Job Permissions10 ms0021+2121+21
Scenario: Add Scheduler permissions to the role in child account23 ms0036+3636+36
Scenario: Add Tag domain permissions to new user18 ms0015+1515+15
Scenario: Add Tag permissions to the role in child account17 ms0026+2626+26
Scenario: Add User domain permissions to new user13 ms0020+2020+20
Scenario: Add account permissions to the role35 ms0019+1919+19
Scenario: Add admin role to the user21 ms0044+4444+44
Scenario: Add and delete Account permissions from the "admin" role10 ms0014+1414+14
Scenario: Add and delete Device permissions from the "admin" role13 ms0014+1414+14
Scenario: Add and delete Endpoint_info permissions from the "admin" role17 ms0014+1414+14
Scenario: Add and delete Group permissions from the "admin" role10 ms0014+1414+14
Scenario: Add and delete Job permissions from the "admin" role14 ms0014+1414+14
Scenario: Add and delete Role permissions from the "admin" role17 ms0014+1414+14
Scenario: Add and delete User permissions from the "admin" role14 ms0015+1515+15
Scenario: Add datastore permissions to the role36 ms0027+2727+27
Scenario: Add deleted role again15 ms0010+1010+10
Scenario: Add device event permissions to the role10 ms0032+3232+32
Scenario: Add device permissions to the role12 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 role17 ms0031+3131+31
Scenario: Add group permissions to the role12 ms0018+1818+18
Scenario: Add job permissions to the role17 ms0019+1919+19
Scenario: Add job permissions to the role in child account24 ms0026+2626+26
Scenario: Add role permissions to the role16 ms0019+1919+19
Scenario: Add same permission twice to the same role19 ms0014+1414+14
Scenario: Add same role to user twice12 ms0013+1313+13
Scenario: Add scheduler permissions to the role13 ms0031+3131+31
Scenario: Add tag permissions to the role18 ms0018+1818+18
Scenario: Add user permissions to the role10 ms0019+1919+19
Scenario: Add user permissions to the role in child account8 ms0026+2626+26
Scenario: Adding "Cron Job" Schedule With All Valid Parameters4 ms0010+1010+10
Scenario: Adding "Cron Job" Schedule With All Valid Parameters And Null Cron Value9 ms0010+1010+10
Scenario: Adding "Cron Job" Schedule With All Valid Parameters Except Cron Format16 ms0011+1111+11
Scenario: Adding "Cron Job" Schedule With End Date Only19 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 Parameter7 ms0016+1616+16
Scenario: Adding "Cron Job" Schedule With Non-Unique Start Date Parameter10 ms0015+1515+15
Scenario: Adding "Cron Job" Schedule With Start Date Only6 ms0011+1111+11
Scenario: Adding "Cron Job" Schedule With the same Start and End time7 ms0012+1212+12
Scenario: Adding "Cron Job" Schedule Without The Start Date Parameter17 ms0010+1010+10
Scenario: Adding "Device Connect" Schedule With All Valid Parameters6 ms008+88+8
Scenario: Adding "Device Connect" Schedule With End Date Only5 ms0010+1010+10
Scenario: Adding "Device Connect" Schedule With End Time before Start time7 ms0011+1111+11
Scenario: Adding "Device Connect" Schedule With Max Length Name6 ms008+88+8
Scenario: Adding "Device Connect" Schedule With Min Length Name6 ms008+88+8
Scenario: Adding "Device Connect" Schedule With Name Only6 ms009+99+9
Scenario: Adding "Device Connect" Schedule With Non-Unique End Date Parameter7 ms0013+1313+13
Scenario: Adding "Device Connect" Schedule With Non-Unique Name9 ms0013+1313+13
Scenario: Adding "Device Connect" Schedule With Non-Unique Start Date Parameter7 ms0011+1111+11
Scenario: Adding "Device Connect" Schedule With Start Date Only6 ms0010+1010+10
Scenario: Adding "Device Connect" Schedule With the same Start and End time5 ms0011+1111+11
Scenario: Adding "Device Connect" Schedule Without Name9 ms0010+1010+10
Scenario: Adding "Device Connect" Schedule Without The Start Date Parameter9 ms009+99+9
Scenario: Adding "Empty" Tag To Device5 ms0055
Scenario: Adding "Interval Job" Schedule With All Valid Parameters6 ms0010+1010+10
Scenario: Adding "Interval Job" Schedule With End Date Only9 ms0010+1010+10
Scenario: Adding "Interval Job" Schedule With End Time before Start time8 ms0012+1212+12
Scenario: Adding "Interval Job" Schedule With Max Length Name16 ms0010+1010+10
Scenario: Adding "Interval Job" Schedule With Min Length Name14 ms0010+1010+10
Scenario: Adding "Interval Job" Schedule With Name Only8 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 Name7 ms0015+1515+15
Scenario: Adding "Interval Job" Schedule With Non-Unique Start Date Parameter6 ms0015+1515+15
Scenario: Adding "Interval Job" Schedule With Null Interval Number9 ms0012+1212+12
Scenario: Adding "Interval Job" Schedule With Start Date Only7 ms0011+1111+11
Scenario: Adding "Interval Job" Schedule With the same Start and End time7 ms0012+1212+12
Scenario: Adding "Interval Job" Schedule Without Interval Number9 ms0011+1111+11
Scenario: Adding "Interval Job" Schedule Without The Start Date Parameter7 ms009+99+9
Scenario: Adding "Interval Job" Schedule Without a Name10 ms0011+1111+11
Scenario: Adding "admin" role to a user in a child account14 ms0014+1414+14
Scenario: Adding "admin" role to multiple users10 ms0018+1818+18
Scenario: Adding "admin" role twice8 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 scope8 ms0030+3030+30
Scenario: Adding Account:Read and Account:Delete permissions to user in same scope9 ms0021+2121+21
Scenario: Adding Account:Read and Account:Write permissions to user in same scope12 ms0019+1919+19
Scenario: Adding Account:Read permission to user in same scope11 ms0023+2323+23
Scenario: Adding Account:Read permission to user in sub-account scope10 ms0029+2929+29
Scenario: Adding Account:Write and Account:Delete permission to user in same scope22 ms0023+2323+23
Scenario: Adding Account:Write permission to user in same scope13 ms0025+2525+25
Scenario: Adding Account:Write permission to user in sub-account scope11 ms0031+3131+31
Scenario: Adding Multiple Permissions To User13 ms0020+2020+20
Scenario: Adding One Permission To User15 ms0011+1111+11
Scenario: Adding Permissions To Child User13 ms0018+1818+18
Scenario: Adding Permissions To Parallel User15 ms0018+1818+18
Scenario: Adding Previously Deleted Permission16 ms0028+2828+28
Scenario: Adding Previously Deleted Tag From Device Again4 ms001111
Scenario: Adding Regular Device to a Group With Description5 ms0010+1010+10
Scenario: Adding Regular Device to a Group Without a Description8 ms0012+1212+12
Scenario: Adding Regular Group Without Description to Device12 ms0010+1010+10
Scenario: Adding Regular Tag Without Description To Device5 ms0066
Scenario: Adding Same Regular Group Without Description to Device8 ms0014+1414+14
Scenario: Adding Tag With Long Name Without Description To Device4 ms0066
Scenario: Adding Tag With Numbers Without Description To Device4 ms0066
Scenario: Adding Tag With Short Name Without Description To Device5 ms0066
Scenario: Adding Tag With Special Symbols Without Description To Device4 ms0066
Scenario: Adding all Account permissions to user in same scope11 ms0017+1717+17
Scenario: Adding all Account permissions to user in sub-account scope16 ms0024+2424+24
Scenario: Adding existing roles to user13 ms0015+1515+15
Scenario: Adding role from child account to user in new child account11 ms0015+1515+15
Scenario: Adding role to multiple users in child account9 ms0018+1818+18
Scenario: Adding same role twice to user in child account12 ms0015+1515+15
Scenario: Adding the same role to user twice in child account20 ms0013+1313+13
Scenario: All device parameters must match the device creator5 ms0033
Scenario: Assign 100 Devices to One Group11 ms0011+1111+11
Scenario: B1 Broker publish to CTRL_ACC_REPLY24 ms0099
Scenario: B10 Broker create sub-topic on ACL_DATA_ACC is not allowed22 ms0099
Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed5 ms0088
Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI17 ms0099
Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed18 ms0099
Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed8 ms0088
Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY24 ms0099
Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY16 ms0099
Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account7 ms0099
Scenario: B5 Broker publish to CTRL_ACC is not allowed14 ms0099
Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed13 ms0099
Scenario: B7 Broker subscribe on CTRL_ACC is not allowed7 ms0088
Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI22 ms0099
Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed21 ms0099
Scenario: Basic Device Event queries10 ms001010
Scenario: Birth and applications event handling4 ms0012+1212+12
Scenario: Birth and death message handling9 ms0012+1212+12
Scenario: Birth and missing event handling11 ms0012+1212+12
Scenario: Birth message handling from a new device10 ms0013+1313+13
Scenario: Birth message handling from an existing device11 ms0012+1212+12
Scenario: Both the parent and child accounts do not expire8 ms0011+1111+11
Scenario: Both the parent and child accounts have the same expiration date7 ms0011+1111+11
Scenario: Captured date based ClientInfo data check27 ms003030
Scenario: Case sensitiveness of named device searches6 ms0044
Scenario: Change an existing step name3 ms0012+1212+12
Scenario: Change role name so it is too short4 ms0066
Scenario: Change the account parent path6 ms0055
Scenario: Changing Client ID5 ms009+99+9
Scenario: Changing Description On Group With Long Description5 ms007+77+7
Scenario: Changing Description On Group With Long Name8 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 Description5 ms007+77+7
Scenario: Changing Description On Group With Short Name6 ms007+77+7
Scenario: Changing Description On Tag With Long Description4 ms0044
Scenario: Changing Description On Tag With Long Name4 ms0055
Scenario: Changing Description On Tag With Numbers In Name7 ms0066
Scenario: Changing Description On Tag With Permitted Symbols In Name7 ms0044
Scenario: Changing Description On Tag With Short Description4 ms0044
Scenario: Changing Description On Tag With Short Name4 ms0044
Scenario: Changing Device Status To Disabled5 ms009+99+9
Scenario: Changing Device Status To Enabled9 ms009+99+9
Scenario: Changing Group's Description To Non-Uniqe One13 ms007+77+7
Scenario: Changing Group's Description To Uniqe One13 ms007+77+7
Scenario: Changing Group's Name To Contain Invalid Symbols In Name Without Changing Description8 ms008+88+8
Scenario: Changing Group's Name To Contain Permitted Symbols In Name Without Changing Description4 ms007+77+7
Scenario: Changing Group's Name To Non-Unique One9 ms009+99+9
Scenario: Changing Group's Name To Short One Without Changing Description8 ms007+77+7
Scenario: Changing Group's Name To Unique One9 ms007+77+7
Scenario: Changing Group's Name To a Long One Without Changing Description12 ms007+77+7
Scenario: Changing Group's Name To a Too Long One Without Changing Description8 ms008+88+8
Scenario: Changing Group's Name To a Too Short One Without Changing Description8 ms008+88+8
Scenario: Changing Tag's Description To Non-Unique One3 ms0055
Scenario: Changing Tag's Description To Unique One4 ms0077
Scenario: Changing Tag's Name To Contain Invalid Symbols In Name Without Description3 ms0055
Scenario: Changing Tag's Name To Contain Permitted Symbols In Name Without Description4 ms0055
Scenario: Changing Tag's Name To Non-Unique One11 ms0066
Scenario: Changing Tag's Name To Short One Without Description4 ms0077
Scenario: Changing Tag's Name To Unique One4 ms0077
Scenario: Changing Tag's Name To a Long One Without Description3 ms0077
Scenario: Changing Tag's Name To a Too Long One Without Description6 ms0055
Scenario: Changing Tag's Name To a Too Short One Without Description7 ms0055
Scenario: Changing description of a nonexisting role4 ms0077
Scenario: Changing job description to non-unique one6 ms0077
Scenario: Changing job description to the long one10 ms0066
Scenario: Changing job description to unique one9 ms0066
Scenario: Changing job description to very short one7 ms0077
Scenario: Changing job name to a long one without description9 ms0077
Scenario: Changing job name to a too long one without description4 ms0055
Scenario: Changing job name to a too short one without description10 ms0066
Scenario: Changing job name to contain invalid symbols in name without description6 ms0044
Scenario: Changing job name to contain permitted symbols in name without description9 ms0055
Scenario: Changing job name to non-unique one12 ms0088
Scenario: Changing job name to short one without description10 ms0077
Scenario: Changing job name to unique one12 ms0099
Scenario: Changing name of a nonexisting role6 ms0077
Scenario: Changing role description to a valid one5 ms0066
Scenario: Changing role name so it is too long4 ms0066
Scenario: Changing role name to contain special character4 ms0044
Scenario: Changing role name to null3 ms0066
Scenario: Changing role's name to a valid one4 ms0066
Scenario: Channel info queries based on datastore channel filters34 ms005050
Scenario: ChannelInfo client ID and topic data based on the client id31 ms002828
Scenario: ChannelInfo client ID based on the account id41 ms002626
Scenario: ChannelInfo last published date27 ms003030
Scenario: ChannelInfo topic data based on the account id29 ms002626
Scenario: Check account properties4 ms0044
Scenario: Check the Device Connection Domain data seetting6 ms0022
Scenario: Check the database cache coherency30 ms003030
Scenario: Check the mapping for message semantic topics38 ms003030
Scenario: Check the message store22 ms002020
Scenario: Check the sanity of the Device Connection Domain data initialization4 ms0022
Scenario: Child account expires after parent9 ms009+99+9
Scenario: Child account expires before parent7 ms0011+1111+11
Scenario: Child account has null expiration date7 ms009+99+9
Scenario: Client Id based ClientInfo data check28 ms002828
Scenario: Compare domain entries14 ms003+33+3
Scenario: Connect to the system and publish some data0.17 sec0022+2222+22
Scenario: Connection Service factory sanity checks2 ms0022
Scenario: Count access info entities in a specific scope8 ms0024+2424+24
Scenario: Count access role entities by scope8 ms0039+3939+39
Scenario: Count connections in empty scope4 ms0044
Scenario: Count connections in scope4 ms0055
Scenario: Count devices with a specific BIOS version8 ms0066
Scenario: Count domains in a blank database12 ms004+44+4
Scenario: Count domains in the database13 ms007+77+7
Scenario: Count events in empty scope8 ms0066
Scenario: Count groups9 ms0014+1414+14
Scenario: Count groups in a blank database13 ms005+55+5
Scenario: Count job items10 ms007+77+7
Scenario: Count job items in wrong - empty - scope9 ms008+88+8
Scenario: Count role permissions in specific scopes4 ms0018+1818+18
Scenario: Count roles in specific scopes8 ms0015+1515+15
Scenario: Count step definition items10 ms0044
Scenario: Count step definitions in wrong (empty) scope10 ms0011
Scenario: Count steps in the database3 ms0015+1515+15
Scenario: Count user5 ms0066
Scenario: Counting created roles items in the DB4 ms0055
Scenario: Create a regular event20 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 entry44 ms0066
Scenario: Create an event with a null scope ID10 ms0077
Scenario: Create and count several execution items for a job10 ms0012+1212+12
Scenario: Create index with specific prefix18 ms001212
Scenario: Create multiple users5 ms0055
Scenario: Create regular access permissions11 ms0020+2020+20
Scenario: Create same user in different accounts20 ms0015+1515+15
Scenario: Create scheduler with correct end date7 ms0088
Scenario: Create scheduler with empty schedule name13 ms0088
Scenario: Create scheduler with end date before start date11 ms0099
Scenario: Create scheduler with invalid Retry Interval property10 ms0099
Scenario: Create scheduler with invalid cron job trigger property7 ms0099
Scenario: Create scheduler with invalid schedule name14 ms0088
Scenario: Create scheduler with short schedule name11 ms0088
Scenario: Create scheduler with too long schedule name9 ms0088
Scenario: Create scheduler with valid Retry Interval property6 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 property13 ms0099
Scenario: Create scheduler without Retry Interval property6 ms0099
Scenario: Create scheduler without start date11 ms0077
Scenario: Create some regular role permissions6 ms009+99+9
Scenario: Create user that already exist6 ms0077
Scenario: Create user that has more than DB allowed length8 ms0055
Scenario: Create user with short name11 ms0055
Scenario: Create user with special characters in his name5 ms0055
Scenario: Create with permissions8 ms0014+1414+14
Scenario: Create with permissions and a role9 ms0017+1717+17
Scenario: Create with permissions and a role in the wrong scope8 ms0015+1515+15
Scenario: Creating 100 Sub-accounts While InfiniteChildAccounts Is Set To True8 ms007+77+7
Scenario: Creating A Device With Disabled Status16 ms007+77+7
Scenario: Creating A Device With Enabled Status8 ms007+77+7
Scenario: Creating A Device With Long Display Name8 ms007+77+7
Scenario: Creating A Device With Long Name6 ms007+77+7
Scenario: Creating A Device With Name Containing Invalid Symbols11 ms008+88+8
Scenario: Creating A Device With Name Containing Permitted Symbols6 ms007+77+7
Scenario: Creating A Device With No Name9 ms008+88+8
Scenario: Creating A Device With Non-unique Display Name12 ms007+77+7
Scenario: Creating A Device With Non-unique Name5 ms0010+1010+10
Scenario: Creating A Device With Short Display Name5 ms007+77+7
Scenario: Creating A Device With Short Name12 ms007+77+7
Scenario: Creating A Device With Too Long Display Name5 ms008+88+8
Scenario: Creating A Device With Too Long Name13 ms008+88+8
Scenario: Creating A Device With Unique Name12 ms009+99+9
Scenario: Creating A Valid Account11 ms005+55+5
Scenario: Creating An Account With Long Name8 ms005+55+5
Scenario: Creating An Account With Long Organization Name6 ms005+55+5
Scenario: Creating An Account With Non-unique Name11 ms008+88+8
Scenario: Creating An Account With Numbers And Valid Symbols In Name10 ms005+55+5
Scenario: Creating An Account With Short Name10 ms005+55+5
Scenario: Creating An Account With Short Organization Name9 ms005+55+5
Scenario: Creating An Account With Special Symbols In Organization Name11 ms005+55+5
Scenario: Creating An Account With Too Long Organization Name7 ms006+66+6
Scenario: Creating An Account With Unique Name10 ms007+77+7
Scenario: Creating An Account With Wrong TLD Format In Email9 ms0010+1010+10
Scenario: Creating An Account Without Email15 ms006+66+6
Scenario: Creating An Account Without Name8 ms006+66+6
Scenario: Creating An Account Without Ogranization Name13 ms006+66+6
Scenario: Creating And Account Without "@" In Email11 ms006+66+6
Scenario: Creating Devices And Than Setting Device Service So It Does Not Allow Devices9 ms0012+1212+12
Scenario: Creating Devices And Then Changing Device Service Values16 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 Devices9 ms009+99+9
Scenario: Creating Devices Under Account That Has Limited Child Devices7 ms0013+1313+13
Scenario: Creating Endpoint Non-Unique "Domain Name"5 ms008+88+8
Scenario: Creating Endpoint Non-Unique "Port"17 ms008+88+8
Scenario: Creating Endpoint Non-Unique "Schema"9 ms009+99+9
Scenario: Creating Endpoint With "Domain Name" Only5 ms006+66+6
Scenario: Creating Endpoint With "Port" Only4 ms006+66+6
Scenario: Creating Endpoint With "Schema" Only5 ms006+66+6
Scenario: Creating Endpoint With Disabled Secure Field4 ms006+66+6
Scenario: Creating Endpoint With Enabled Secure Field16 ms006+66+6
Scenario: Creating Endpoint With Invalid "Domain Name"4 ms006+66+6
Scenario: Creating Endpoint With Invalid "Schema" containing symbols4 ms006+66+6
Scenario: Creating Endpoint With Long "Domain Name"5 ms005+55+5
Scenario: Creating Endpoint With Max Length "Port"7 ms005+55+5
Scenario: Creating Endpoint With NULL parameters16 ms006+66+6
Scenario: Creating Endpoint With Schema Containing "http://"6 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"4 ms006+66+6
Scenario: Creating Endpoint With Small Number "Port"3 ms006+66+6
Scenario: Creating Endpoint With Too Big "Port"4 ms006+66+6
Scenario: Creating Endpoint With Too Long "Domain Name"5 ms006+66+6
Scenario: Creating Endpoint With Too Long "Schema"7 ms006+66+6
Scenario: Creating Endpoint Without "Domain Name"7 ms006+66+6
Scenario: Creating Endpoint Without "Port"7 ms006+66+6
Scenario: Creating Endpoint Without "Schema"5 ms006+66+6
Scenario: Creating Endpoint Without Long "Schema"4 ms005+55+5
Scenario: Creating Endpoint with invalid "Schema" which contains only numbers15 ms006+66+6
Scenario: Creating Group Invalid Symbols In Name Without Description5 ms007+77+7
Scenario: Creating Group With Invalid Symbols In Name With Valid Description9 ms007+77+7
Scenario: Creating Group With Long Name With Valid Description12 ms006+66+6
Scenario: Creating Group With Long Name Without Description11 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 Description8 ms006+66+6
Scenario: Creating Group With Permitted Symbols In Name With Valid Description13 ms006+66+6
Scenario: Creating Group With Short Name With Valid Description8 ms006+66+6
Scenario: Creating Group With Short Name Without Description6 ms006+66+6
Scenario: Creating Group With Too Long Name With Valid Description5 ms007+77+7
Scenario: Creating Group With Too Long Name Without Description5 ms007+77+7
Scenario: Creating Group With Too Short Name With Valid Description6 ms007+77+7
Scenario: Creating Group With Too Short Name Without Description12 ms007+77+7
Scenario: Creating Group Without a Name And With Valid Description7 ms007+77+7
Scenario: Creating Group Without a Name And Without Description13 ms007+77+7
Scenario: Creating Groups And Than Setting Group Service So It Does Not Allow Groups8 ms0011+1111+11
Scenario: Creating Groups And Then Changing InfiniteChildGroups To False And Set MaxNumberChildGroups8 ms0010+1010+10
Scenario: Creating Groups Under Account That Allows Infinite Child Groups3 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 Groups9 ms0012+1212+12
Scenario: Creating Jobs And Than Setting Job Service So It Does Not Allow Jobs8 ms0012+1212+12
Scenario: Creating Jobs And Then Changing Job Service Values11 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 Jobs6 ms009+99+9
Scenario: Creating Jobs Under Account That Has Limited Child Jobs11 ms0013+1313+13
Scenario: Creating Non-Unique Group With Valid Description12 ms008+88+8
Scenario: Creating Non-Unique Tag With Valid Description7 ms0055
Scenario: Creating Non-unique Group Without Description5 ms008+88+8
Scenario: Creating Non-unique Tag Without Description9 ms0044
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 Values9 ms0010+1010+10
Scenario: Creating Roles Under Account That Allows Infinite Child Roles9 ms0010+1010+10
Scenario: Creating Roles Under Account That Does Not Allow Roles4 ms009+99+9
Scenario: Creating Roles Under Account That Has Limited Child Roles16 ms0012+1212+12
Scenario: Creating Sub-accounts When InfiniteChildAccoounts Is Set To False And maxNumberChildAccounts Is Set14 ms0013+1313+13
Scenario: Creating Sub-accounts When InfiniteChildAccoounts Is Set To True And maxNumberChildAccounts Is Set8 ms0014+1414+14
Scenario: Creating Sub-accounts When InfiniteChildAccounts Is Set To False10 ms009+99+9
Scenario: Creating Sub-accounts when InfiniteChildAccounts Is Set To True9 ms0012+1212+12
Scenario: Creating Tag With Invalid Symbols In Name With Valid Description7 ms0044
Scenario: Creating Tag With Invalid Symbols In Name Without Description4 ms0044
Scenario: Creating Tag With Long Name With Valid Description13 ms0044
Scenario: Creating Tag With Long Name Without Description10 ms0044
Scenario: Creating Tag With Numbers In Name With Valid Description4 ms0044
Scenario: Creating Tag With Numbers In Name Without Description7 ms0044
Scenario: Creating Tag With Permitted Symbols In Name With Valid Description4 ms0044
Scenario: Creating Tag With Permitted Symbols In Name Without Description7 ms0044
Scenario: Creating Tag With Short Name With Valid Description6 ms0044
Scenario: Creating Tag With Short Name Without Description7 ms0044
Scenario: Creating Tag With Too Long Name With Valid Description5 ms0044
Scenario: Creating Tag With Too Long Name Without Description9 ms0044
Scenario: Creating Tag With Too Short Name With Valid Description5 ms0044
Scenario: Creating Tag With Too Short Name Without Description6 ms0044
Scenario: Creating Tag Without a Name And With Valid Description4 ms0044
Scenario: Creating Tag Without a Name And Without Description6 ms0044
Scenario: Creating Tags And Than Setting Tag Service So It Does Not Allow Tags8 ms0011+1111+11
Scenario: Creating Tags And Then Changing Tag Service Values8 ms0010+1010+10
Scenario: Creating Tags Under Account That Allows Infinite Child Devices13 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 Tags14 ms0012+1212+12
Scenario: Creating Unique Group With Long Description6 ms006+66+6
Scenario: Creating Unique Group With Non-unique Description6 ms007+77+7
Scenario: Creating Unique Group With Short Description3 ms006+66+6
Scenario: Creating Unique Group With Unique Description7 ms006+66+6
Scenario: Creating Unique Group Without Description12 ms006+66+6
Scenario: Creating Unique Tag With Long Description6 ms0044
Scenario: Creating Unique Tag With Non-unique Description4 ms0055
Scenario: Creating Unique Tag With Short Description5 ms0044
Scenario: Creating Unique Tag With Unique Description8 ms0044
Scenario: Creating Unique Tag Without Description20 ms0044
Scenario: Creating Users And Than Setting User Service So It Does Not Allow Users14 ms0011+1111+11
Scenario: Creating Users And Then Changing User Service Values10 ms0010+1010+10
Scenario: Creating Users Under Account That Allows Infinite Child Users9 ms0010+1010+10
Scenario: Creating Users Under Account That Does Not Allow Users8 ms009+99+9
Scenario: Creating Users Under Account That Has Limited Child Users7 ms0012+1212+12
Scenario: Creating Valid Endpoint6 ms006+66+6
Scenario: Creating a Access Group with invalid special symbols in name3 ms0044
Scenario: Creating a Device With Permitted Symbols in its Display Name4 ms007+77+7
Scenario: Creating a Device With Unique Display Name10 ms008+88+8
Scenario: Creating a job with name only10 ms0066
Scenario: Creating a job with null name17 ms0055
Scenario: Creating a job without name with valid description4 ms0055
Scenario: Creating a new PASSWORD Credential meeting a custom length requirement10 ms0044
Scenario: Creating a new PASSWORD Credential meeting the standard length requirement23 ms0033
Scenario: Creating a new PASSWORD Credential not meeting a custom length requirement9 ms0055
Scenario: Creating a new PASSWORD Credential not meeting the standard length requirement10 ms0044
Scenario: Creating a role name with allowed symbols in its name4 ms0055
Scenario: Creating a role with 255 characters long description3 ms0055
Scenario: Creating a role with a name and description that contain digits only3 ms0055
Scenario: Creating a role with forbidden symbols in its name1 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 enough6 ms0055
Scenario: Creating a role with special characters in the description5 ms0044
Scenario: Creating a role with the name that contains digits4 ms0055
Scenario: Creating a role with too long name0 ms0055
Scenario: Creating a role with too short name2 ms0055
Scenario: Creating a role with valid name and with too long description4 ms0033
Scenario: Creating a role wtih 255 characters long name4 ms0055
Scenario: Creating a single device with case sensitive clientID6 ms0055
Scenario: Creating a single device with clientID that contains 255 characters6 ms0055
Scenario: Creating a single device with clientID that contains 256 characters3 ms0044
Scenario: Creating a single device with clientID that contains invalid character2 ms0044
Scenario: Creating a single device with clientID that contains invalid characters5 ms0044
Scenario: Creating a single device with spaces in clientID6 ms0055
Scenario: Creating a single device with valid clientID4 ms0055
Scenario: Creating a valid Access Group with numbers in name5 ms0055
Scenario: Creating a valid Access Group with only numbers in name7 ms0055
Scenario: Creating a valid Access Group with unique name4 ms0055
Scenario: Creating a valid Access Group with valid special symbols in name3 ms0055
Scenario: Creating a valid role5 ms0055
Scenario: Creating an Access Group with empty name6 ms0044
Scenario: Creating an Access Group with long name7 ms0055
Scenario: Creating an Access Group with short name8 ms0055
Scenario: Creating an Access Group with too long name5 ms0044
Scenario: Creating an Access Group with too short name8 ms0044
Scenario: Creating an Access Group without name and with description4 ms0044
Scenario: Creating and Deleting Endpoint Two Times15 ms0025+2525+25
Scenario: Creating index with regular user18 ms002525
Scenario: Creating job with invalid symbols in name without description0 ms0044
Scenario: Creating job with long name and valid description7 ms0066
Scenario: Creating job with long name without description13 ms0066
Scenario: Creating job with numbers in name and valid description5 ms0066
Scenario: Creating job with numbers in name without description8 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 description11 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 description15 ms0055
Scenario: Creating job without name and without description5 ms0055
Scenario: Creating new device and tagging it with specific Tag15 ms0014+1414+14
Scenario: Creating new device, tagging it with specific Tag and then deleting this Tag12 ms0016+1616+16
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 description8 ms0077
Scenario: Creating two device with the same clientID4 ms0055
Scenario: Creating two indexes with daily index15 ms001717
Scenario: Creating two indexes with hourly index15 ms001717
Scenario: Creating two indexes with weekly index15 ms001717
Scenario: Creating two roles with the same description3 ms0066
Scenario: Creating two roles with the same name3 ms0077
Scenario: Creating unique Access Group with long description4 ms0055
Scenario: Creating unique Access Group with non-unique description4 ms0066
Scenario: Creating unique Access Group with numbers in description4 ms0055
Scenario: Creating unique Access Group with only numbers in description7 ms0055
Scenario: Creating unique Access Group with short description4 ms0055
Scenario: Creating unique Access Group with special symbols in description32 ms2114
Scenario: Creating unique Access Group with unique description7 ms0055
Scenario: Creating unique job with long description6 ms0066
Scenario: Creating unique job with non-unique description6 ms001010
Scenario: Creating unique job with short description7 ms0066
Scenario: Creating user21 ms0055
Scenario: Creation of access role with neither acess info and role entities5 ms0012+1212+12
Scenario: Creation of access role without an acess info entity6 ms0012+1212+12
Scenario: D1 Device publish to CTRL_ACC_REPLY13 ms0099
Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI7 ms0099
Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed16 ms0099
Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed14 ms0077
Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY15 ms0099
Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY14 ms0099
Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account8 ms0099
Scenario: D5 Device subscribe - publish - admin on CTRL_ACC14 ms0099
Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI20 ms0099
Scenario: D7 Device publish to ACL_DATA_ACC is not allowed15 ms0099
Scenario: D8 Device create sub-topic on ACL_DATA_ACC is not allowed14 ms0099
Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed6 ms0088
Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed18 ms0099
Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI21 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 allowed5 ms0088
Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY20 ms0099
Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY24 ms0099
Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account8 ms0099
Scenario: DM5 Data manage publish to CTRL_ACC is not allowed15 ms0099
Scenario: DM6 Data manage create sub-topic on CTRL_ACC is not allowed11 ms0099
Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed7 ms0088
Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI6 ms0099
Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC12 ms0099
Scenario: DV1 Data view publish to CTRL_ACC_REPLY15 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 allowed12 ms001010
Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed15 ms0099
Scenario: DV13 Data view create sub-topic on ACL_CTRL_ACC_CLI is not allowed16 ms0099
Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed16 ms0099
Scenario: DV17 Data view subscribe on ACL_CTRL_ACC_NOTIFY is not allowed11 ms0088
Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY17 ms0099
Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY11 ms0099
Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account7 ms0099
Scenario: DV5 Data view publish to CTRL_ACC is not allowed19 ms0099
Scenario: DV6 Data view create sub-topic on CTRL_ACC is not allowed16 ms0099
Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed6 ms0088
Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI18 ms0099
Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed13 ms0099
Scenario: Decreasing MaxNumberChildAccounts When Sub-accounts Are Already Created6 ms0015+1515+15
Scenario: Delete Kapua system user7 ms0055
Scenario: Delete a access info entity with permissions and roles13 ms0017+1717+17
Scenario: Delete a connection from the database3 ms0088
Scenario: Delete a group from the database8 ms0010+1010+10
Scenario: Delete a group from the database - Unknown group ID7 ms006+66+6
Scenario: Delete a job10 ms0011+1111+11
Scenario: Delete a job execution item3 ms009+99+9
Scenario: Delete a job execution item twice6 ms0010+1010+10
Scenario: Delete a job twice6 ms0010+1010+10
Scenario: Delete a non existent event6 ms0077
Scenario: Delete a non existing connection5 ms0077
Scenario: Delete a non existing permission entity4 ms0016+1616+16
Scenario: Delete a non existing role entry7 ms0011+1111+11
Scenario: Delete a non-existing step3 ms0013+1313+13
Scenario: Delete a nonexistent domain4 ms005+55+5
Scenario: Delete a step definition6 ms0088
Scenario: Delete a step definition twice5 ms0077
Scenario: Delete access role from user11 ms0012+1212+12
Scenario: Delete an access info entity twice9 ms0011+1111+11
Scenario: Delete an access info entity using the wrong scope ID8 ms0011+1111+11
Scenario: Delete an existing access info entity7 ms0012+1212+12
Scenario: Delete an existing access permission entity4 ms0015+1515+15
Scenario: Delete an existing access role entry6 ms0022+2222+22
Scenario: Delete an existing account5 ms0055
Scenario: Delete an existing device from the registry8 ms0044
Scenario: Delete an existing event5 ms0099
Scenario: Delete an existing role8 ms0010+1010+10
Scenario: Delete an existing role twice9 ms0016+1616+16
Scenario: Delete an existing step7 ms0012+1212+12
Scenario: Delete items based on query results49 ms008484
Scenario: Delete items by date ranges1.2 sec00132132
Scenario: Delete items by the datastore ID36 ms006666
Scenario: Delete middle child expiration5 ms0015+1515+15
Scenario: Delete nonexisting account3 ms0044
Scenario: Delete nonexisting role permission17 ms0013+1313+13
Scenario: Delete parent expiration6 ms0014+1414+14
Scenario: Delete permissions from role13 ms0018+1818+18
Scenario: Delete role permissions6 ms0010+1010+10
Scenario: Delete scheduler6 ms0088
Scenario: Delete scheduler which doesn't exist8 ms0055
Scenario: Delete the Kapua system account6 ms0055
Scenario: Delete the last created domain entry12 ms008+88+8
Scenario: Delete user9 ms0066
Scenario: Delete user that doesn't exist4 ms0055
Scenario: Deleting "Cron Schedule" Triggering8 ms0013+1313+13
Scenario: Deleting "Device Schedule" Triggering6 ms0011+1111+11
Scenario: Deleting "Interval Schedule" Triggering8 ms0013+1313+13
Scenario: Deleting Device With Disabled Status11 ms0010+1010+10
Scenario: Deleting Device With Enabled Status21 ms0010+1010+10
Scenario: Deleting Endpoint Domain Name And Leaving it Empty8 ms008+88+8
Scenario: Deleting Endpoint Which Does Not Exist4 ms006+66+6
Scenario: Deleting Existing Group8 ms008+88+8
Scenario: Deleting Existing Group And Creating It Again With Same Name14 ms0012+1212+12
Scenario: Deleting Existing Tag And Creating It Again With Same Name4 ms0077
Scenario: Deleting Group's Name And Leaving It Empty Without Changing Description7 ms008+88+8
Scenario: Deleting Non-Existent Tag3 ms0077
Scenario: Deleting Tag From Device4 ms0088
Scenario: Deleting Tag's Name And Leaving It Empty Without Description4 ms0055
Scenario: Deleting Unexisitng Group25 ms0011+1111+11
Scenario: Deleting a Permission10 ms0021+2121+21
Scenario: Deleting a non-existing Access Group4 ms0066
Scenario: Deleting a role twice2 ms0077
Scenario: Deleting admin role16 ms007+77+7
Scenario: Deleting an existing Access Group3 ms0055
Scenario: Deleting an existing Access Group and creating it again with the same name5 ms0077
Scenario: Deleting an existing role1 ms0066
Scenario: Deleting default permissions from admin role10 ms0012+1212+12
Scenario: Deleting existing tag4 ms0099
Scenario: Deleting role after adding it to user10 ms0014+1414+14
Scenario: Deleting role after it has been added to user in child account10 ms0016+1616+16
Scenario: Deleting user in account that is higher in hierarchy24 ms0023+2323+23
Scenario: Deleting user in account that is lower in hierarchy15 ms0024+2424+24
Scenario: Device connection update3 ms0077
Scenario: Device factory sanity checks3 ms0022
Scenario: Device queries4 ms001010
Scenario: Device query - find by BIOS version5 ms0077
Scenario: Domain entry query5 ms005+55+5
Scenario: Domain with null actions7 ms005+55+5
Scenario: Domain with null name11 ms005+55+5
Scenario: Domains with duplicate names5 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 ms0055
Scenario: Editing Access Group description to description with only numbers3 ms0055
Scenario: Editing Access Group description to description with special symbols3 ms0044
Scenario: Editing Access Group description to long description6 ms0055
Scenario: Editing Access Group description to non-unique one3 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 one6 ms0077
Scenario: Editing Access Group name to a too long one6 ms0055
Scenario: Editing Access Group name to empty name2 ms0055
Scenario: Editing Access Group name to name that contains numbers5 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 one4 ms0066
Scenario: Editing Access Group name to short one4 ms0077
Scenario: Editing Access Group name to too short one4 ms0055
Scenario: Editing Access Group name to valid one5 ms0077
Scenario: Editing Endpoint Domain Name So It Contains Invalid Symbols6 ms008+88+8
Scenario: Editing Endpoint Domain Name So It Contains Only Numbers7 ms008+88+8
Scenario: Editing Endpoint Domain Name So It Has Max Value8 ms007+77+7
Scenario: Editing Endpoint Domain Name So It Has Min Value6 ms007+77+7
Scenario: Editing Endpoint Domain Name To Non-unique Value7 ms009+99+9
Scenario: Editing Endpoint Domain Name To Unique Value7 ms007+77+7
Scenario: Editing Endpoint Port To Non-unique Value8 ms009+99+9
Scenario: Editing Endpoint Port To Unique Value16 ms007+77+7
Scenario: Editing Endpoint Schema And Leaving It Empty6 ms008+88+8
Scenario: Editing Endpoint Schema So It Contains "http://"7 ms008+88+8
Scenario: Editing Endpoint Schema So It Contains "https://"16 ms008+88+8
Scenario: Editing Endpoint Schema So It Contains Invalid Symbols3 ms008+88+8
Scenario: Editing Endpoint Schema So It Contains Only Numbers8 ms008+88+8
Scenario: Editing Endpoint Schema So It Has Max Length6 ms007+77+7
Scenario: Editing Endpoint Schema So It Has Min Length8 ms007+77+7
Scenario: Editing Endpoint Schema To Non-unique Value27 ms008+88+8
Scenario: Editing Endpoint Schema To Unique Value15 ms007+77+7
Scenario: Editing Endpoint Secure Field To Non-unique Value6 ms009+99+9
Scenario: Editing Endpoint Secure Field To Unique Value7 ms007+77+7
Scenario: Editing Endpoint To NULL Values7 ms0014+1414+14
Scenario: Editing Endpoint To Non-unique Endpoint6 ms0010+1010+10
Scenario: Editing Group's Name To Contain Numbers Without Changing Description7 ms007+77+7
Scenario: Editing Tag's Name To Contain Numbers Without Description6 ms0077
Scenario: Empty query results are supported7 ms008+88+8
Scenario: Event factory sanity checks4 ms0022
Scenario: Event service domain check4 ms0022
Scenario: Every account must have the default configuration items3 ms0033
Scenario: Execute possible docker steps to show its usage7 ms2+231+31033+33
Scenario: Executing Job And Then Restarting Device11 ms2+216+1627+2745+45
Scenario: Executing Job When Device Connected After End Date And Time14 ms0038+3838+38
Scenario: Executing Job When Device Connected After The Specified Start Date And Time54 ms2+26+630+3038+38
Scenario: Executing Job When Device Connected Before End Date And Time15 ms2+26+631+3139+39
Scenario: Executing Job When Device Connected Before The Specified Start Date And Time38 ms0037+3737+37
Scenario: Executing Job Without Steps30 ms0040+4040+40
Scenario: Extra long continuous test with multiple subscenarios with LOOSE default connection mode49 ms00419+419419+419
Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode40 ms00397+397397+397
Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode and no previously defined devices30 ms00305+305305+305
Scenario: Find a connection by its IDs4 ms0066
Scenario: Find a connection by its client ID5 ms0066
Scenario: Find a group entry in the database12 ms009+99+9
Scenario: Find a non existing event10 ms0066
Scenario: Find account by Id11 ms0044
Scenario: Find account by Ids9 ms0044
Scenario: Find account by name5 ms0044
Scenario: Find account by random Id5 ms0033
Scenario: Find all child accounts11 ms0033
Scenario: Find an access info entity11 ms0011+1111+11
Scenario: Find an access info entity by user ID7 ms0010+1010+10
Scenario: Find an event by its ID9 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.47 sec005858
Scenario: Find device by client ID5 ms0033
Scenario: Find device by registry ID4 ms0044
Scenario: Find last created permission5 ms0012+1212+12
Scenario: Find multiple users4 ms0055
Scenario: Find role by ID7 ms007+77+7
Scenario: Find self account by id6 ms0011+1111+11
Scenario: Find self account by id and scope id7 ms0011+1111+11
Scenario: Find self account by name9 ms0011+1111+11
Scenario: Find the last created domain entry6 ms005+55+5
Scenario: Find user by id6 ms0055
Scenario: Find user by its email4 ms0066
Scenario: Find user by its phone number4 ms0066
Scenario: Find user by name12 ms0055
Scenario: Find user by name that doesn't exist4 ms0033
Scenario: Find user with id and scope id that doesn't exist6 ms0033
Scenario: Finding all messages by selecting all metrics0.44 sec004040
Scenario: Finding correct number of messages by corresponding two metrics0.45 sec005252
Scenario: Finding messages with incorrect metric parameters0.44 sec007272
Scenario: Finding user by expiration date in the future4 ms0055
Scenario: Finding user by expiration date in the past4 ms0066
Scenario: Finding user by expiration date in the present5 ms0066
Scenario: Generic connection query6 ms0088
Scenario: Get metadata7 ms0033
Scenario: Group with a null name11 ms007+77+7
Scenario: Handle account creation25 ms0033
Scenario: Handle duplicate account names15 ms0055
Scenario: Handle null account name7 ms0044
Scenario: Handling of 2 birth messages15 ms0012+1212+12
Scenario: Handling of a disconnect message from a non existing device9 ms0010+1010+10
Scenario: Have Two Devices in The Same Group Without Description8 ms0013+1313+13
Scenario: I try to find a non-existing connection3 ms0066
Scenario: If user credential expiration date is before today, user can not login7 ms0014+1414+14
Scenario: If user credential expiration date is today, user can not login it is day inclusive6 ms0014+1414+14
Scenario: If user credential expiration date is tomorrow, user can login3 ms0013+1313+13
Scenario: If user credential is in state disabled, user can not login2 ms0014+1414+14
Scenario: If user credential is in state enabled, user can login6 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 reached17 ms0013+1313+13
Scenario: If user expiration date is tomorrow, user can login7 ms0012+1212+12
Scenario: Init Security Context for all scenarios0.17 sec0048+4848+48
Scenario: Installing a package14 ms0013+1313+13
Scenario: Interval Job" Schedule With Too Long Name17 ms0011+1111+11
Scenario: It must be possible to query for specific entries in the role database18 ms008+88+8
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 name4 ms009+99+9
Scenario: Job with a null name2 ms008+88+8
Scenario: Job with a null scope ID10 ms009+99+9
Scenario: Job with an empty name4 ms008+88+8
Scenario: List Endpoints Created From Sub-Account15 ms2+223+231+126+26
Scenario: List Endpoints From "kapua-sys" Account28 ms2+24+45+511+11
Scenario: List Endpoints From Sub-Account Of Another Sub-Account10 ms2+223+231+126+26
Scenario: List Endpoints From Sub-account5 ms2+212+121+115+15
Scenario: MetricsInfo client ID and topic data based on the client id41 ms003434
Scenario: MetricsInfo last published date31 ms004848
Scenario: Modify a role that was deleted11 ms009+99+9
Scenario: Modify an existing account4 ms0044
Scenario: Modify last child expiration so that it still expires before parent8 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 parent10 ms0015+1515+15
Scenario: Modify nonexisting account7 ms0066
Scenario: Modify parent expiration so that it still expires after child34 ms0014+1414+14
Scenario: Modify parent expiration to before child expiration7 ms0015+1515+15
Scenario: Modifying Sub-account of a different parent account11 ms0025+2525+25
Scenario: Moving Device From One Group With Description to Another5 ms0014+1414+14
Scenario: Nameless role entry8 ms007+77+7
Scenario: Negative scenario when client connects twice with same client id35 ms0011+1111+11
Scenario: New connection with reserved ID13 ms0034+3434+34
Scenario: Permission factory sanity checks5 ms003+33+3
Scenario: Positive scenario without stealing link24 ms0012+1212+12
Scenario: Query based on message ordering40 ms002020
Scenario: Query based on metrics ordering27 ms002020
Scenario: Query before schema search12 ms008282
Scenario: Query for a specific group by name13 ms0016+1616+16
Scenario: Query for all the access info entities of a specific user4 ms0018+1818+18
Scenario: Query for all the access info entities of an invalid user8 ms0010+1010+10
Scenario: Query for executions of a specific job5 ms0019+1919+19
Scenario: Query for jobs with specified name6 ms009+99+9
Scenario: Query for step definitions5 ms0077
Scenario: Query user6 ms0066
Scenario: Querying Other Items With All Account Permissions17 ms0039+3939+39
Scenario: Regular connection6 ms0077
Scenario: Regular creation of Access Role entity9 ms0014+1414+14
Scenario: Regular domain11 ms005+55+5
Scenario: Regular group in random scope12 ms007+77+7
Scenario: Regular group in root scope5 ms007+77+7
Scenario: Regular job creation3 ms0010+1010+10
Scenario: Regular job execution creation7 ms008+88+8
Scenario: Regular role creation5 ms009+99+9
Scenario: Regular step creation3 ms0012+1212+12
Scenario: Regular step definition creation6 ms0077
Scenario: Regular step definition with a property list5 ms0044
Scenario: Reset Security Context for all scenarios0.16 sec0048+4848+48
Scenario: Restarting a job with Asset Write and Bundle Start steps28 ms0028+2828+28
Scenario: Restarting a job with Command Execution and Bundle Start steps20 ms0028+2828+28
Scenario: Restarting a job with Configuration Put and Bundle Start steps18 ms0028+2828+28
Scenario: Restarting a job with Package Uninstall and Bundle Start steps30 ms0028+2828+28
Scenario: Restarting a job with invalid Configuration Put and multiple devices two times38 ms0033+3333+33
Scenario: Restarting a job with invalid Configuration Put step two times22 ms0036+3636+36
Scenario: Restarting a job with invalid Package Install step and multiple devices two times19 ms0031+3131+31
Scenario: Restarting a job with invalid Package Install step two times35 ms0034+3434+34
Scenario: Restarting a job with invalid Package Uninstall step and multiple devices two times42 ms0032+3232+32
Scenario: Restarting a job with invalid Package Uninstall step two times36 ms0034+3434+34
Scenario: Restarting a job with valid Configuration Put step and multiple devices two times40 ms0033+3333+33
Scenario: Restarting a job with valid Configuration Put step two times85 ms0036+3636+36
Scenario: Restarting a job with valid Package Install step and multiple devices two times34 ms0029+2929+29
Scenario: Restarting a job with valid Package Install step two times26 ms0034+3434+34
Scenario: Restarting a job with valid Package Uninstall step and multiple devices two times30 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 times31 ms0034+3434+34
Scenario: Restarting job With valid Asset Write step two times18 ms0036+3636+36
Scenario: Restarting job with Asset Write and Bundle Start steps and multiple devices20 ms0031+3131+31
Scenario: Restarting job with Asset Write step20 ms0025+2525+25
Scenario: Restarting job with Asset Write step and multiple devices24 ms0028+2828+28
Scenario: Restarting job with Bundle Start step28 ms0025+2525+25
Scenario: Restarting job with Bundle Start step and multiple devices26 ms0027+2727+27
Scenario: Restarting job with Bundle Stop and Bundle Start step and multiple devices21 ms0031+3131+31
Scenario: Restarting job with Bundle Stop and Bundle Start steps22 ms0029+2929+29
Scenario: Restarting job with Bundle Stop step24 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 devices30 ms0031+3131+31
Scenario: Restarting job with Command Execution step30 ms0025+2525+25
Scenario: Restarting job with Command Execution step and multiple devices26 ms0027+2727+27
Scenario: Restarting job with Configuration Put and Bundle Start steps and multiple devices33 ms0031+3131+31
Scenario: Restarting job with Configuration Put step23 ms0025+2525+25
Scenario: Restarting job with Configuration Put step and multiple devices22 ms0027+2727+27
Scenario: Restarting job with Package Download/Install and Bundle Start steps and multiple devices42 ms0059+5959+59
Scenario: Restarting job with Package Download/Install step and multiple devices26 ms0027+2727+27
Scenario: Restarting job with Package Install step26 ms0025+2525+25
Scenario: Restarting job with Package Uninstall and Bundle start steps and multiple device28 ms0031+3131+31
Scenario: Restarting job with Package Uninstall step19 ms0025+2525+25
Scenario: Restarting job with Package Uninstall step and multiple device27 ms0027+2727+27
Scenario: Restarting job with invalid Asset Write step two times21 ms0036+3636+36
Scenario: Restarting job with invalid Bundle Start and Bundle Stop steps and multiple devices two times42 ms0041+4141+41
Scenario: Restarting job with invalid Bundle Start and Bundle Stop steps two times24 ms0043+4343+43
Scenario: Restarting job with invalid Bundle Start step and multiple devices two times38 ms0035+3535+35
Scenario: Restarting job with invalid Bundle Start step two times30 ms0037+3737+37
Scenario: Restarting job with invalid Bundle Stop step and multiple devices two times43 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 times31 ms0036+3636+36
Scenario: Restarting job with invalid Command Execution and Package Install steps and multiple devices two times36 ms0037+3737+37
Scenario: Restarting job with invalid Command Execution step and multiple devices two times89 ms0031+3131+31
Scenario: Restarting job with invalid Command Execution step two times31 ms0032+3232+32
Scenario: Restarting job with invalid Configuration Put And Command Execution steps two times29 ms0038+3838+38
Scenario: Restarting job with invalid Configuration Put and Command Execution steps and multiple devices two times31 ms0037+3737+37
Scenario: Restarting job with invalid Package Uninstall and Asset Write steps and multiple devices two times46 ms0038+3838+38
Scenario: Restarting job with invalid Package Uninstall and Asset Write steps two times19 ms0040+4040+40
Scenario: Restarting job with two Bundle Start steps23 ms0029+2929+29
Scenario: Restarting job with two Bundle Start steps and multiple devices19 ms0031+3131+31
Scenario: Restarting job with valid Asset Write step and multiple devices two times34 ms0034+3434+34
Scenario: Restarting job with valid Bundle Start And Bundle Stop steps two times44 ms0043+4343+43
Scenario: Restarting job with valid Bundle Start and Bundle Stop steps and multiple devices two times24 ms0041+4141+41
Scenario: Restarting job with valid Bundle Start step and multiple devices two times38 ms0035+3535+35
Scenario: Restarting job with valid Bundle Start step two times32 ms0037+3737+37
Scenario: Restarting job with valid Bundle Stop step and multiple devices two times55 ms0035+3535+35
Scenario: Restarting job with valid Bundle Stop step two times49 ms0037+3737+37
Scenario: Restarting job with valid Command Execution and Package Install steps and multiple devices two times31 ms0033+3333+33
Scenario: Restarting job with valid Command Execution and Package Install steps two times41 ms0034+3434+34
Scenario: Restarting job with valid Command Execution step and multiple devices two times41 ms0031+3131+31
Scenario: Restarting job with valid Command Execution step two times46 ms0032+3232+32
Scenario: Restarting job with valid Configuration Put and Command Execution steps and multiple devices two times32 ms0037+3737+37
Scenario: Restarting job with valid Configuration Put and Command Execution steps two times28 ms0038+3838+38
Scenario: Restarting job with valid Package Uninstall and Asset Write steps and multiple devices two times47 ms0036+3636+36
Scenario: Restarting job with valid Package Uninstall and Asset Write steps two times42 ms0038+3838+38
Scenario: Role creator sanity checks6 ms002+22+2
Scenario: Role entry with no actions8 ms006+66+6
Scenario: Role object equality check5 ms002+22+2
Scenario: Role service related objects sanity checks6 ms004+44+4
Scenario: Search By Client ID And Get Multiple Matches22 ms0037+3737+37
Scenario: Search By Client ID And Get No Matches15 ms0010+1010+10
Scenario: Search By Client ID And Get One Match8 ms008+88+8
Scenario: Search By Client ID and Display Name16 ms0012+1212+12
Scenario: Search By Client ID and Serial Number5 ms0012+1212+12
Scenario: Search By Client ID and Status10 ms0012+1212+12
Scenario: Search By Client ID, Display Name and Serial Number16 ms0012+1212+12
Scenario: Search By Client ID, Display Name and Status10 ms0012+1212+12
Scenario: Search By Client ID, Display Name, Serial Number and Status20 ms0012+1212+12
Scenario: Search By Device Status And Get No Matches7 ms008+88+8
Scenario: Search By Device's Display Name And Get One Match13 ms008+88+8
Scenario: Search By Display Name and Serial Number8 ms0012+1212+12
Scenario: Search By Display Name and Status7 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 Matches9 ms008+88+8
Scenario: Search By One Letter Of Display Name6 ms008+88+8
Scenario: Search By One Letter Of Serial Number14 ms0012+1212+12
Scenario: Search By Serial Number And Get Multiple Matches10 ms0014+1414+14
Scenario: Search By Serial Number And Get No Matches12 ms0010+1010+10
Scenario: Search By Serial Number And Get One Match8 ms0011+1111+11
Scenario: Search By Serial Number and Status20 ms0012+1212+12
Scenario: Search By Serial Number, Display Name and Status5 ms0012+1212+12
Scenario: Search By Specific Serial Number7 ms0010+1010+10
Scenario: Search By Status And Get Multiple Matches8 ms0010+1010+10
Scenario: Search by Device Status And Get One Match7 ms0010+1010+10
Scenario: Search for a non existent client ID3 ms0066
Scenario: Search for an access info entity by an incorrect user ID9 ms0011+1111+11
Scenario: Search the role database for a random ID8 ms007+77+7
Scenario: Send BIRTH message and then DC message26 ms0015+1515+15
Scenario: Send BIRTH message and then DC message while broker ip is NOT set40 ms006+66+6
Scenario: Send BIRTH message and then DC message while broker ip is set by System44 ms008+88+8
Scenario: Send BIRTH message and then DC message while broker ip is set by config file63 ms008+88+8
Scenario: Set a correct minimum for password length9 ms0033
Scenario: Set an incorrect minimum for password length7 ms0066
Scenario: Set environment variables0.15 sec0061+4961+49
Scenario: Setting InfiniteChildAccounts To False And Increasing MaxNumberChildAccounts When Sub-accounts Are Already Created7 ms0014+1414+14
Scenario: Setting InfiniteChildAccounts To False When Sub-accounts Are Already Created14 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 Seconds11 ms0015+1515+15
Scenario: Setting Lockout Duration To Negative Value7 ms007+77+7
Scenario: Setting Max Failures To 011 ms0015+1515+15
Scenario: Setting Max Failures To 112 ms0015+1515+15
Scenario: Setting Max Failures To 10012 ms0015+1515+15
Scenario: Setting Max Failures To Negative Value18 ms007+77+7
Scenario: Setting Reset After Login Counter To 0 Seconds10 ms0017+1717+17
Scenario: Setting Reset After Login Counter To Negative Value3 ms007+77+7
Scenario: Setting configuration without mandatory items must raise an error4 ms0055
Scenario: Simple create6 ms0011+1111+11
Scenario: Simple positive scenario for creating daily index13 ms001414
Scenario: Simple positive scenario for creating default - weekly index18 ms001212
Scenario: Simple positive scenario for creating hourly index13 ms001414
Scenario: Start broker for all scenarios0.32 sec0044+3244+32
Scenario: Start datastore for all scenarios0.7 sec0030+1830+18
Scenario: Start event broker for all scenarios0.43 sec0050+3850+38
Scenario: Starting a job with Asset Write and Bundle Start steps31 ms0036+3636+36
Scenario: Starting a job with Asset Write step21 ms0025+2525+25
Scenario: Starting a job with Bundle Start step26 ms0034+3434+34
Scenario: Starting a job with Bundle Stop and Bundle Start steps24 ms0039+3939+39
Scenario: Starting a job with Bundle Stop step15 ms0035+3535+35
Scenario: Starting a job with Command Execution and Bundle Start steps22 ms0037+3737+37
Scenario: Starting a job with Command Execution step21 ms0025+2525+25
Scenario: Starting a job with Configuration Put and Bundle Start steps27 ms0037+3737+37
Scenario: Starting a job with Configuration Put step23 ms0025+2525+25
Scenario: Starting a job with Package Install and Bundle Start steps23 ms0039+3939+39
Scenario: Starting a job with Package Install step25 ms0032+3232+32
Scenario: Starting a job with Package Uninstall and Bundle Start steps31 ms0036+3636+36
Scenario: Starting a job with Package Uninstall step20 ms0033+3333+33
Scenario: Starting a job with invalid Asset Write step24 ms0031+3131+31
Scenario: Starting a job with invalid Asset Write step and multiple targets48 ms0029+2929+29
Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps28 ms0036+3636+36
Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps and multiple devices30 ms0035+3535+35
Scenario: Starting a job with invalid Bundle Start step43 ms0031+3131+31
Scenario: Starting a job with invalid Bundle Stop step24 ms0031+3131+31
Scenario: Starting a job with invalid Bundle Stop step and multiple devices39 ms0029+2929+29
Scenario: Starting a job with invalid Command Execution step28 ms0027+2727+27
Scenario: Starting a job with invalid Configuration Put step20 ms0030+3030+30
Scenario: Starting a job with invalid Configuration Put step and multiple devices46 ms0028+2828+28
Scenario: Starting a job with invalid Package Install step40 ms0029+2929+29
Scenario: Starting a job with invalid Package Install step and multiple devices26 ms0026+2626+26
Scenario: Starting a job with invalid Package Uninstall and Asset Write steps29 ms0034+3434+34
Scenario: Starting a job with invalid Package Uninstall and Asset Write steps and multiple devices63 ms0032+3232+32
Scenario: Starting a job with invalid Package Uninstall step24 ms0029+2929+29
Scenario: Starting a job with invalid Package Uninstall step and multiple targets17 ms0026+2626+26
Scenario: Starting a job with two Bundle Start steps21 ms0039+3939+39
Scenario: Starting a job with valid Asset Write step34 ms0031+3131+31
Scenario: Starting a job with valid Asset Write step and multiple targets31 ms0029+2929+29
Scenario: Starting a job with valid Bundle Start and Bundle Stop steps58 ms0036+3636+36
Scenario: Starting a job with valid Bundle Start and Bundle Stop steps and multiple devices40 ms0034+3434+34
Scenario: Starting a job with valid Bundle Start step29 ms0031+3131+31
Scenario: Starting a job with valid Bundle Stop step35 ms0031+3131+31
Scenario: Starting a job with valid Bundle Stop step and multiple devices39 ms0029+2929+29
Scenario: Starting a job with valid Command Execution step70 ms0027+2727+27
Scenario: Starting a job with valid Configuration Put step38 ms0031+3131+31
Scenario: Starting a job with valid Configuration Put step and multiple devices36 ms0026+2626+26
Scenario: Starting a job with valid Package Install step29 ms0029+2929+29
Scenario: Starting a job with valid Package Install step and multiple devices43 ms0026+2626+26
Scenario: Starting a job with valid Package Uninstall and Asset Write steps30 ms0033+3333+33
Scenario: Starting a job with valid Package Uninstall and Asset Write steps and multiple devices40 ms0032+3232+32
Scenario: Starting a job with valid Package Uninstall step38 ms0030+3030+30
Scenario: Starting a job with valid Package Uninstall step and multiple targets29 ms0026+2626+26
Scenario: Starting and stopping the simulator should create a device entry and properly set its status6 ms0020+2020+20
Scenario: Starting job with Asset Write and Bundle Start steps and multiple devices27 ms0032+3232+32
Scenario: Starting job with Asset Write step and multiple devices31 ms0028+2828+28
Scenario: Starting job with Bundle Start step and multiple devices31 ms0028+2828+28
Scenario: Starting job with Bundle Stop and Bundle Start step and multiple devices34 ms0032+3232+32
Scenario: Starting job with Bundle Stop step and multiple devices21 ms0028+2828+28
Scenario: Starting job with Command Execution and Bundle Start steps and multiple devices19 ms0032+3232+32
Scenario: Starting job with Command Execution step and multiple devices24 ms0028+2828+28
Scenario: Starting job with Configuration Put and Bundle Start steps and multiple devices23 ms0032+3232+32
Scenario: Starting job with Configuration Put step and multiple devices23 ms0028+2828+28
Scenario: Starting job with Package Download/Install and Bundle Start steps and multiple devices24 ms0038+3838+38
Scenario: Starting job with Package Download/Install step and multiple devices50 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 device28 ms0027+2727+27
Scenario: Starting job with invalid Bundle Start step and multiple devices53 ms0029+2929+29
Scenario: Starting job with invalid Command Execution and Package Install steps34 ms0031+3131+31
Scenario: Starting job with invalid Command Execution step and multiple devices0.11 sec0028+2828+28
Scenario: Starting job with invalid Command Execution, invalid Package Install steps and multiple devices54 ms0029+2929+29
Scenario: Starting job with invalid Configuration Put and Command Execution steps25 ms0032+3232+32
Scenario: Starting job with invalid Configuration Put and Command Execution steps and multiple devices34 ms0031+3131+31
Scenario: Starting job with two Bundle Start steps and multiple devices23 ms0032+3232+32
Scenario: Starting job with valid Bundle Start step and multiple devices32 ms0029+2929+29
Scenario: Starting job with valid Command Execution and Package Install steps31 ms0031+3131+31
Scenario: Starting job with valid Command Execution step and multiple devices42 ms0026+2626+26
Scenario: Starting job with valid Command Execution, valid Package Install steps and multiple devices35 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 devices50 ms0030+3030+30
Scenario: Stealing link scenario21 ms0028+2828+28
Scenario: Step definition factory sanity checks5 ms0022
Scenario: Step definition with a duplicate name6 ms0066
Scenario: Step definition with a null name6 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 ID11 ms0012+1212+12
Scenario: Stop broker after all scenarios0.35 sec0046+3446+34
Scenario: Stop datastore after all scenarios0.23 sec0030+1830+18
Scenario: Stop event broker for all scenarios0.4 sec0050+3850+38
Scenario: Stop job with multiple Asset Write and Package Install steps and one target37 ms0037+3737+37
Scenario: Stop job with multiple Bundle Start and Package Install steps and one target59 ms0037+3737+37
Scenario: Stop job with multiple Bundle Stop and Package Uninstall steps and one target54 ms0037+3737+37
Scenario: Stop job with multiple Command Execution and Package Install steps and one target24 ms0034+3434+34
Scenario: Stop job with multiple Configuration Put and Package Uninstall steps and one target28 ms0035+3535+35
Scenario: Stop job with multiple targets and Asset Write and Package Install steps and one target53 ms0037+3737+37
Scenario: Stop job with multiple targets and Bundle Start and Package Install steps28 ms0036+3636+36
Scenario: Stop job with multiple targets and Bundle Stop and Package Uninstall steps46 ms0037+3737+37
Scenario: Stop job with multiple targets and Command Execution and Package Install steps59 ms0034+3434+34
Scenario: Stop job with multiple targets and Configuration Put and Package Uninstall steps45 ms0037+3737+37
Scenario: Test LOOSE user coupling on single connection13 ms0028+2828+28
Scenario: Test LOOSE user coupling with 3 connections12 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 user15 ms0063+6363+63
Scenario: Test STRICT user coupling with user change allowed on single connection15 ms0036+3636+36
Scenario: Test account query5 ms0044
Scenario: Test the message store with server timestamp indexing33 ms002626
Scenario: Test the message store with timestamp indexing29 ms002626
Scenario: The Client ID is case sensitive3 ms0088
Scenario: To be defined4 ms0013+1313+13
Scenario: Translating "CommandRequestMessage" to "KuraRequestMessage"44 ms0044
Scenario: Translating CommandRequestMessage to null9 ms0044
Scenario: Translating empty message to empty message9 ms0044
Scenario: Translating from "AssetRequestMessage" to "AssetResponseMessage"6 ms0044
Scenario: Translating invalid jms data message with valid channel, body and metrics into kura data message3 ms0055
Scenario: Translating invalid kura data message with valid channel, body and metrics into jms message3 ms0055
Scenario: Translating invalid kura data message with valid channel, body and metrics into mqtt message5 ms0055
Scenario: Translating kura data message with null channel, and payload without body and with metrics2 ms0055
Scenario: Translating kura data message with valid channel and with null payload5 ms0055
Scenario: Translating kura data message with valid channel and without body and metrics into jms message4 ms0055
Scenario: Translating kura data message with valid channel, and with null payload3 ms0055
Scenario: Translating kura data message with valid channel, body and metrics into jms message3 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 message5 ms0055
Scenario: Translating null to KuraRequestMessage11 ms0044
Scenario: Translating of jms message with empty payload and invalid topic that contain only userName into kura data message2 ms0055
Scenario: Translating of jms message with empty payload and valid topic into kura data message3 ms0066
Scenario: Translating of jms message with invalid payload and valid topic into kura data message4 ms0066
Scenario: Translating of jms message with valid payload and valid topic into kura data message6 ms0066
Scenario: Translating of mqtt message with invalid payload and invalid topic into kura data message4 ms0055
Scenario: Translating of mqtt message with invalid payload and with null topic into kura data message4 ms0055
Scenario: Translation of kura data message with valid channel and without body and metrics into mqtt message4 ms0055
Scenario: Translation of kura data message with valid channel, body and metrics into mqtt message4 ms0055
Scenario: Translation of kura data message with valid channel, metrics and without body into mqtt message6 ms0055
Scenario: Translation of mqtt message with empty payload into kura data message7 ms0066
Scenario: Translation of mqtt message with invalid payload and invalid topic into kura response message5 ms0055
Scenario: Translation of mqtt message with invalid payload and valid topic into kura data message6 ms0066
Scenario: Translation of mqtt message with invalid payload and valid topic into kura response message11 ms0066
Scenario: Translation of mqtt message with valid payload and invalid topic into kura response message5 ms0055
Scenario: Translation of mqtt message with valid payload and valid topic into kura data message6 ms0066
Scenario: Translation of mqtt message with valid payload and valid topic into kura response message4 ms0066
Scenario: Try to add two different roles with same permissions19 ms0021+2121+21
Scenario: Try to change an existing connection ID4 ms0077
Scenario: Try to create an access into entity with an invalid role id10 ms0012+1212+12
Scenario: Try to delete a non existing device from the registry4 ms0044
Scenario: Try to find a device with an invalid client ID6 ms0033
Scenario: Try to find a device with an invalid registry ID3 ms0033
Scenario: Try to find users granted to "admin" role17 ms0012+1212+12
Scenario: Try to find users that have assigned specific role16 ms0012+1212+12
Scenario: Try to modify the connection client ID4 ms0077
Scenario: Try to update the device client ID3 ms0044
Scenario: Uncorrect Login While Lockout Policy Is Disabled21 ms0017+1717+17
Scenario: Uncorrect Login While Lockout Policy Is Enabled11 ms0017+1717+17
Scenario: Update a group entry in the database8 ms009+99+9
Scenario: Update a group entry with a false ID11 ms0010+1010+10
Scenario: Update a job XML definition6 ms0010+1010+10
Scenario: Update a job description10 ms0010+1010+10
Scenario: Update a job name5 ms0010+1010+10
Scenario: Update a non existing device5 ms0055
Scenario: Update a nonexistent job4 ms0010+1010+10
Scenario: Update a nonexistent step definition5 ms0077
Scenario: Update a step definition name6 ms0077
Scenario: Update a step definition processor name7 ms0088
Scenario: Update a step definition target type8 ms0088
Scenario: Update existing role name5 ms008+88+8
Scenario: Update job id of an existing execution item6 ms009+99+9
Scenario: Update schedule which doesn't exist7 ms0055
Scenario: Update scheduler end date14 ms0099
Scenario: Update scheduler name11 ms0088
Scenario: Update scheduler start date8 ms0088
Scenario: Update the end time of an existing execution item4 ms0010+1010+10
Scenario: Update trigger definition6 ms0088
Scenario: Update user8 ms0077
Scenario: Update user that doesn't exist5 ms0055
Scenario: User locking itself out by using out login attempts6 ms0016+1616+16
Scenario: User locking itself out with failed attempts and not waiting to unlock6 ms0017+1717+17
Scenario: User locking itself out with failed attempts and waiting to unlock4 ms0017+1717+17
Scenario: User login with wrong pass, but with enough time between login failures3 ms0019+1919+19
Scenario: User not locking itself out by using less than max failed login attempts11 ms0017+1717+17
Scenario: Validate a device client based search with a null client ID3 ms0055
Scenario: Validate a device client based search with an empty client ID5 ms0055
Scenario: Validate a device client search with null scope3 ms0055
Scenario: Validate a device creator with a null client ID1 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 ID2 ms0066
Scenario: Validate a null creator3 ms0055
Scenario: Validate a null device2 ms0055
Scenario: Validate a null device count3 ms0055
Scenario: Validate a null device query2 ms0055
Scenario: Validate a regular creator3 ms0044
Scenario: Validate a regular device client search4 ms0044
Scenario: Validate a regular device count4 ms0044
Scenario: Validate a regular device query2 ms0044
Scenario: Validate a regular device search3 ms0055
Scenario: Validate deleting a device with a null device ID1 ms0066
Scenario: Validate deleting a device with a null scope ID3 ms0066
Scenario: Waiting For Lock Duration Time To Pass17 ms0019+1919+19
Scenario: Waiting For Reset After Login Counter To Pass5 ms0018+1818+18
empty) scope0 ms0044