Test Result : (root)

18 failures (-104) , 122 skipped (-1227)
16,502 tests (+11678)
Took 17 sec.

All Failed Tests

Test NameDurationAge
 Scenario: Creating unique Access Group with special symbols in description.Scenario: Creating unique Access Group with special symbols in description12 ms9
 Scenario: Creating unique Access Group with special symbols in description.Then I find the group with name "groupName53"12 ms9
 Scenario: Execute possible docker steps to show its usage.Given List images by name "kapua/kapua-broker:1.3.0-SNAPSHOT"2 ms3
 Scenario: Execute possible docker steps to show its usage.Scenario: Execute possible docker steps to show its usage3 ms3
 Scenario: Executing Job And Then Restarting Device.Scenario: Executing Job And Then Restarting Device5 ms9
 Scenario: Executing Job And Then Restarting Device.Then I find 4 device events3 ms9
 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 Time27 ms9
 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 ms9
 Scenario: List Endpoints Created From Sub-Account.And I create endpoint with schema "Schema1", domain "abc.com" and port 22222 ms3
 Scenario: List Endpoints Created From Sub-Account.Scenario: List Endpoints Created From Sub-Account16 ms3
 Scenario: List Endpoints From "kapua-sys" Account.Scenario: List Endpoints From "kapua-sys" Account2 ms3
 Scenario: List Endpoints From "kapua-sys" Account.Then I find 3 endpoints1 ms1
 Scenario: List Endpoints From Sub-Account Of Another Sub-Account.And I create endpoint with schema "Schema1", domain "abc.com" and port 22222 ms3
 Scenario: List Endpoints From Sub-Account Of Another Sub-Account.Scenario: List Endpoints From Sub-Account Of Another Sub-Account11 ms3
 Scenario: List Endpoints From Sub-account.And I create endpoint with schema "Schema1", domain "abc.com" and port 22222 ms3
 Scenario: List Endpoints From Sub-account.Scenario: List Endpoints From Sub-account4 ms3

All Tests

ClassDurationFail(diff)Skip(diff)Pass(diff)Total(diff)
Scenario: A fresh database must contain 1 default role in the root scope5 ms004+14+1
Scenario: A newly created account must have some metadata3 ms0033
Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic22 ms0088
Scenario: Access info service sanity checks5 ms0044
Scenario: Access service comparison sanity checks4 ms0033
Scenario: Account based ClientInfo data check41 ms0024+1224+12
Scenario: Account exactly on its expiration date8 ms001414
Scenario: Account name must not be mutable3 ms0066
Scenario: Account past its expiration date11 ms001414
Scenario: Account wide metrics check26 ms0028+1428+14
Scenario: Account with future expiration date6 ms001313
Scenario: Account with no expiration date8 ms001313
Scenario: Add Access Info domain permissions to new user13 ms0026+2626+26
Scenario: Add Account permissions to the role in child account23 ms0028+2828+28
Scenario: Add Credential domain permissions to new user15 ms0018+1818+18
Scenario: Add Datastore domain permissions to new user69 ms0019+1919+19
Scenario: Add Device Connection domain permissions to kapua-sys user13 ms0011+1111+11
Scenario: Add Device Connection domain permissions to new user18 ms0023+2323+23
Scenario: Add Device Event domain permissions to new user8 ms0016+1616+16
Scenario: Add Device domain permissions to new user9 ms0017+1717+17
Scenario: Add Domain domain permissions to kapua-sys user11 ms0017+1717+17
Scenario: Add Domain domain permissions to new user12 ms0032+3232+32
Scenario: Add Endpoint Permission To The User17 ms0030+3030+30
Scenario: Add Endpoint_info permissions to the role in child account10 ms0030+3030+30
Scenario: Add Group domain permissions to new user12 ms0017+1717+17
Scenario: Add Group permissions to the role in child account23 ms0026+2626+26
Scenario: Add Job domain permissions to new user11 ms0019+1919+19
Scenario: Add Role domain permissions to new user14 ms0017+1717+17
Scenario: Add Role permissions to the role in child account27 ms0026+2626+26
Scenario: Add Scheduler Permissions With Job Permissions12 ms0031+3131+31
Scenario: Add Scheduler Permissions Without Job Permissions10 ms0021+2121+21
Scenario: Add Scheduler permissions to the role in child account10 ms0036+3636+36
Scenario: Add Tag domain permissions to new user16 ms0015+1515+15
Scenario: Add Tag permissions to the role in child account9 ms0026+2626+26
Scenario: Add User domain permissions to new user13 ms0020+2020+20
Scenario: Add account permissions to the role19 ms0019+1919+19
Scenario: Add admin role to the user18 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" role15 ms0014+1414+14
Scenario: Add and delete Endpoint_info permissions from the "admin" role16 ms0014+1414+14
Scenario: Add and delete Group permissions from the "admin" role11 ms0014+1414+14
Scenario: Add and delete Job permissions from the "admin" role10 ms0014+1414+14
Scenario: Add and delete Role permissions from the "admin" role10 ms0014+1414+14
Scenario: Add and delete User permissions from the "admin" role12 ms0015+1515+15
Scenario: Add datastore permissions to the role10 ms0027+2727+27
Scenario: Add deleted role again11 ms0010+1010+10
Scenario: Add device event permissions to the role9 ms0032+3232+32
Scenario: Add device permissions to the role10 ms0019+1919+19
Scenario: Add device permissions to the role in child account14 ms0026+2626+26
Scenario: Add domain, user and access_info permissions to the role12 ms0023+2323+23
Scenario: Add endpoint_info permissions to the role10 ms0031+3131+31
Scenario: Add group permissions to the role10 ms0018+1818+18
Scenario: Add job permissions to the role11 ms0019+1919+19
Scenario: Add job permissions to the role in child account12 ms0026+2626+26
Scenario: Add role permissions to the role17 ms0019+1919+19
Scenario: Add same permission twice to the same role26 ms0014+1414+14
Scenario: Add same role to user twice39 ms0013+1313+13
Scenario: Add scheduler permissions to the role18 ms0031+3131+31
Scenario: Add tag permissions to the role11 ms0018+1818+18
Scenario: Add user permissions to the role12 ms0019+1919+19
Scenario: Add user permissions to the role in child account25 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 Value11 ms0010+1010+10
Scenario: Adding "Cron Job" Schedule With All Valid Parameters Except Cron Format6 ms0011+1111+11
Scenario: Adding "Cron Job" Schedule With End Date Only4 ms0010+1010+10
Scenario: Adding "Cron Job" Schedule With End Time before Start time7 ms0012+1212+12
Scenario: Adding "Cron Job" Schedule With Non-Unique End Date Parameter9 ms0016+1616+16
Scenario: Adding "Cron Job" Schedule With Non-Unique Start Date Parameter6 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 Parameter5 ms0010+1010+10
Scenario: Adding "Device Connect" Schedule With All Valid Parameters5 ms008+88+8
Scenario: Adding "Device Connect" Schedule With End Date Only9 ms0010+1010+10
Scenario: Adding "Device Connect" Schedule With End Time before Start time5 ms0011+1111+11
Scenario: Adding "Device Connect" Schedule With Max Length Name8 ms008+88+8
Scenario: Adding "Device Connect" Schedule With Min Length Name7 ms008+88+8
Scenario: Adding "Device Connect" Schedule With Name Only6 ms009+99+9
Scenario: Adding "Device Connect" Schedule With Non-Unique End Date Parameter6 ms0013+1313+13
Scenario: Adding "Device Connect" Schedule With Non-Unique Name17 ms0013+1313+13
Scenario: Adding "Device Connect" Schedule With Non-Unique Start Date Parameter5 ms0011+1111+11
Scenario: Adding "Device Connect" Schedule With Start Date Only5 ms0010+1010+10
Scenario: Adding "Device Connect" Schedule With the same Start and End time12 ms0011+1111+11
Scenario: Adding "Device Connect" Schedule Without Name7 ms0010+1010+10
Scenario: Adding "Device Connect" Schedule Without The Start Date Parameter7 ms009+99+9
Scenario: Adding "Empty" Tag To Device3 ms005+55+5
Scenario: Adding "Interval Job" Schedule With All Valid Parameters9 ms0010+1010+10
Scenario: Adding "Interval Job" Schedule With End Date Only6 ms0010+1010+10
Scenario: Adding "Interval Job" Schedule With End Time before Start time6 ms0012+1212+12
Scenario: Adding "Interval Job" Schedule With Max Length Name9 ms0010+1010+10
Scenario: Adding "Interval Job" Schedule With Min Length Name26 ms0010+1010+10
Scenario: Adding "Interval Job" Schedule With Name Only6 ms0010+1010+10
Scenario: Adding "Interval Job" Schedule With Non-Unique End Date Parameter6 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 Number8 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 time5 ms0012+1212+12
Scenario: Adding "Interval Job" Schedule Without Interval Number6 ms0011+1111+11
Scenario: Adding "Interval Job" Schedule Without The Start Date Parameter7 ms009+99+9
Scenario: Adding "Interval Job" Schedule Without a Name8 ms0011+1111+11
Scenario: Adding "admin" role to a user in a child account11 ms0014+1414+14
Scenario: Adding "admin" role to multiple users14 ms0018+1818+18
Scenario: Adding "admin" role twice9 ms0013+1313+13
Scenario: Adding Account:Delete permission to user in same scope20 ms0025+2525+25
Scenario: Adding Account:Delete permission to user in sub-account scope11 ms0030+3030+30
Scenario: Adding Account:Read and Account:Delete permissions to user in same scope10 ms0021+2121+21
Scenario: Adding Account:Read and Account:Write permissions to user in same scope11 ms0019+1919+19
Scenario: Adding Account:Read permission to user in same scope15 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 scope10 ms0023+2323+23
Scenario: Adding Account:Write permission to user in same scope11 ms0025+2525+25
Scenario: Adding Account:Write permission to user in sub-account scope10 ms0031+3131+31
Scenario: Adding Multiple Permissions To User15 ms0020+2020+20
Scenario: Adding One Permission To User14 ms0011+1111+11
Scenario: Adding Permissions To Child User7 ms0018+1818+18
Scenario: Adding Permissions To Parallel User12 ms0018+1818+18
Scenario: Adding Previously Deleted Permission12 ms0028+2828+28
Scenario: Adding Previously Deleted Tag From Device Again3 ms0011+1111+11
Scenario: Adding Regular Device to a Group With Description10 ms0010+1010+10
Scenario: Adding Regular Device to a Group Without a Description8 ms0012+1212+12
Scenario: Adding Regular Group Without Description to Device11 ms0010+1010+10
Scenario: Adding Regular Tag Without Description To Device5 ms006+66+6
Scenario: Adding Same Regular Group Without Description to Device11 ms0014+1414+14
Scenario: Adding Tag With Long Name Without Description To Device3 ms006+66+6
Scenario: Adding Tag With Numbers Without Description To Device5 ms006+66+6
Scenario: Adding Tag With Short Name Without Description To Device3 ms006+66+6
Scenario: Adding Tag With Special Symbols Without Description To Device3 ms006+66+6
Scenario: Adding all Account permissions to user in same scope12 ms0017+1717+17
Scenario: Adding all Account permissions to user in sub-account scope10 ms0024+2424+24
Scenario: Adding existing roles to user12 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 account10 ms0018+1818+18
Scenario: Adding same role twice to user in child account18 ms0015+1515+15
Scenario: Adding the same role to user twice in child account19 ms0013+1313+13
Scenario: All device parameters must match the device creator4 ms0033
Scenario: Assign 100 Devices to One Group12 ms0011+1111+11
Scenario: B1 Broker publish to CTRL_ACC_REPLY15 ms0-20-29+49
Scenario: B10 Broker create sub-topic on ACL_DATA_ACC is not allowed10 ms0-20-29+49
Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed11 ms0-20-28+48
Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI15 ms0099
Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed18 ms0-20-29+49
Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed11 ms0-20-28+48
Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY12 ms0-20-29+49
Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY22 ms0099
Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account10 ms0-20-29+49
Scenario: B5 Broker publish to CTRL_ACC is not allowed14 ms0099
Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed15 ms0099
Scenario: B7 Broker subscribe on CTRL_ACC is not allowed5 ms0-20-28+48
Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI10 ms0099
Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed18 ms0-20-29+49
Scenario: Basic Device Event queries7 ms0010-410-4
Scenario: Birth and applications event handling6 ms001212
Scenario: Birth and death message handling8 ms001212
Scenario: Birth and missing event handling5 ms001212
Scenario: Birth message handling from a new device8 ms001313
Scenario: Birth message handling from an existing device8 ms001212
Scenario: Both the parent and child accounts do not expire6 ms001111
Scenario: Both the parent and child accounts have the same expiration date8 ms001111
Scenario: Captured date based ClientInfo data check40 ms0030+1530+15
Scenario: Case sensitiveness of named device searches3 ms004+44+4
Scenario: Change an existing step name4 ms0012+412+4
Scenario: Change role name so it is too short4 ms006+66+6
Scenario: Change the account parent path8 ms0055
Scenario: Changing Client ID6 ms009+99+9
Scenario: Changing Description On Group With Long Description6 ms007+77+7
Scenario: Changing Description On Group With Long Name6 ms007+77+7
Scenario: Changing Description On Group With Numbers In Name5 ms0010+1010+10
Scenario: Changing Description On Group With Permitted Symbols6 ms007+77+7
Scenario: Changing Description On Group With Short Description6 ms007+77+7
Scenario: Changing Description On Group With Short Name4 ms007+77+7
Scenario: Changing Description On Tag With Long Description4 ms004+44+4
Scenario: Changing Description On Tag With Long Name6 ms005+55+5
Scenario: Changing Description On Tag With Numbers In Name4 ms006+66+6
Scenario: Changing Description On Tag With Permitted Symbols In Name4 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 Disabled5 ms009+99+9
Scenario: Changing Device Status To Enabled9 ms009+99+9
Scenario: Changing Group's Description To Non-Uniqe One8 ms007+77+7
Scenario: Changing Group's Description To Uniqe One8 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 Description8 ms007+77+7
Scenario: Changing Group's Name To Non-Unique One8 ms009+99+9
Scenario: Changing Group's Name To Short One Without Changing Description9 ms007+77+7
Scenario: Changing Group's Name To Unique One4 ms007+77+7
Scenario: Changing Group's Name To a Long One Without Changing Description10 ms007+77+7
Scenario: Changing Group's Name To a Too Long One Without Changing Description4 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 One5 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 Description4 ms005+55+5
Scenario: Changing Tag's Name To Contain Permitted Symbols In Name Without Description3 ms005+55+5
Scenario: Changing Tag's Name To Non-Unique One6 ms006+66+6
Scenario: Changing Tag's Name To Short One Without Description4 ms007+77+7
Scenario: Changing Tag's Name To Unique One5 ms007+77+7
Scenario: Changing Tag's Name To a Long One Without Description7 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 Description4 ms005+55+5
Scenario: Changing description of a nonexisting role4 ms007+77+7
Scenario: Changing job description to non-unique one16 ms007+77+7
Scenario: Changing job description to the long one7 ms006+66+6
Scenario: Changing job description to unique one5 ms006+66+6
Scenario: Changing job description to very short one11 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 description11 ms005+55+5
Scenario: Changing job name to a too short one without description7 ms006+66+6
Scenario: Changing job name to contain invalid symbols in name without description8 ms004+44+4
Scenario: Changing job name to contain permitted symbols in name without description7 ms005+55+5
Scenario: Changing job name to non-unique one11 ms008+88+8
Scenario: Changing job name to short one without description8 ms007+77+7
Scenario: Changing job name to unique one8 ms009+99+9
Scenario: Changing name of a nonexisting role4 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 null3 ms006+66+6
Scenario: Changing role's name to a valid one3 ms006+66+6
Scenario: Channel info queries based on datastore channel filters31 ms0050+2550+25
Scenario: ChannelInfo client ID and topic data based on the client id38 ms0028+1428+14
Scenario: ChannelInfo client ID based on the account id36 ms0026+1326+13
Scenario: ChannelInfo last published date30 ms0030+1530+15
Scenario: ChannelInfo topic data based on the account id45 ms0026+1326+13
Scenario: Check account properties4 ms0044
Scenario: Check the Device Connection Domain data seetting4 ms0022
Scenario: Check the database cache coherency26 ms0030+1530+15
Scenario: Check the mapping for message semantic topics26 ms0030+1530+15
Scenario: Check the message store37 ms0020+1020+10
Scenario: Check the sanity of the Device Connection Domain data initialization3 ms0022
Scenario: Child account expires after parent25 ms0099
Scenario: Child account expires before parent9 ms001111
Scenario: Child account has null expiration date29 ms0099
Scenario: Client Id based ClientInfo data check30 ms0028+1428+14
Scenario: Compare domain entries9 ms003+13+1
Scenario: Connect to the system and publish some data78 ms0-20-1522+1722
Scenario: Connection Service factory sanity checks2 ms0022
Scenario: Count access info entities in a specific scope6 ms0024+524+5
Scenario: Count access role entities by scope5 ms0039+639+6
Scenario: Count connections in empty scope3 ms0044
Scenario: Count connections in scope3 ms0055
Scenario: Count devices with a specific BIOS version3 ms0066
Scenario: Count domains in a blank database11 ms004+14+1
Scenario: Count domains in the database7 ms007+17+1
Scenario: Count events in empty scope6 ms006-46-4
Scenario: Count groups9 ms0014+214+2
Scenario: Count groups in a blank database5 ms005+25+2
Scenario: Count job items4 ms007+37+3
Scenario: Count job items in wrong - empty - scope3 ms008+88+8
Scenario: Count role permissions in specific scopes6 ms0018+318+3
Scenario: Count roles in specific scopes6 ms0015+215+2
Scenario: Count step definition items7 ms0044
Scenario: Count step definitions in wrong (empty) scope5 ms0011
Scenario: Count steps in the database4 ms0015+415+4
Scenario: Count user4 ms0066
Scenario: Counting created roles items in the DB3 ms005+55+5
Scenario: Create a regular event21 ms008-28-2
Scenario: Create a single device with an empty string for clientID4 ms004+44+4
Scenario: Create a single device with null clientID value3 ms004+44+4
Scenario: Create a valid job entry42 ms006+66+6
Scenario: Create an event with a null scope ID8 ms007-37-3
Scenario: Create and count several execution items for a job5 ms0012+312+3
Scenario: Create index with specific prefix15 ms0012-112-1
Scenario: Create multiple users3 ms0055
Scenario: Create regular access permissions14 ms0020+520+5
Scenario: Create same user in different accounts21 ms0015+1515+15
Scenario: Create scheduler with correct end date6 ms008+88+8
Scenario: Create scheduler with empty schedule name11 ms008+88+8
Scenario: Create scheduler with end date before start date8 ms009+99+9
Scenario: Create scheduler with invalid Retry Interval property6 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 name8 ms008+88+8
Scenario: Create scheduler with too long schedule name9 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 name34 ms006+66+6
Scenario: Create scheduler without Cron Job Trigger property5 ms009+99+9
Scenario: Create scheduler without Retry Interval property6 ms009+99+9
Scenario: Create scheduler without start date10 ms007+77+7
Scenario: Create some regular role permissions5 ms009+39+3
Scenario: Create user that already exist4 ms0077
Scenario: Create user that has more than DB allowed length8 ms0055
Scenario: Create user with short name7 ms0055
Scenario: Create user with special characters in his name6 ms0055
Scenario: Create with permissions9 ms0014+414+4
Scenario: Create with permissions and a role8 ms0017+417+4
Scenario: Create with permissions and a role in the wrong scope9 ms0015+515+5
Scenario: Creating 100 Sub-accounts While InfiniteChildAccounts Is Set To True8 ms007+77+7
Scenario: Creating A Device With Disabled Status9 ms007+77+7
Scenario: Creating A Device With Enabled Status5 ms007+77+7
Scenario: Creating A Device With Long Display Name19 ms007+77+7
Scenario: Creating A Device With Long Name4 ms007+77+7
Scenario: Creating A Device With Name Containing Invalid Symbols8 ms008+88+8
Scenario: Creating A Device With Name Containing Permitted Symbols8 ms007+77+7
Scenario: Creating A Device With No Name8 ms008+88+8
Scenario: Creating A Device With Non-unique Display Name5 ms007+77+7
Scenario: Creating A Device With Non-unique Name4 ms0010+1010+10
Scenario: Creating A Device With Short Display Name9 ms007+77+7
Scenario: Creating A Device With Short Name5 ms007+77+7
Scenario: Creating A Device With Too Long Display Name5 ms008+88+8
Scenario: Creating A Device With Too Long Name6 ms008+88+8
Scenario: Creating A Device With Unique Name7 ms009+99+9
Scenario: Creating A Valid Account7 ms005+55+5
Scenario: Creating An Account With Long Name8 ms005+55+5
Scenario: Creating An Account With Long Organization Name8 ms005+55+5
Scenario: Creating An Account With Non-unique Name7 ms008+88+8
Scenario: Creating An Account With Numbers And Valid Symbols In Name6 ms005+55+5
Scenario: Creating An Account With Short Name6 ms005+55+5
Scenario: Creating An Account With Short Organization Name7 ms005+55+5
Scenario: Creating An Account With Special Symbols In Organization Name6 ms005+55+5
Scenario: Creating An Account With Too Long Organization Name8 ms006+66+6
Scenario: Creating An Account With Unique Name7 ms007+77+7
Scenario: Creating An Account With Wrong TLD Format In Email5 ms0010+1010+10
Scenario: Creating An Account Without Email7 ms006+66+6
Scenario: Creating An Account Without Name7 ms006+66+6
Scenario: Creating An Account Without Ogranization Name5 ms006+66+6
Scenario: Creating And Account Without "@" In Email35 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 Values7 ms0010+1010+10
Scenario: Creating Devices Under Account That Allows Infinite Child Devices10 ms0010+1010+10
Scenario: Creating Devices Under Account That Does Not Allow Devices10 ms009+99+9
Scenario: Creating Devices Under Account That Has Limited Child Devices6 ms0013+1313+13
Scenario: Creating Endpoint Non-Unique "Domain Name"8 ms008+88+8
Scenario: Creating Endpoint Non-Unique "Port"3 ms008+88+8
Scenario: Creating Endpoint Non-Unique "Schema"12 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 Field5 ms006+66+6
Scenario: Creating Endpoint With Invalid "Domain Name"12 ms006+66+6
Scenario: Creating Endpoint With Invalid "Schema" containing symbols2 ms006+66+6
Scenario: Creating Endpoint With Long "Domain Name"5 ms005+55+5
Scenario: Creating Endpoint With Max Length "Port"8 ms005+55+5
Scenario: Creating Endpoint With NULL parameters5 ms006+66+6
Scenario: Creating Endpoint With Schema Containing "http://"4 ms006+66+6
Scenario: Creating Endpoint With Schema Containing "https://"7 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"7 ms006+66+6
Scenario: Creating Endpoint With Too Big "Port"5 ms006+66+6
Scenario: Creating Endpoint With Too Long "Domain Name"13 ms006+66+6
Scenario: Creating Endpoint With Too Long "Schema"7 ms006+66+6
Scenario: Creating Endpoint Without "Domain Name"5 ms006+66+6
Scenario: Creating Endpoint Without "Port"3 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 numbers3 ms006+66+6
Scenario: Creating Group Invalid Symbols In Name Without Description4 ms007+77+7
Scenario: Creating Group With Invalid Symbols In Name With Valid Description5 ms007+77+7
Scenario: Creating Group With Long Name With Valid Description7 ms006+66+6
Scenario: Creating Group With Long Name Without Description6 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 Description4 ms006+66+6
Scenario: Creating Group With Permitted Symbols In Name With Valid Description5 ms006+66+6
Scenario: Creating Group With Short Name With Valid Description8 ms006+66+6
Scenario: Creating Group With Short Name Without Description2 ms006+66+6
Scenario: Creating Group With Too Long Name With Valid Description6 ms007+77+7
Scenario: Creating Group With Too Long Name Without Description5 ms007+77+7
Scenario: Creating Group With Too Short Name With Valid Description9 ms007+77+7
Scenario: Creating Group With Too Short Name Without Description5 ms007+77+7
Scenario: Creating Group Without a Name And With Valid Description5 ms007+77+7
Scenario: Creating Group Without a Name And Without Description5 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 MaxNumberChildGroups7 ms0010+1010+10
Scenario: Creating Groups Under Account That Allows Infinite Child Groups9 ms009+99+9
Scenario: Creating Groups Under Account That Does Not Allow Groups4 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 Jobs6 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 Jobs6 ms009+99+9
Scenario: Creating Jobs Under Account That Has Limited Child Jobs23 ms0013+1313+13
Scenario: Creating Non-Unique Group With Valid Description7 ms008+88+8
Scenario: Creating Non-Unique Tag With Valid Description3 ms005+55+5
Scenario: Creating Non-unique Group Without Description6 ms008+88+8
Scenario: Creating Non-unique Tag Without Description8 ms004+44+4
Scenario: Creating Roles And Than Setting Role Service So It Does Not Allow Roles9 ms0011+1111+11
Scenario: Creating Roles And Then Changing Role Service Values6 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 Roles8 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 Set7 ms0013+1313+13
Scenario: Creating Sub-accounts When InfiniteChildAccoounts Is Set To True And maxNumberChildAccounts Is Set6 ms0014+1414+14
Scenario: Creating Sub-accounts When InfiniteChildAccounts Is Set To False7 ms009+99+9
Scenario: Creating Sub-accounts when InfiniteChildAccounts Is Set To True6 ms0012+1212+12
Scenario: Creating Tag With Invalid Symbols In Name With Valid Description3 ms004+44+4
Scenario: Creating Tag With Invalid Symbols In Name Without Description3 ms004+44+4
Scenario: Creating Tag With Long Name With Valid Description4 ms004+44+4
Scenario: Creating Tag With Long Name Without Description7 ms004+44+4
Scenario: Creating Tag With Numbers In Name With Valid Description4 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 Description7 ms004+44+4
Scenario: Creating Tag With Permitted Symbols In Name Without Description5 ms004+44+4
Scenario: Creating Tag With Short Name With Valid Description4 ms004+44+4
Scenario: Creating Tag With Short Name Without Description8 ms004+44+4
Scenario: Creating Tag With Too Long Name With Valid Description4 ms004+44+4
Scenario: Creating Tag With Too Long Name Without Description10 ms004+44+4
Scenario: Creating Tag With Too Short Name With Valid Description4 ms004+44+4
Scenario: Creating Tag With Too Short Name Without Description5 ms004+44+4
Scenario: Creating Tag Without a Name And With Valid Description4 ms004+44+4
Scenario: Creating Tag Without a Name And Without Description4 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 Values8 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 Tags9 ms009+99+9
Scenario: Creating Tags Under Account That Has Limited Child Tags7 ms0012+1212+12
Scenario: Creating Unique Group With Long Description5 ms006+66+6
Scenario: Creating Unique Group With Non-unique Description8 ms007+77+7
Scenario: Creating Unique Group With Short Description4 ms006+66+6
Scenario: Creating Unique Group With Unique Description7 ms006+66+6
Scenario: Creating Unique Group Without Description13 ms006+66+6
Scenario: Creating Unique Tag With Long Description5 ms004+44+4
Scenario: Creating Unique Tag With Non-unique Description6 ms005+55+5
Scenario: Creating Unique Tag With Short Description5 ms004+44+4
Scenario: Creating Unique Tag With Unique Description4 ms004+44+4
Scenario: Creating Unique Tag Without Description20 ms004+44+4
Scenario: Creating Users And Than Setting User Service So It Does Not Allow Users9 ms0011+1111+11
Scenario: Creating Users And Then Changing User Service Values8 ms0010+1010+10
Scenario: Creating Users Under Account That Allows Infinite Child Users7 ms0010+1010+10
Scenario: Creating Users Under Account That Does Not Allow Users9 ms009+99+9
Scenario: Creating Users Under Account That Has Limited Child Users7 ms0012+1212+12
Scenario: Creating Valid Endpoint4 ms006+66+6
Scenario: Creating a Access Group with invalid special symbols in name5 ms004+44+4
Scenario: Creating a Device With Permitted Symbols in its Display Name14 ms007+77+7
Scenario: Creating a Device With Unique Display Name5 ms008+88+8
Scenario: Creating a job with name only10 ms006+66+6
Scenario: Creating a job with null name18 ms005+55+5
Scenario: Creating a job without name with valid description11 ms005+55+5
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 only2 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 enough2 ms005+55+5
Scenario: Creating a role with special characters in the description3 ms004+44+4
Scenario: Creating a role with the name that contains digits5 ms005+55+5
Scenario: Creating a role with too long name2 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 description4 ms003+33+3
Scenario: Creating a role wtih 255 characters long name3 ms005+55+5
Scenario: Creating a single device with case sensitive clientID4 ms005+55+5
Scenario: Creating a single device with clientID that contains 255 characters5 ms005+55+5
Scenario: Creating a single device with clientID that contains 256 characters6 ms004+44+4
Scenario: Creating a single device with clientID that contains invalid character4 ms004+44+4
Scenario: Creating a single device with clientID that contains invalid characters10 ms004+44+4
Scenario: Creating a single device with spaces in clientID5 ms005+55+5
Scenario: Creating a single device with valid clientID6 ms005+55+5
Scenario: Creating a valid Access Group with numbers in name5 ms005+55+5
Scenario: Creating a valid Access Group with only numbers in name3 ms005+55+5
Scenario: Creating a valid Access Group with unique name27 ms005+55+5
Scenario: Creating a valid Access Group with valid special symbols in name6 ms005+55+5
Scenario: Creating a valid role3 ms005+55+5
Scenario: Creating an Access Group with empty name7 ms004+44+4
Scenario: Creating an Access Group with long name7 ms005+55+5
Scenario: Creating an Access Group with short name9 ms005+55+5
Scenario: Creating an Access Group with too long name5 ms004+44+4
Scenario: Creating an Access Group with too short name7 ms004+44+4
Scenario: Creating an Access Group without name and with description3 ms004+44+4
Scenario: Creating and Deleting Endpoint Two Times8 ms0025+2525+25
Scenario: Creating index with regular user16 ms002525
Scenario: Creating job with invalid symbols in name without description2 ms004+44+4
Scenario: Creating job with long name and valid description7 ms006+66+6
Scenario: Creating job with long name without description12 ms006+66+6
Scenario: Creating job with numbers in name and valid description6 ms006+66+6
Scenario: Creating job with numbers in name without description6 ms006+66+6
Scenario: Creating job with permitted symbols in name without description8 ms003+33+3
Scenario: Creating job with short name and valid job description7 ms006+66+6
Scenario: Creating job with short name without description9 ms006+66+6
Scenario: Creating job with too long name and valid description8 ms005+55+5
Scenario: Creating job with too long name without description20 ms005+55+5
Scenario: Creating job with too short name and valid description6 ms005+55+5
Scenario: Creating job with too short name without description16 ms005+55+5
Scenario: Creating job without name and without description11 ms005+55+5
Scenario: Creating new device and tagging it with specific Tag4 ms001414
Scenario: Creating new device, tagging it with specific Tag and then deleting this Tag5 ms001616
Scenario: Creating non-unique Access Group7 ms005+55+5
Scenario: Creating non-unique Access Group with unique description5 ms005+55+5
Scenario: Creating non-unique job name with valid job description6 ms007+77+7
Scenario: Creating two device with the same clientID8 ms005+55+5
Scenario: Creating two indexes with daily index13 ms001717
Scenario: Creating two indexes with hourly index13 ms001717
Scenario: Creating two indexes with weekly index16 ms001717
Scenario: Creating two roles with the same description2 ms006+66+6
Scenario: Creating two roles with the same name2 ms007+77+7
Scenario: Creating unique Access Group with long description4 ms005+55+5
Scenario: Creating unique Access Group with non-unique description4 ms006+66+6
Scenario: Creating unique Access Group with numbers in description4 ms005+55+5
Scenario: Creating unique Access Group with only numbers in description4 ms005+55+5
Scenario: Creating unique Access Group with short description3 ms005+55+5
Scenario: Creating unique Access Group with special symbols in description24 ms2+21+11+14+4
Scenario: Creating unique Access Group with unique description7 ms005+55+5
Scenario: Creating unique job with long description11 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 user35 ms0055
Scenario: Creation of access role with neither acess info and role entities5 ms0012+412+4
Scenario: Creation of access role without an acess info entity8 ms0012+412+4
Scenario: D1 Device publish to CTRL_ACC_REPLY15 ms0-20-29+49
Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI18 ms0099
Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed15 ms0-20-29+49
Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed11 ms0077
Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY17 ms0-20-29+49
Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY17 ms0099
Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account11 ms0-20-29+49
Scenario: D5 Device subscribe - publish - admin on CTRL_ACC15 ms0099
Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI18 ms0099
Scenario: D7 Device publish to ACL_DATA_ACC is not allowed15 ms0-20-29+49
Scenario: D8 Device create sub-topic on ACL_DATA_ACC is not allowed19 ms0-20-29+49
Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed7 ms0-20-28+48
Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed27 ms0-20-29+49
Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI11 ms0099
Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed18 ms0-20-29+49
Scenario: DM13 Data manage subscribe on ACL_CTRL_ACC_NOTIFY is not allowed5 ms0-20-28+48
Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY15 ms0-20-29+49
Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY17 ms0099
Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account7 ms0-20-29+49
Scenario: DM5 Data manage publish to CTRL_ACC is not allowed15 ms0099
Scenario: DM6 Data manage create sub-topic on CTRL_ACC is not allowed10 ms0099
Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed5 ms0-20-28+48
Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI12 ms0099
Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC7 ms0099
Scenario: DV1 Data view publish to CTRL_ACC_REPLY13 ms0-20-29+49
Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed8 ms0-20-29+49
Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed25 ms001010
Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed11 ms0099
Scenario: DV13 Data view create sub-topic on ACL_CTRL_ACC_CLI is not allowed9 ms0099
Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed9 ms0-20-29+49
Scenario: DV17 Data view subscribe on ACL_CTRL_ACC_NOTIFY is not allowed6 ms0-20-28+48
Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY17 ms0-20-29+49
Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY15 ms0099
Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account10 ms0-20-29+49
Scenario: DV5 Data view publish to CTRL_ACC is not allowed5 ms0099
Scenario: DV6 Data view create sub-topic on CTRL_ACC is not allowed17 ms0099
Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed9 ms0-20-28+48
Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI10 ms0099
Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed13 ms0-20-29+49
Scenario: Decreasing MaxNumberChildAccounts When Sub-accounts Are Already Created8 ms0015+1515+15
Scenario: Delete Kapua system user6 ms0055
Scenario: Delete a access info entity with permissions and roles7 ms0017+817+8
Scenario: Delete a connection from the database7 ms008+18+1
Scenario: Delete a group from the database14 ms0010+410+4
Scenario: Delete a group from the database - Unknown group ID6 ms006+26+2
Scenario: Delete a job4 ms0011+311+3
Scenario: Delete a job execution item4 ms009+39+3
Scenario: Delete a job execution item twice4 ms0010+310+3
Scenario: Delete a job twice3 ms0010+310+3
Scenario: Delete a non existent event6 ms007-47-4
Scenario: Delete a non existing connection5 ms007+17+1
Scenario: Delete a non existing permission entity6 ms0016+416+4
Scenario: Delete a non existing role entry4 ms0011+311+3
Scenario: Delete a non-existing step4 ms0013+413+4
Scenario: Delete a nonexistent domain8 ms005+15+1
Scenario: Delete a step definition5 ms0088
Scenario: Delete a step definition twice5 ms0077
Scenario: Delete access role from user11 ms0012+1212+12
Scenario: Delete an access info entity twice5 ms0011+311+3
Scenario: Delete an access info entity using the wrong scope ID10 ms0011+311+3
Scenario: Delete an existing access info entity5 ms0012+312+3
Scenario: Delete an existing access permission entity12 ms0015+415+4
Scenario: Delete an existing access role entry7 ms0022+422+4
Scenario: Delete an existing account7 ms0055
Scenario: Delete an existing device from the registry6 ms0044
Scenario: Delete an existing event5 ms009-49-4
Scenario: Delete an existing role8 ms0010+510+5
Scenario: Delete an existing role twice9 ms0016+516+5
Scenario: Delete an existing step4 ms0012+412+4
Scenario: Delete items based on query results35 ms0084+4284+42
Scenario: Delete items by date ranges0.28 sec00132+132132+132
Scenario: Delete items by the datastore ID38 ms0066+3366+33
Scenario: Delete middle child expiration8 ms001515
Scenario: Delete nonexisting account4 ms0044
Scenario: Delete nonexisting role permission10 ms0013+313+3
Scenario: Delete parent expiration8 ms001414
Scenario: Delete permissions from role11 ms0018+1818+18
Scenario: Delete role permissions7 ms0010+310+3
Scenario: Delete scheduler6 ms008+88+8
Scenario: Delete scheduler which doesn't exist7 ms005+55+5
Scenario: Delete the Kapua system account3 ms0055
Scenario: Delete the last created domain entry6 ms008+18+1
Scenario: Delete user6 ms0066
Scenario: Delete user that doesn't exist4 ms0055
Scenario: Deleting "Cron Schedule" Triggering6 ms0013+1313+13
Scenario: Deleting "Device Schedule" Triggering7 ms0011+1111+11
Scenario: Deleting "Interval Schedule" Triggering6 ms0013+1313+13
Scenario: Deleting Device With Disabled Status5 ms0010+1010+10
Scenario: Deleting Device With Enabled Status5 ms0010+1010+10
Scenario: Deleting Endpoint Domain Name And Leaving it Empty5 ms008+88+8
Scenario: Deleting Endpoint Which Does Not Exist5 ms006+66+6
Scenario: Deleting Existing Group5 ms008+88+8
Scenario: Deleting Existing Group And Creating It Again With Same Name6 ms0012+1212+12
Scenario: Deleting Existing Tag And Creating It Again With Same Name3 ms007+77+7
Scenario: Deleting Group's Name And Leaving It Empty Without Changing Description12 ms008+88+8
Scenario: Deleting Non-Existent Tag5 ms007+77+7
Scenario: Deleting Tag From Device17 ms008+88+8
Scenario: Deleting Tag's Name And Leaving It Empty Without Description6 ms005+55+5
Scenario: Deleting Unexisitng Group5 ms0011+1111+11
Scenario: Deleting a Permission34 ms0021+2121+21
Scenario: Deleting a non-existing Access Group4 ms006+66+6
Scenario: Deleting a role twice2 ms007+77+7
Scenario: Deleting admin role13 ms007+77+7
Scenario: Deleting an existing Access Group4 ms005+55+5
Scenario: Deleting an existing Access Group and creating it again with the same name3 ms007+77+7
Scenario: Deleting an existing role2 ms006+66+6
Scenario: Deleting default permissions from admin role10 ms0012+1212+12
Scenario: Deleting existing tag6 ms009+99+9
Scenario: Deleting role after adding it to user14 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 hierarchy18 ms002323
Scenario: Deleting user in account that is lower in hierarchy13 ms002424
Scenario: Device connection update3 ms007+17+1
Scenario: Device factory sanity checks6 ms0022
Scenario: Device queries3 ms0010-310-3
Scenario: Device query - find by BIOS version4 ms0077
Scenario: Domain entry query5 ms005+15+1
Scenario: Domain with null actions8 ms005+15+1
Scenario: Domain with null name5 ms005+15+1
Scenario: Domains with duplicate names5 ms008+18+1
Scenario: Duplicate group name in root scope6 ms0010+210+2
Scenario: Duplicate role names6 ms007+37+3
Scenario: Editing Access Group description to description with numbers3 ms005+55+5
Scenario: Editing Access Group description to description with only numbers3 ms005+55+5
Scenario: Editing Access Group description to description with special symbols3 ms004+44+4
Scenario: Editing Access Group description to long description6 ms005+55+5
Scenario: Editing Access Group description to non-unique one3 ms005+55+5
Scenario: Editing Access Group description to short description2 ms005+55+5
Scenario: Editing Access Group description to unique one3 ms007+77+7
Scenario: Editing Access Group name to a long one3 ms007+77+7
Scenario: Editing Access Group name to a too long one3 ms005+55+5
Scenario: Editing Access Group name to empty name3 ms005+55+5
Scenario: Editing Access Group name to name that contains numbers4 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 one2 ms006+66+6
Scenario: Editing Access Group name to short one3 ms007+77+7
Scenario: Editing Access Group name to too short one3 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 Numbers10 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 Value5 ms007+77+7
Scenario: Editing Endpoint Domain Name To Non-unique Value3 ms009+99+9
Scenario: Editing Endpoint Domain Name To Unique Value5 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://"4 ms008+88+8
Scenario: Editing Endpoint Schema So It Contains "https://"3 ms008+88+8
Scenario: Editing Endpoint Schema So It Contains Invalid Symbols3 ms008+88+8
Scenario: Editing Endpoint Schema So It Contains Only Numbers4 ms008+88+8
Scenario: Editing Endpoint Schema So It Has Max Length4 ms007+77+7
Scenario: Editing Endpoint Schema So It Has Min Length5 ms007+77+7
Scenario: Editing Endpoint Schema To Non-unique Value5 ms008+88+8
Scenario: Editing Endpoint Schema To Unique Value4 ms007+77+7
Scenario: Editing Endpoint Secure Field To Non-unique Value5 ms009+99+9
Scenario: Editing Endpoint Secure Field To Unique Value5 ms007+77+7
Scenario: Editing Endpoint To NULL Values5 ms0014+1414+14
Scenario: Editing Endpoint To Non-unique Endpoint5 ms0010+1010+10
Scenario: Editing Group's Name To Contain Numbers Without Changing Description11 ms007+77+7
Scenario: Editing Tag's Name To Contain Numbers Without Description4 ms007+77+7
Scenario: Empty query results are supported5 ms008+38+3
Scenario: Event factory sanity checks4 ms002-42-4
Scenario: Event service domain check5 ms002-42-4
Scenario: Every account must have the default configuration items6 ms0033
Scenario: Execute possible docker steps to show its usage5 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 Time24 ms0038+3838+38
Scenario: Executing Job When Device Connected After The Specified Start Date And Time52 ms2+26+630+3038+38
Scenario: Executing Job When Device Connected Before End Date And Time11 ms2+26+631+3139+39
Scenario: Executing Job When Device Connected Before The Specified Start Date And Time29 ms0037+3737+37
Scenario: Executing Job Without Steps27 ms0040+4040+40
Scenario: Extra long continuous test with multiple subscenarios with LOOSE default connection mode30 ms0-20-404419+407419+1
Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode31 ms0-20-382397+385397+1
Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode and no previously defined devices29 ms0-20-293305+296305+1
Scenario: Find a connection by its IDs4 ms006+16+1
Scenario: Find a connection by its client ID3 ms006+16+1
Scenario: Find a group entry in the database9 ms009+29+2
Scenario: Find a non existing event9 ms006-46-4
Scenario: Find account by Id7 ms0044
Scenario: Find account by Ids6 ms0044
Scenario: Find account by name7 ms0044
Scenario: Find account by random Id4 ms0033
Scenario: Find all child accounts10 ms0033
Scenario: Find an access info entity5 ms0011+311+3
Scenario: Find an access info entity by user ID7 ms0010+310+3
Scenario: Find an event by its ID7 ms006-46-4
Scenario: Find an existing access role entity9 ms0013+413+4
Scenario: Find by name nonexisting account5 ms0033
Scenario: Find correct number of messages by corresponding metric0.2 sec0058+5858+58
Scenario: Find device by client ID4 ms0033
Scenario: Find device by registry ID3 ms0044
Scenario: Find last created permission10 ms0012+1212+12
Scenario: Find multiple users4 ms0055
Scenario: Find role by ID6 ms007+37+3
Scenario: Find self account by id8 ms0011+1111+11
Scenario: Find self account by id and scope id4 ms0011+1111+11
Scenario: Find self account by name5 ms0011+1111+11
Scenario: Find the last created domain entry9 ms005+15+1
Scenario: Find user by id7 ms0055
Scenario: Find user by its email3 ms006+66+6
Scenario: Find user by its phone number5 ms006+66+6
Scenario: Find user by name8 ms0055
Scenario: Find user by name that doesn't exist5 ms0033
Scenario: Find user with id and scope id that doesn't exist4 ms0033
Scenario: Finding all messages by selecting all metrics0.19 sec0040+4040+40
Scenario: Finding correct number of messages by corresponding two metrics0.19 sec0052+5252+52
Scenario: Finding messages with incorrect metric parameters0.53 sec0072+7272+72
Scenario: Finding user by expiration date in the future4 ms005+55+5
Scenario: Finding user by expiration date in the past4 ms006+66+6
Scenario: Finding user by expiration date in the present4 ms006+66+6
Scenario: Generic connection query5 ms008+18+1
Scenario: Get metadata4 ms0033
Scenario: Group with a null name13 ms007+27+2
Scenario: Handle account creation18 ms0033
Scenario: Handle duplicate account names8 ms0055
Scenario: Handle null account name6 ms0044
Scenario: Handling of 2 birth messages5 ms001212
Scenario: Handling of a disconnect message from a non existing device7 ms001010
Scenario: Have Two Devices in The Same Group Without Description7 ms0013+1313+13
Scenario: I try to find a non-existing connection3 ms006+16+1
Scenario: If user credential expiration date is before today, user can not login11 ms001414
Scenario: If user credential expiration date is today, user can not login it is day inclusive8 ms001414
Scenario: If user credential expiration date is tomorrow, user can login4 ms001313
Scenario: If user credential is in state disabled, user can not login14 ms001414
Scenario: If user credential is in state enabled, user can login7 ms001313
Scenario: If user expiration date is before today, user can not login8 ms001313
Scenario: If user expiration date is today, user can not login because expiration date was reached6 ms001313
Scenario: If user expiration date is tomorrow, user can login3 ms001212
Scenario: Init Security Context for all scenarios0.16 sec0048+4848+48
Scenario: Installing a package15 ms0-20-713+913
Scenario: Interval Job" Schedule With Too Long Name8 ms0011+1111+11
Scenario: It must be possible to query for specific entries in the role database5 ms008+38+3
Scenario: It should not be possible to change the configuration items3 ms005+55+5
Scenario: Job execution factory sanity checks3 ms0022
Scenario: Job factory sanity checks4 ms0033
Scenario: Job with a duplicate name4 ms009+39+3
Scenario: Job with a null name3 ms008+38+3
Scenario: Job with a null scope ID3 ms009+39+3
Scenario: Job with an empty name2 ms008+28+2
Scenario: List Endpoints Created From Sub-Account18 ms2+223+231+126+26
Scenario: List Endpoints From "kapua-sys" Account3 ms2+24+45+511+11
Scenario: List Endpoints From Sub-Account Of Another Sub-Account13 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 id31 ms0034+1734+17
Scenario: MetricsInfo last published date28 ms0048+2448+24
Scenario: Modify a role that was deleted10 ms009+39+3
Scenario: Modify an existing account10 ms0044
Scenario: Modify last child expiration so that it still expires before parent15 ms001414
Scenario: Modify middle child expiration so that it still expires before parent6 ms001414
Scenario: Modify middle child expiration to outlive parent9 ms001515
Scenario: Modify nonexisting account4 ms0066
Scenario: Modify parent expiration so that it still expires after child9 ms001414
Scenario: Modify parent expiration to before child expiration7 ms001515
Scenario: Modifying Sub-account of a different parent account9 ms0025+2525+25
Scenario: Moving Device From One Group With Description to Another8 ms0014+1414+14
Scenario: Nameless role entry5 ms007+37+3
Scenario: Negative scenario when client connects twice with same client id49 ms001111
Scenario: New connection with reserved ID14 ms0-20-1934+2234+1
Scenario: Permission factory sanity checks6 ms0033
Scenario: Positive scenario without stealing link18 ms001212
Scenario: Query based on message ordering30 ms0020+1020+10
Scenario: Query based on metrics ordering27 ms0020+1020+10
Scenario: Query before schema search33 ms0082+4182+41
Scenario: Query for a specific group by name6 ms0016+216+2
Scenario: Query for all the access info entities of a specific user6 ms0018+318+3
Scenario: Query for all the access info entities of an invalid user9 ms0010+310+3
Scenario: Query for executions of a specific job5 ms0019+319+3
Scenario: Query for jobs with specified name4 ms009+39+3
Scenario: Query for step definitions4 ms0077
Scenario: Query user7 ms0066
Scenario: Querying Other Items With All Account Permissions11 ms0039+3939+39
Scenario: Regular connection6 ms007+17+1
Scenario: Regular creation of Access Role entity9 ms0014+414+4
Scenario: Regular domain12 ms005+15+1
Scenario: Regular group in random scope10 ms007+27+2
Scenario: Regular group in root scope7 ms007+27+2
Scenario: Regular job creation5 ms0010+310+3
Scenario: Regular job execution creation3 ms008+38+3
Scenario: Regular role creation6 ms009+39+3
Scenario: Regular step creation3 ms0012+412+4
Scenario: Regular step definition creation7 ms0077
Scenario: Regular step definition with a property list6 ms0044
Scenario: Reset Security Context for all scenarios0.17 sec0048+4848+48
Scenario: Restarting a job with Asset Write and Bundle Start steps22 ms0028+2828+28
Scenario: Restarting a job with Command Execution and Bundle Start steps25 ms0028+2828+28
Scenario: Restarting a job with Configuration Put and Bundle Start steps26 ms0028+2828+28
Scenario: Restarting a job with Package Uninstall and Bundle Start steps22 ms0028+2828+28
Scenario: Restarting a job with invalid Configuration Put and multiple devices two times47 ms0033+3333+33
Scenario: Restarting a job with invalid Configuration Put step two times35 ms0036+3636+36
Scenario: Restarting a job with invalid Package Install step and multiple devices two times31 ms0031+3131+31
Scenario: Restarting a job with invalid Package Install step two times33 ms0034+3434+34
Scenario: Restarting a job with invalid Package Uninstall step and multiple devices two times31 ms0032+3232+32
Scenario: Restarting a job with invalid Package Uninstall step two times21 ms0034+3434+34
Scenario: Restarting a job with valid Configuration Put step and multiple devices two times56 ms0033+3333+33
Scenario: Restarting a job with valid Configuration Put step two times24 ms0036+3636+36
Scenario: Restarting a job with valid Package Install step and multiple devices two times67 ms0029+2929+29
Scenario: Restarting a job with valid Package Install step two times30 ms0034+3434+34
Scenario: Restarting a job with valid Package Uninstall step and multiple devices two times25 ms0030+3030+30
Scenario: Restarting a job with valid Package Uninstall step two times25 ms0032+3232+32
Scenario: Restarting job With invalid Asset Write and multiple two times33 ms0034+3434+34
Scenario: Restarting job With valid Asset Write step two times34 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 step31 ms0025+2525+25
Scenario: Restarting job with Asset Write step and multiple devices21 ms0028+2828+28
Scenario: Restarting job with Bundle Start step24 ms0025+2525+25
Scenario: Restarting job with Bundle Start step and multiple devices20 ms0027+2727+27
Scenario: Restarting job with Bundle Stop and Bundle Start step and multiple devices38 ms0031+3131+31
Scenario: Restarting job with Bundle Stop and Bundle Start steps20 ms0029+2929+29
Scenario: Restarting job with Bundle Stop step20 ms0025+2525+25
Scenario: Restarting job with Bundle Stop step and multiple devices31 ms0027+2727+27
Scenario: Restarting job with Command Execution and Bundle Start steps and multiple devices23 ms0031+3131+31
Scenario: Restarting job with Command Execution step23 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 devices51 ms0031+3131+31
Scenario: Restarting job with Configuration Put step24 ms0025+2525+25
Scenario: Restarting job with Configuration Put step and multiple devices20 ms0027+2727+27
Scenario: Restarting job with Package Download/Install and Bundle Start steps and multiple devices45 ms0059+5959+59
Scenario: Restarting job with Package Download/Install step and multiple devices22 ms0027+2727+27
Scenario: Restarting job with Package Install step21 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 step22 ms0025+2525+25
Scenario: Restarting job with Package Uninstall step and multiple device21 ms0027+2727+27
Scenario: Restarting job with invalid Asset Write step two times29 ms0036+3636+36
Scenario: Restarting job with invalid Bundle Start and Bundle Stop steps and multiple devices two times38 ms0041+4141+41
Scenario: Restarting job with invalid Bundle Start and Bundle Stop steps two times38 ms0043+4343+43
Scenario: Restarting job with invalid Bundle Start step and multiple devices two times36 ms0035+3535+35
Scenario: Restarting job with invalid Bundle Start step two times23 ms0037+3737+37
Scenario: Restarting job with invalid Bundle Stop step and multiple devices two times35 ms0035+3535+35
Scenario: Restarting job with invalid Bundle Stop step two times33 ms0037+3737+37
Scenario: Restarting job with invalid Command Execution and Package Install step two times29 ms0036+3636+36
Scenario: Restarting job with invalid Command Execution and Package Install steps and multiple devices two times31 ms0037+3737+37
Scenario: Restarting job with invalid Command Execution step and multiple devices two times56 ms0031+3131+31
Scenario: Restarting job with invalid Command Execution step two times42 ms0032+3232+32
Scenario: Restarting job with invalid Configuration Put And Command Execution steps two times41 ms0038+3838+38
Scenario: Restarting job with invalid Configuration Put and Command Execution steps and multiple devices two times38 ms0037+3737+37
Scenario: Restarting job with invalid Package Uninstall and Asset Write steps and multiple devices two times66 ms0038+3838+38
Scenario: Restarting job with invalid Package Uninstall and Asset Write steps two times18 ms0040+4040+40
Scenario: Restarting job with two Bundle Start steps20 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 times35 ms0034+3434+34
Scenario: Restarting job with valid Bundle Start And Bundle Stop steps two times17 ms0043+4343+43
Scenario: Restarting job with valid Bundle Start and Bundle Stop steps and multiple devices two times30 ms0041+4141+41
Scenario: Restarting job with valid Bundle Start step and multiple devices two times44 ms0035+3535+35
Scenario: Restarting job with valid Bundle Start step two times44 ms0037+3737+37
Scenario: Restarting job with valid Bundle Stop step and multiple devices two times53 ms0035+3535+35
Scenario: Restarting job with valid Bundle Stop step two times27 ms0037+3737+37
Scenario: Restarting job with valid Command Execution and Package Install steps and multiple devices two times63 ms0033+3333+33
Scenario: Restarting job with valid Command Execution and Package Install steps two times32 ms0034+3434+34
Scenario: Restarting job with valid Command Execution step and multiple devices two times52 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 times31 ms0037+3737+37
Scenario: Restarting job with valid Configuration Put and Command Execution steps two times52 ms0038+3838+38
Scenario: Restarting job with valid Package Uninstall and Asset Write steps and multiple devices two times43 ms0036+3636+36
Scenario: Restarting job with valid Package Uninstall and Asset Write steps two times42 ms0038+3838+38
Scenario: Role creator sanity checks5 ms0022
Scenario: Role entry with no actions7 ms006+26+2
Scenario: Role object equality check6 ms0022
Scenario: Role service related objects sanity checks6 ms0044
Scenario: Search By Client ID And Get Multiple Matches39 ms0037+3737+37
Scenario: Search By Client ID And Get No Matches6 ms0010+1010+10
Scenario: Search By Client ID And Get One Match5 ms008+88+8
Scenario: Search By Client ID and Display Name7 ms0012+1212+12
Scenario: Search By Client ID and Serial Number4 ms0012+1212+12
Scenario: Search By Client ID and Status6 ms0012+1212+12
Scenario: Search By Client ID, Display Name and Serial Number4 ms0012+1212+12
Scenario: Search By Client ID, Display Name and Status13 ms0012+1212+12
Scenario: Search By Client ID, Display Name, Serial Number and Status10 ms0012+1212+12
Scenario: Search By Device Status And Get No Matches6 ms008+88+8
Scenario: Search By Device's Display Name And Get One Match4 ms008+88+8
Scenario: Search By Display Name and Serial Number4 ms0012+1212+12
Scenario: Search By Display Name and Status10 ms0012+1212+12
Scenario: Search By Full Client ID And Get One Match8 ms0010+1010+10
Scenario: Search By Non-existing Client ID And Get No Matches8 ms008+88+8
Scenario: Search By One Letter Of Display Name7 ms008+88+8
Scenario: Search By One Letter Of Serial Number5 ms0012+1212+12
Scenario: Search By Serial Number And Get Multiple Matches11 ms0014+1414+14
Scenario: Search By Serial Number And Get No Matches4 ms0010+1010+10
Scenario: Search By Serial Number And Get One Match4 ms0011+1111+11
Scenario: Search By Serial Number and Status13 ms0012+1212+12
Scenario: Search By Serial Number, Display Name and Status14 ms0012+1212+12
Scenario: Search By Specific Serial Number5 ms0010+1010+10
Scenario: Search By Status And Get Multiple Matches8 ms0010+1010+10
Scenario: Search by Device Status And Get One Match5 ms0010+1010+10
Scenario: Search for a non existent client ID21 ms006+16+1
Scenario: Search for an access info entity by an incorrect user ID6 ms0011+311+3
Scenario: Search the role database for a random ID5 ms007+37+3
Scenario: Send BIRTH message and then DC message27 ms0-20-715+915
Scenario: Send BIRTH message and then DC message while broker ip is NOT set31 ms0066
Scenario: Send BIRTH message and then DC message while broker ip is set by System39 ms0-20-28+48
Scenario: Send BIRTH message and then DC message while broker ip is set by config file54 ms0-20-28+48
Scenario: Set environment variables0.12 sec0061+1861+18
Scenario: Setting InfiniteChildAccounts To False And Increasing MaxNumberChildAccounts When Sub-accounts Are Already Created9 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 Value5 ms007+77+7
Scenario: Setting Max Failures To 015 ms0015+1515+15
Scenario: Setting Max Failures To 111 ms0015+1515+15
Scenario: Setting Max Failures To 10014 ms0015+1515+15
Scenario: Setting Max Failures To Negative Value8 ms007+77+7
Scenario: Setting Reset After Login Counter To 0 Seconds25 ms0017+1717+17
Scenario: Setting Reset After Login Counter To Negative Value8 ms007+77+7
Scenario: Setting configuration without mandatory items must raise an error3 ms0055
Scenario: Simple create6 ms0011+411+4
Scenario: Simple positive scenario for creating daily index13 ms001414
Scenario: Simple positive scenario for creating default - weekly index15 ms001212
Scenario: Simple positive scenario for creating hourly index11 ms001414
Scenario: Start broker for all scenarios0.31 sec0-30044+4244+12
Scenario: Start datastore for all scenarios0.57 sec003030
Scenario: Start event broker for all scenarios0.38 sec0050+1450+14
Scenario: Starting a job with Asset Write and Bundle Start steps24 ms0036+3636+36
Scenario: Starting a job with Asset Write step26 ms0025+2525+25
Scenario: Starting a job with Bundle Start step26 ms0034+3434+34
Scenario: Starting a job with Bundle Stop and Bundle Start steps23 ms0039+3939+39
Scenario: Starting a job with Bundle Stop step20 ms0035+3535+35
Scenario: Starting a job with Command Execution and Bundle Start steps24 ms0037+3737+37
Scenario: Starting a job with Command Execution step20 ms0025+2525+25
Scenario: Starting a job with Configuration Put and Bundle Start steps24 ms0037+3737+37
Scenario: Starting a job with Configuration Put step24 ms0025+2525+25
Scenario: Starting a job with Package Install and Bundle Start steps21 ms0039+3939+39
Scenario: Starting a job with Package Install step22 ms0032+3232+32
Scenario: Starting a job with Package Uninstall and Bundle Start steps25 ms0036+3636+36
Scenario: Starting a job with Package Uninstall step22 ms0033+3333+33
Scenario: Starting a job with invalid Asset Write step30 ms0031+3131+31
Scenario: Starting a job with invalid Asset Write step and multiple targets20 ms0029+2929+29
Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps32 ms0036+3636+36
Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps and multiple devices44 ms0035+3535+35
Scenario: Starting a job with invalid Bundle Start step31 ms0031+3131+31
Scenario: Starting a job with invalid Bundle Stop step25 ms0031+3131+31
Scenario: Starting a job with invalid Bundle Stop step and multiple devices31 ms0029+2929+29
Scenario: Starting a job with invalid Command Execution step73 ms0027+2727+27
Scenario: Starting a job with invalid Configuration Put step40 ms0030+3030+30
Scenario: Starting a job with invalid Configuration Put step and multiple devices88 ms0028+2828+28
Scenario: Starting a job with invalid Package Install step55 ms0029+2929+29
Scenario: Starting a job with invalid Package Install step and multiple devices31 ms0026+2626+26
Scenario: Starting a job with invalid Package Uninstall and Asset Write steps25 ms0034+3434+34
Scenario: Starting a job with invalid Package Uninstall and Asset Write steps and multiple devices18 ms0032+3232+32
Scenario: Starting a job with invalid Package Uninstall step26 ms0029+2929+29
Scenario: Starting a job with invalid Package Uninstall step and multiple targets37 ms0026+2626+26
Scenario: Starting a job with two Bundle Start steps26 ms0039+3939+39
Scenario: Starting a job with valid Asset Write step22 ms0031+3131+31
Scenario: Starting a job with valid Asset Write step and multiple targets58 ms0029+2929+29
Scenario: Starting a job with valid Bundle Start and Bundle Stop steps35 ms0036+3636+36
Scenario: Starting a job with valid Bundle Start and Bundle Stop steps and multiple devices37 ms0034+3434+34
Scenario: Starting a job with valid Bundle Start step31 ms0031+3131+31
Scenario: Starting a job with valid Bundle Stop step23 ms0031+3131+31
Scenario: Starting a job with valid Bundle Stop step and multiple devices43 ms0029+2929+29
Scenario: Starting a job with valid Command Execution step46 ms0027+2727+27
Scenario: Starting a job with valid Configuration Put step27 ms0031+3131+31
Scenario: Starting a job with valid Configuration Put step and multiple devices45 ms0026+2626+26
Scenario: Starting a job with valid Package Install step26 ms0029+2929+29
Scenario: Starting a job with valid Package Install step and multiple devices34 ms0026+2626+26
Scenario: Starting a job with valid Package Uninstall and Asset Write steps42 ms0033+3333+33
Scenario: Starting a job with valid Package Uninstall and Asset Write steps and multiple devices49 ms0032+3232+32
Scenario: Starting a job with valid Package Uninstall step29 ms0030+3030+30
Scenario: Starting a job with valid Package Uninstall step and multiple targets58 ms0026+2626+26
Scenario: Starting and stopping the simulator should create a device entry and properly set its status12 ms0-20-1420+1620
Scenario: Starting job with Asset Write and Bundle Start steps and multiple devices29 ms0032+3232+32
Scenario: Starting job with Asset Write step and multiple devices18 ms0028+2828+28
Scenario: Starting job with Bundle Start step and multiple devices26 ms0028+2828+28
Scenario: Starting job with Bundle Stop and Bundle Start step and multiple devices21 ms0032+3232+32
Scenario: Starting job with Bundle Stop step and multiple devices22 ms0028+2828+28
Scenario: Starting job with Command Execution and Bundle Start steps and multiple devices24 ms0032+3232+32
Scenario: Starting job with Command Execution step and multiple devices21 ms0028+2828+28
Scenario: Starting job with Configuration Put and Bundle Start steps and multiple devices26 ms0032+3232+32
Scenario: Starting job with Configuration Put step and multiple devices22 ms0028+2828+28
Scenario: Starting job with Package Download/Install and Bundle Start steps and multiple devices28 ms0038+3838+38
Scenario: Starting job with Package Download/Install step and multiple devices31 ms0034+3434+34
Scenario: Starting job with Package Uninstall and Bundle start steps and multiple device24 ms0032+3232+32
Scenario: Starting job with Package Uninstall step and multiple device30 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 steps27 ms0031+3131+31
Scenario: Starting job with invalid Command Execution step and multiple devices38 ms0028+2828+28
Scenario: Starting job with invalid Command Execution, invalid Package Install steps and multiple devices44 ms0029+2929+29
Scenario: Starting job with invalid Configuration Put and Command Execution steps29 ms0032+3232+32
Scenario: Starting job with invalid Configuration Put and Command Execution steps and multiple devices36 ms0031+3131+31
Scenario: Starting job with two Bundle Start steps and multiple devices21 ms0032+3232+32
Scenario: Starting job with valid Bundle Start step and multiple devices47 ms0029+2929+29
Scenario: Starting job with valid Command Execution and Package Install steps20 ms0031+3131+31
Scenario: Starting job with valid Command Execution step and multiple devices40 ms0026+2626+26
Scenario: Starting job with valid Command Execution, valid Package Install steps and multiple devices50 ms0029+2929+29
Scenario: Starting job with valid Configuration Put and Command Execution steps59 ms0032+3232+32
Scenario: Starting job with valid Configuration Put and Command Execution steps and multiple devices40 ms0030+3030+30
Scenario: Stealing link scenario18 ms0-20-1428+1628
Scenario: Step definition factory sanity checks5 ms0022
Scenario: Step definition with a duplicate name6 ms0066
Scenario: Step definition with a null name4 ms0066
Scenario: Step definition with a null scope ID6 ms0066
Scenario: Step definition with an empty name5 ms0055
Scenario: Step factory sanity checks4 ms0022
Scenario: Step with a null scope ID3 ms0012+412+4
Scenario: Stop broker after all scenarios0.32 sec0046+1446+14
Scenario: Stop datastore after all scenarios0.21 sec003030
Scenario: Stop event broker for all scenarios0.42 sec0050+1450+14
Scenario: Stop job with multiple Asset Write and Package Install steps and one target25 ms0037+3737+37
Scenario: Stop job with multiple Bundle Start and Package Install steps and one target25 ms0037+3737+37
Scenario: Stop job with multiple Bundle Stop and Package Uninstall steps and one target32 ms0037+3737+37
Scenario: Stop job with multiple Command Execution and Package Install steps and one target51 ms0034+3434+34
Scenario: Stop job with multiple Configuration Put and Package Uninstall steps and one target44 ms0035+3535+35
Scenario: Stop job with multiple targets and Asset Write and Package Install steps and one target40 ms0037+3737+37
Scenario: Stop job with multiple targets and Bundle Start and Package Install steps78 ms0036+3636+36
Scenario: Stop job with multiple targets and Bundle Stop and Package Uninstall steps40 ms0037+3737+37
Scenario: Stop job with multiple targets and Command Execution and Package Install steps42 ms0034+3434+34
Scenario: Stop job with multiple targets and Configuration Put and Package Uninstall steps24 ms0037+3737+37
Scenario: Test LOOSE user coupling on single connection12 ms0-20-1328+1628+1
Scenario: Test LOOSE user coupling with 3 connections14 ms0-20-2338+2638+1
Scenario: Test STRICT user coupling on single connection16 ms0-20-1025+1325+1
Scenario: Test STRICT user coupling with 3 connections and a reserved user15 ms0-20-4863+5163+1
Scenario: Test STRICT user coupling with user change allowed on single connection15 ms0-20-2136+2436+1
Scenario: Test account query4 ms0044
Scenario: Test the message store with server timestamp indexing19 ms0026+1326+13
Scenario: Test the message store with timestamp indexing31 ms0026+1326+13
Scenario: The Client ID is case sensitive4 ms008+18+1
Scenario: To be defined5 ms00-1513+1213-3
Scenario: Translating "CommandRequestMessage" to "KuraRequestMessage"31 ms004+44+4
Scenario: Translating CommandRequestMessage to null8 ms004+44+4
Scenario: Translating empty message to empty message7 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 message2 ms005+55+5
Scenario: Translating invalid kura data message with valid channel, body and metrics into mqtt message7 ms005+55+5
Scenario: Translating kura data message with null channel, and payload without body and with metrics2 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 message3 ms005+55+5
Scenario: Translating kura data message with valid channel, metrics and without body into jms message1 ms005+55+5
Scenario: Translating kura data message with valid channel, metrics and without body into mqtt message4 ms005+55+5
Scenario: Translating null to KuraRequestMessage8 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 message3 ms006+66+6
Scenario: Translating of jms message with valid payload and valid topic into kura data message6 ms006+66+6
Scenario: Translating of mqtt message with invalid payload and invalid topic into kura data message4 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 message7 ms005+55+5
Scenario: Translation of kura data message with valid channel, body and metrics into mqtt message3 ms005+55+5
Scenario: Translation of kura data message with valid channel, metrics and without body into mqtt message4 ms005+55+5
Scenario: Translation of mqtt message with empty payload into kura data message4 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 message7 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 message5 ms006+66+6
Scenario: Try to add two different roles with same permissions13 ms0021+2121+21
Scenario: Try to change an existing connection ID2 ms007+17+1
Scenario: Try to create an access into entity with an invalid role id4 ms0012+412+4
Scenario: Try to delete a non existing device from the registry3 ms0044
Scenario: Try to find a device with an invalid client ID5 ms0033
Scenario: Try to find a device with an invalid registry ID4 ms0033
Scenario: Try to find users granted to "admin" role11 ms0012+1212+12
Scenario: Try to find users that have assigned specific role9 ms0012+1212+12
Scenario: Try to modify the connection client ID4 ms007+17+1
Scenario: Try to update the device client ID3 ms0044
Scenario: Uncorrect Login While Lockout Policy Is Disabled10 ms0017+1717+17
Scenario: Uncorrect Login While Lockout Policy Is Enabled16 ms0017+1717+17
Scenario: Update a group entry in the database7 ms009+29+2
Scenario: Update a group entry with a false ID6 ms0010+210+2
Scenario: Update a job XML definition3 ms0010+310+3
Scenario: Update a job description3 ms0010+310+3
Scenario: Update a job name4 ms0010+310+3
Scenario: Update a non existing device3 ms0055
Scenario: Update a nonexistent job4 ms0010+310+3
Scenario: Update a nonexistent step definition6 ms0077
Scenario: Update a step definition name17 ms0077
Scenario: Update a step definition processor name5 ms0088
Scenario: Update a step definition target type7 ms0088
Scenario: Update existing role name7 ms008+38+3
Scenario: Update job id of an existing execution item4 ms009+39+3
Scenario: Update schedule which doesn't exist7 ms005+55+5
Scenario: Update scheduler end date10 ms009+99+9
Scenario: Update scheduler name6 ms008+88+8
Scenario: Update scheduler start date9 ms008+88+8
Scenario: Update the end time of an existing execution item4 ms0010+310+3
Scenario: Update trigger definition6 ms008+88+8
Scenario: Update user10 ms0077
Scenario: Update user that doesn't exist4 ms0055
Scenario: User locking itself out by using out login attempts9 ms001616
Scenario: User locking itself out with failed attempts and not waiting to unlock8 ms001717
Scenario: User locking itself out with failed attempts and waiting to unlock6 ms001717
Scenario: User login with wrong pass, but with enough time between login failures3 ms001919
Scenario: User not locking itself out by using less than max failed login attempts5 ms001717
Scenario: Validate a device client based search with a null client ID4 ms005+15+1
Scenario: Validate a device client based search with an empty client ID4 ms005+15+1
Scenario: Validate a device client search with null scope2 ms005+15+1
Scenario: Validate a device creator with a null client ID3 ms0066
Scenario: Validate a device creator with a null scope ID4 ms0066
Scenario: Validate a device query with a null Scope ID3 ms004-14-1
Scenario: Validate a device search with a null device ID3 ms006+26+2
Scenario: Validate a device search with a null scope ID1 ms006+26+2
Scenario: Validate a null creator7 ms0055
Scenario: Validate a null device3 ms0055
Scenario: Validate a null device count2 ms0055
Scenario: Validate a null device query3 ms0055
Scenario: Validate a regular creator3 ms0044
Scenario: Validate a regular device client search3 ms004+14+1
Scenario: Validate a regular device count3 ms0044
Scenario: Validate a regular device query4 ms0044
Scenario: Validate a regular device search3 ms005+25+2
Scenario: Validate deleting a device with a null device ID2 ms006+26+2
Scenario: Validate deleting a device with a null scope ID2 ms006+26+2
Scenario: Waiting For Lock Duration Time To Pass8 ms0019+1919+19
Scenario: Waiting For Reset After Login Counter To Pass8 ms0018+1818+18
empty) scope1 ms004-44-4