Test Result : (root)

53 failures (-69) , 264 skipped (-1085)
16,563 tests (+11739)
Took 17 sec.

All Failed Tests

Test NameDurationAge
 Scenario: Add datastore permissions to the role.And I search for data message with id "fake-id"1 ms27
 Scenario: Add datastore permissions to the role.Scenario: Add datastore permissions to the role2 ms27
 Scenario: Bug when user can retrieve user in another account if it has other account's user id.Scenario: Bug when user can retrieve user in another account if it has other account's user id1 ms29
 Scenario: Bug when user can retrieve user in another account if it has other account's user id.Then REST POST call at "/v1/authentication/user" with JSON "{"password": "ToManySecrets123#", "username": "kapua-a"}"1 ms29
 Scenario: Create same user in different accounts.Scenario: Create same user in different accounts0.89 sec27
 Scenario: Create scheduler with correct end date.Scenario: Create scheduler with correct end date2 ms25
 Scenario: Create scheduler with correct end date.Then I create a new trigger from the existing creator with previously defined date properties1 ms25
 Scenario: Create scheduler with end date before start date.Scenario: Create scheduler with end date before start date7 ms25
 Scenario: Create scheduler with end date before start date.Then I create a new trigger from the existing creator with previously defined date properties7 ms25
 Scenario: Creating unique Access Group with special symbols in description.Scenario: Creating unique Access Group with special symbols in description5 ms47
 Scenario: Creating unique Access Group with special symbols in description.Then I find the group with name "groupName53"5 ms47
 Scenario: Deleting "Cron Schedule" Triggering.And I create a new trigger from the existing creator with previously defined date properties1 ms1
 Scenario: Deleting "Cron Schedule" Triggering.Scenario: Deleting "Cron Schedule" Triggering1 ms1
 Scenario: Deleting "Interval Schedule" Triggering.And I create a new trigger from the existing creator with previously defined date properties1 ms1
 Scenario: Deleting "Interval Schedule" Triggering.Scenario: Deleting "Interval Schedule" Triggering2 ms1
 Scenario: Deleting user in account that is higher in hierarchy.Scenario: Deleting user in account that is higher in hierarchy0.94 sec27
 Scenario: Deleting user in account that is lower in hierarchy.Scenario: Deleting user in account that is lower in hierarchy0.91 sec27
 Scenario: Execute possible docker steps to show its usage.Given List images by name "kapua/kapua-broker:1.5.0-SNAPSHOT"0 ms34
 Scenario: Execute possible docker steps to show its usage.Scenario: Execute possible docker steps to show its usage1 ms34
 Scenario: Init Security Context for all scenarios.Scenario: Init Security Context for all scenarios0.92 sec27
 Scenario: List Endpoints Created From Sub-Account.And I create endpoint with schema "Schema1", domain "abc.com" and port 22221 ms27
 Scenario: List Endpoints Created From Sub-Account.Scenario: List Endpoints Created From Sub-Account2 ms27
 Scenario: List Endpoints From "kapua-sys" Account.Scenario: List Endpoints From "kapua-sys" Account1 ms27
 Scenario: List Endpoints From "kapua-sys" Account.Then I find 3 endpoints1 ms27
 Scenario: List Endpoints From Sub-Account Of Another Sub-Account.And I create endpoint with schema "Schema1", domain "abc.com" and port 22221 ms27
 Scenario: List Endpoints From Sub-Account Of Another Sub-Account.Scenario: List Endpoints From Sub-Account Of Another Sub-Account2 ms27
 Scenario: List Endpoints From Sub-account.And I create endpoint with schema "Schema1", domain "abc.com" and port 22221 ms27
 Scenario: List Endpoints From Sub-account.Scenario: List Endpoints From Sub-account2 ms27
 Scenario: Reset Security Context for all scenarios.Scenario: Reset Security Context for all scenarios0.89 sec27
 Scenario: Restarting a job with valid Package Install step and multiple devices two times.And I confirm the executed job is finished4 ms1
 Scenario: Restarting a job with valid Package Install step and multiple devices two times.Scenario: Restarting a job with valid Package Install step and multiple devices two times5 ms1
 Scenario: Restarting job with valid Package Uninstall and Asset Write steps two times.And I confirm the executed job is finished8 ms1
 Scenario: Restarting job with valid Package Uninstall and Asset Write steps two times.Scenario: Restarting job with valid Package Uninstall and Asset Write steps two times9 ms1
 Scenario: Simple Jetty with rest-api war.Scenario: Simple Jetty with rest-api war2 ms29
 Scenario: Simple Jetty with rest-api war.When REST POST call at "/v1/authentication/user" with JSON "{"password": "kapua-password", "username": "kapua-sys"}"1 ms29
 Scenario: Start Jetty server for all scenarios.Given Start Jetty Server on host "127.0.0.1" at port "8081"1 ms29
 Scenario: Start Jetty server for all scenarios.Scenario: Start Jetty server for all scenarios1 ms29
 Scenario: Start datastore for all scenarios.Given Start Datastore0 ms27
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios1 ms27
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios0.89 sec27
 Scenario: Starting a job with valid Bundle Stop step and multiple devices.And Bundles are requested1 ms1
 Scenario: Starting a job with valid Bundle Stop step and multiple devices.Scenario: Starting a job with valid Bundle Stop step and multiple devices2 ms1
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios0.89 sec27
 Scenario: Stop job with multiple targets and Bundle Start and Package Install steps.And I confirm the step index is 0 and status is "PROCESS_AWAITING"0 ms1
 Scenario: Stop job with multiple targets and Bundle Start and Package Install steps.Scenario: Stop job with multiple targets and Bundle Start and Package Install steps1 ms1
 Scenario: Stop job with multiple targets and Bundle Stop and Package Uninstall steps.And I confirm the step index is 0 and status is "PROCESS_AWAITING"1 ms2
 Scenario: Stop job with multiple targets and Bundle Stop and Package Uninstall steps.Scenario: Stop job with multiple targets and Bundle Stop and Package Uninstall steps1 ms2
 Scenario: Stop job with multiple targets and Configuration Put and Package Uninstall steps.And Configuration is requested1 ms1
 Scenario: Stop job with multiple targets and Configuration Put and Package Uninstall steps.Scenario: Stop job with multiple targets and Configuration Put and Package Uninstall steps1 ms3
 Scenario: Update scheduler end date.And I try to edit end date to 13-12-2020 at 10:001 ms25
 Scenario: Update scheduler end date.Scenario: Update scheduler end date2 ms25
 Scenario: Update trigger definition.And I try to edit trigger definition to "Cron Job"1 ms25
 Scenario: Update trigger definition.Scenario: Update trigger definition2 ms25

All Tests

ClassDurationFail(diff)Skip(diff)Pass(diff)Total(diff)
Scenario: A fresh database must contain 1 default role in the root scope6 ms004+14+1
Scenario: A newly created account must have some metadata5 ms0033
Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic3 ms0088
Scenario: Access info service sanity checks11 ms0044
Scenario: Access service comparison sanity checks7 ms0033
Scenario: Account based ClientInfo data check8 ms0024+1224+12
Scenario: Account exactly on its expiration date5 ms001414
Scenario: Account name must not be mutable4 ms0066
Scenario: Account past its expiration date5 ms001414
Scenario: Account wide metrics check11 ms0028+1428+14
Scenario: Account with future expiration date7 ms001313
Scenario: Account with no expiration date6 ms001313
Scenario: Add Access Info domain permissions to new user10 ms0026+2626+26
Scenario: Add Account permissions to the role in child account11 ms0028+2828+28
Scenario: Add Credential domain permissions to new user10 ms0018+1818+18
Scenario: Add Datastore domain permissions to new user0.12 sec0019+1919+19
Scenario: Add Device Connection domain permissions to kapua-sys user9 ms0011+1111+11
Scenario: Add Device Connection domain permissions to new user8 ms0023+2323+23
Scenario: Add Device Event domain permissions to new user11 ms0016+1616+16
Scenario: Add Device domain permissions to new user9 ms0017+1717+17
Scenario: Add Domain domain permissions to kapua-sys user9 ms0017+1717+17
Scenario: Add Domain domain permissions to new user9 ms0032+3232+32
Scenario: Add Endpoint Permission To The User8 ms0030+3030+30
Scenario: Add Endpoint_info permissions to the role in child account12 ms0030+3030+30
Scenario: Add Group domain permissions to new user15 ms0017+1717+17
Scenario: Add Group permissions to the role in child account12 ms0026+2626+26
Scenario: Add Job domain permissions to new user11 ms0019+1919+19
Scenario: Add Role domain permissions to new user8 ms0017+1717+17
Scenario: Add Role permissions to the role in child account15 ms0026+2626+26
Scenario: Add Scheduler Permissions With Job Permissions8 ms0031+3131+31
Scenario: Add Scheduler Permissions Without Job Permissions9 ms0021+2121+21
Scenario: Add Scheduler permissions to the role in child account11 ms0036+3636+36
Scenario: Add Tag domain permissions to new user10 ms0015+1515+15
Scenario: Add Tag permissions to the role in child account11 ms0026+2626+26
Scenario: Add User domain permissions to new user8 ms0020+2020+20
Scenario: Add account permissions to the role13 ms0019+1919+19
Scenario: Add admin role to the user11 ms0044+4444+44
Scenario: Add and delete Account permissions from the "admin" role15 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" role12 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" role13 ms0014+1414+14
Scenario: Add and delete Role permissions from the "admin" role15 ms0014+1414+14
Scenario: Add and delete User permissions from the "admin" role13 ms0015+1515+15
Scenario: Add datastore permissions to the role3 ms2+23+322+2227+27
Scenario: Add deleted role again11 ms0010+1010+10
Scenario: Add device event permissions to the role13 ms0032+3232+32
Scenario: Add device permissions to the role26 ms0019+1919+19
Scenario: Add device permissions to the role in child account12 ms0026+2626+26
Scenario: Add domain, user and access_info permissions to the role14 ms0023+2323+23
Scenario: Add endpoint_info permissions to the role12 ms0031+3131+31
Scenario: Add group permissions to the role15 ms0018+1818+18
Scenario: Add job permissions to the role13 ms0019+1919+19
Scenario: Add job permissions to the role in child account15 ms0026+2626+26
Scenario: Add role permissions to the role16 ms0019+1919+19
Scenario: Add same permission twice to the same role12 ms0014+1414+14
Scenario: Add same role to user twice13 ms0013+1313+13
Scenario: Add scheduler permissions to the role12 ms0031+3131+31
Scenario: Add tag permissions to the role15 ms0018+1818+18
Scenario: Add user permissions to the role11 ms0019+1919+19
Scenario: Add user permissions to the role in child account14 ms0026+2626+26
Scenario: Adding "Cron Job" Schedule With All Valid Parameters6 ms0010+1010+10
Scenario: Adding "Cron Job" Schedule With All Valid Parameters And Null Cron Value5 ms0010+1010+10
Scenario: Adding "Cron Job" Schedule With All Valid Parameters Except Cron Format4 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 time5 ms0012+1212+12
Scenario: Adding "Cron Job" Schedule With Non-Unique End Date Parameter4 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 Only4 ms0011+1111+11
Scenario: Adding "Cron Job" Schedule With the same Start and End time4 ms0012+1212+12
Scenario: Adding "Cron Job" Schedule Without The Start Date Parameter6 ms0010+1010+10
Scenario: Adding "Device Connect" Schedule With All Valid Parameters4 ms008+88+8
Scenario: Adding "Device Connect" Schedule With End Date Only6 ms0010+1010+10
Scenario: Adding "Device Connect" Schedule With End Time before Start time6 ms0011+1111+11
Scenario: Adding "Device Connect" Schedule With Max Length Name4 ms008+88+8
Scenario: Adding "Device Connect" Schedule With Min Length Name5 ms008+88+8
Scenario: Adding "Device Connect" Schedule With Name Only6 ms009+99+9
Scenario: Adding "Device Connect" Schedule With Non-Unique End Date Parameter5 ms0013+1313+13
Scenario: Adding "Device Connect" Schedule With Non-Unique Name4 ms0014+1414+14
Scenario: Adding "Device Connect" Schedule With Non-Unique Start Date Parameter4 ms0011+1111+11
Scenario: Adding "Device Connect" Schedule With Start Date Only4 ms0010+1010+10
Scenario: Adding "Device Connect" Schedule With the same Start and End time4 ms0011+1111+11
Scenario: Adding "Device Connect" Schedule Without Name4 ms0010+1010+10
Scenario: Adding "Device Connect" Schedule Without The Start Date Parameter5 ms009+99+9
Scenario: Adding "Empty" Tag To Device3 ms005+55+5
Scenario: Adding "Interval Job" Schedule With All Valid Parameters5 ms0010+1010+10
Scenario: Adding "Interval Job" Schedule With End Date Only5 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 Name4 ms0010+1010+10
Scenario: Adding "Interval Job" Schedule With Min Length Name4 ms0010+1010+10
Scenario: Adding "Interval Job" Schedule With Name Only6 ms0010+1010+10
Scenario: Adding "Interval Job" Schedule With Non-Unique End Date Parameter4 ms0016+1616+16
Scenario: Adding "Interval Job" Schedule With Non-Unique Name4 ms0015+1515+15
Scenario: Adding "Interval Job" Schedule With Non-Unique Start Date Parameter5 ms0015+1515+15
Scenario: Adding "Interval Job" Schedule With Null Interval Number5 ms0012+1212+12
Scenario: Adding "Interval Job" Schedule With Start Date Only4 ms0011+1111+11
Scenario: Adding "Interval Job" Schedule With the same Start and End time4 ms0012+1212+12
Scenario: Adding "Interval Job" Schedule Without Interval Number4 ms0011+1111+11
Scenario: Adding "Interval Job" Schedule Without The Start Date Parameter4 ms009+99+9
Scenario: Adding "Interval Job" Schedule Without a Name5 ms0011+1111+11
Scenario: Adding "admin" role to a user in a child account20 ms0014+1414+14
Scenario: Adding "admin" role to multiple users14 ms0018+1818+18
Scenario: Adding "admin" role twice14 ms0013+1313+13
Scenario: Adding Account:Delete permission to user in same scope11 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 scope8 ms0021+2121+21
Scenario: Adding Account:Read and Account:Write permissions to user in same scope10 ms0019+1919+19
Scenario: Adding Account:Read permission to user in same scope9 ms0023+2323+23
Scenario: Adding Account:Read permission to user in sub-account scope9 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 scope8 ms0025+2525+25
Scenario: Adding Account:Write permission to user in sub-account scope9 ms0031+3131+31
Scenario: Adding Multiple Permissions To User9 ms0020+2020+20
Scenario: Adding One Permission To User11 ms0011+1111+11
Scenario: Adding Permissions To Child User8 ms0018+1818+18
Scenario: Adding Permissions To Parallel User15 ms0018+1818+18
Scenario: Adding Previously Deleted Permission10 ms0028+2828+28
Scenario: Adding Previously Deleted Tag From Device Again2 ms0011+1111+11
Scenario: Adding Regular Device to a Group With Description6 ms0010+1010+10
Scenario: Adding Regular Device to a Group Without a Description5 ms0012+1212+12
Scenario: Adding Regular Group Without Description to Device9 ms0010+1010+10
Scenario: Adding Regular Tag Without Description To Device6 ms006+66+6
Scenario: Adding Same Regular Group Without Description to Device7 ms0014+1414+14
Scenario: Adding Tag With Long Name Without Description To Device5 ms006+66+6
Scenario: Adding Tag With Numbers Without Description To Device2 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 scope9 ms0017+1717+17
Scenario: Adding all Account permissions to user in sub-account scope8 ms0024+2424+24
Scenario: Adding existing roles to user15 ms0015+1515+15
Scenario: Adding role from child account to user in new child account15 ms0015+1515+15
Scenario: Adding role to multiple users in child account14 ms0018+1818+18
Scenario: Adding same role twice to user in child account14 ms0015+1515+15
Scenario: Adding the same role to user twice in child account14 ms0013+1313+13
Scenario: All device parameters must match the device creator8 ms0033
Scenario: Assign 100 Devices to One Group13 ms0011+1111+11
Scenario: B1 Broker publish to CTRL_ACC_REPLY4 ms0-20-29+49
Scenario: B10 Broker create sub-topic on ACL_DATA_ACC is not allowed5 ms0-20-29+49
Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed3 ms0-20-28+48
Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI5 ms0099
Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed4 ms0-20-29+49
Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed4 ms0-20-28+48
Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY4 ms0-20-29+49
Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY5 ms0099
Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account3 ms0-20-29+49
Scenario: B5 Broker publish to CTRL_ACC is not allowed4 ms0099
Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed5 ms0099
Scenario: B7 Broker subscribe on CTRL_ACC is not allowed3 ms0-20-28+48
Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI3 ms0099
Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed4 ms0-20-29+49
Scenario: Basic Device Event queries9 ms0010-410-4
Scenario: Birth and applications event handling4 ms001212
Scenario: Birth and death message handling7 ms001212
Scenario: Birth and missing event handling4 ms001212
Scenario: Birth message handling from a new device25 ms001313
Scenario: Birth message handling from an existing device4 ms001212
Scenario: Both the parent and child accounts do not expire5 ms001111
Scenario: Both the parent and child accounts have the same expiration date5 ms001111
Scenario: Bug when user can retrieve user in another account if it has other account's user id2 ms2+212+1219+1933+33
Scenario: Captured date based ClientInfo data check8 ms0030+1530+15
Scenario: Case sensitiveness of named device searches4 ms004+44+4
Scenario: Change an existing step name3 ms0011+311+3
Scenario: Change role name so it is too short2 ms006+66+6
Scenario: Change the account parent path3 ms0055
Scenario: Changing Client ID5 ms009+99+9
Scenario: Changing Description On Group With Long Description10 ms007+77+7
Scenario: Changing Description On Group With Long Name7 ms007+77+7
Scenario: Changing Description On Group With Numbers In Name5 ms0010+1010+10
Scenario: Changing Description On Group With Permitted Symbols4 ms007+77+7
Scenario: Changing Description On Group With Short Description5 ms007+77+7
Scenario: Changing Description On Group With Short Name5 ms007+77+7
Scenario: Changing Description On Tag With Long Description3 ms004+44+4
Scenario: Changing Description On Tag With Long Name3 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 Description5 ms004+44+4
Scenario: Changing Description On Tag With Short Name4 ms004+44+4
Scenario: Changing Device Status To Disabled4 ms009+99+9
Scenario: Changing Device Status To Enabled5 ms009+99+9
Scenario: Changing Group's Description To Non-Uniqe One4 ms007+77+7
Scenario: Changing Group's Description To Uniqe One4 ms007+77+7
Scenario: Changing Group's Name To Contain Invalid Symbols In Name Without Changing Description7 ms008+88+8
Scenario: Changing Group's Name To Contain Permitted Symbols In Name Without Changing Description5 ms007+77+7
Scenario: Changing Group's Name To Non-Unique One5 ms009+99+9
Scenario: Changing Group's Name To Short One Without Changing Description5 ms007+77+7
Scenario: Changing Group's Name To Unique One5 ms007+77+7
Scenario: Changing Group's Name To a Long One Without Changing Description6 ms007+77+7
Scenario: Changing Group's Name To a Too Long One Without Changing Description7 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 One3 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 Description2 ms005+55+5
Scenario: Changing Tag's Name To Non-Unique One3 ms006+66+6
Scenario: Changing Tag's Name To Short One Without Description3 ms007+77+7
Scenario: Changing Tag's Name To Unique One5 ms007+77+7
Scenario: Changing Tag's Name To a Long One Without Description5 ms007+77+7
Scenario: Changing Tag's Name To a Too Long One Without Description7 ms005+55+5
Scenario: Changing Tag's Name To a Too Short One Without Description3 ms005+55+5
Scenario: Changing description of a nonexisting role4 ms007+77+7
Scenario: Changing job description to non-unique one4 ms007+77+7
Scenario: Changing job description to the long one4 ms006+66+6
Scenario: Changing job description to unique one4 ms006+66+6
Scenario: Changing job description to very short one7 ms007+77+7
Scenario: Changing job name to a long one without description10 ms007+77+7
Scenario: Changing job name to a too long one without description4 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 description11 ms004+44+4
Scenario: Changing job name to contain permitted symbols in name without description3 ms005+55+5
Scenario: Changing job name to non-unique one5 ms008+88+8
Scenario: Changing job name to short one without description4 ms007+77+7
Scenario: Changing job name to unique one6 ms009+99+9
Scenario: Changing name of a nonexisting role3 ms007+77+7
Scenario: Changing role description to a valid one2 ms006+66+6
Scenario: Changing role name so it is too long0 ms006+66+6
Scenario: Changing role name to contain special character2 ms004+44+4
Scenario: Changing role name to null3 ms006+66+6
Scenario: Changing role's name to a valid one2 ms006+66+6
Scenario: Channel info queries based on datastore channel filters8 ms0050+2550+25
Scenario: ChannelInfo client ID and topic data based on the client id8 ms0028+1428+14
Scenario: ChannelInfo client ID based on the account id9 ms0026+1326+13
Scenario: ChannelInfo last published date9 ms0030+1530+15
Scenario: ChannelInfo topic data based on the account id10 ms0026+1326+13
Scenario: Check account properties4 ms0044
Scenario: Check the Device Connection Domain data seetting2 ms0022
Scenario: Check the database cache coherency11 ms0030+1530+15
Scenario: Check the mapping for message semantic topics10 ms0030+1530+15
Scenario: Check the message store7 ms0020+1020+10
Scenario: Check the sanity of the Device Connection Domain data initialization2 ms0022
Scenario: Child account expires after parent5 ms0099
Scenario: Child account expires before parent4 ms001111
Scenario: Child account has null expiration date5 ms0099
Scenario: Client Id based ClientInfo data check11 ms0028+1428+14
Scenario: Compare domain entries6 ms003+13+1
Scenario: Connect to the system and publish some data0.14 sec0-20-1522+1722
Scenario: Connection Service factory sanity checks2 ms0022
Scenario: Count access info entities in a specific scope9 ms0024+524+5
Scenario: Count access role entities by scope9 ms0039+639+6
Scenario: Count connections in empty scope3 ms0044
Scenario: Count connections in scope5 ms0055
Scenario: Count devices with a specific BIOS version2 ms0066
Scenario: Count domains in a blank database6 ms004+14+1
Scenario: Count domains in the database5 ms007+17+1
Scenario: Count events in empty scope6 ms006-46-4
Scenario: Count groups5 ms0014+214+2
Scenario: Count groups in a blank database9 ms005+25+2
Scenario: Count job items3 ms007+37+3
Scenario: Count job items in wrong - empty - scope3 ms008+88+8
Scenario: Count role permissions in specific scopes7 ms0018+318+3
Scenario: Count roles in specific scopes6 ms0015+215+2
Scenario: Count step definition items4 ms0044
Scenario: Count step definitions in wrong (empty) scope4 ms0011
Scenario: Count steps in the database4 ms0014+314+3
Scenario: Count user6 ms0066
Scenario: Counting created roles items in the DB2 ms005+55+5
Scenario: Create a regular event14 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 value0 ms004+44+4
Scenario: Create a valid job entry18 ms006+66+6
Scenario: Create an event with a null scope ID38 ms007-37-3
Scenario: Create and count several execution items for a job2 ms0011+211+2
Scenario: Create index with specific prefix4 ms0012-112-1
Scenario: Create multiple users3 ms0055
Scenario: Create regular access permissions10 ms0020+520+5
Scenario: Create same user in different accounts0.89 sec1+114+14015+15
Scenario: Create scheduler with correct end date3 ms2+21+15+58+8
Scenario: Create scheduler with empty schedule name11 ms008+88+8
Scenario: Create scheduler with end date before start date15 ms2+21+16+69+9
Scenario: Create scheduler with invalid Retry Interval property6 ms009+99+9
Scenario: Create scheduler with invalid cron job trigger property33 ms009+99+9
Scenario: Create scheduler with invalid schedule name10 ms008+88+8
Scenario: Create scheduler with short schedule name8 ms008+88+8
Scenario: Create scheduler with too long schedule name6 ms008+88+8
Scenario: Create scheduler with valid Retry Interval property8 ms007+77+7
Scenario: Create scheduler with valid cron job trigger property10 ms007+77+7
Scenario: Create scheduler with valid schedule name18 ms006+66+6
Scenario: Create scheduler without Cron Job Trigger property6 ms009+99+9
Scenario: Create scheduler without Retry Interval property6 ms009+99+9
Scenario: Create scheduler without start date7 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 length5 ms0055
Scenario: Create user with short name26 ms0055
Scenario: Create user with special characters in his name5 ms0055
Scenario: Create with permissions42 ms0014+414+4
Scenario: Create with permissions and a role10 ms0017+417+4
Scenario: Create with permissions and a role in the wrong scope6 ms0015+515+5
Scenario: Creating 100 Sub-accounts While InfiniteChildAccounts Is Set To True7 ms007+77+7
Scenario: Creating A Device With Disabled Status4 ms007+77+7
Scenario: Creating A Device With Enabled Status6 ms007+77+7
Scenario: Creating A Device With Long Display Name3 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 Symbols4 ms007+77+7
Scenario: Creating A Device With No Name5 ms008+88+8
Scenario: Creating A Device With Non-unique Display Name4 ms007+77+7
Scenario: Creating A Device With Non-unique Name4 ms0010+1010+10
Scenario: Creating A Device With Short Display Name4 ms007+77+7
Scenario: Creating A Device With Short Name4 ms007+77+7
Scenario: Creating A Device With Too Long Display Name3 ms008+88+8
Scenario: Creating A Device With Too Long Name4 ms008+88+8
Scenario: Creating A Device With Unique Name5 ms009+99+9
Scenario: Creating A Valid Account4 ms005+55+5
Scenario: Creating An Account With Long Name5 ms005+55+5
Scenario: Creating An Account With Long Organization Name14 ms005+55+5
Scenario: Creating An Account With Non-unique Name6 ms008+88+8
Scenario: Creating An Account With Numbers And Valid Symbols In Name7 ms005+55+5
Scenario: Creating An Account With Short Name4 ms005+55+5
Scenario: Creating An Account With Short Organization Name6 ms005+55+5
Scenario: Creating An Account With Special Symbols In Organization Name5 ms005+55+5
Scenario: Creating An Account With Too Long Organization Name5 ms006+66+6
Scenario: Creating An Account With Unique Name5 ms007+77+7
Scenario: Creating An Account With Wrong TLD Format In Email4 ms0010+1010+10
Scenario: Creating An Account Without Email5 ms006+66+6
Scenario: Creating An Account Without Name5 ms006+66+6
Scenario: Creating An Account Without Ogranization Name6 ms006+66+6
Scenario: Creating And Account Without "@" In Email7 ms006+66+6
Scenario: Creating Devices And Than Setting Device Service So It Does Not Allow Devices6 ms0012+1212+12
Scenario: Creating Devices And Then Changing Device Service Values13 ms0010+1010+10
Scenario: Creating Devices Under Account That Allows Infinite Child Devices5 ms0010+1010+10
Scenario: Creating Devices Under Account That Does Not Allow Devices4 ms009+99+9
Scenario: Creating Devices Under Account That Has Limited Child Devices7 ms0013+1313+13
Scenario: Creating Endpoint Non-Unique "Domain Name"3 ms008+88+8
Scenario: Creating Endpoint Non-Unique "Port"4 ms008+88+8
Scenario: Creating Endpoint Non-Unique "Schema"4 ms009+99+9
Scenario: Creating Endpoint With "Domain Name" Only4 ms006+66+6
Scenario: Creating Endpoint With "Port" Only3 ms006+66+6
Scenario: Creating Endpoint With "Schema" Only4 ms006+66+6
Scenario: Creating Endpoint With Disabled Secure Field4 ms006+66+6
Scenario: Creating Endpoint With Enabled Secure Field4 ms006+66+6
Scenario: Creating Endpoint With Invalid "Domain Name"3 ms006+66+6
Scenario: Creating Endpoint With Invalid "Schema" containing symbols2 ms006+66+6
Scenario: Creating Endpoint With Long "Domain Name"3 ms005+55+5
Scenario: Creating Endpoint With Max Length "Port"4 ms005+55+5
Scenario: Creating Endpoint With NULL parameters4 ms006+66+6
Scenario: Creating Endpoint With Schema Containing "http://"3 ms006+66+6
Scenario: Creating Endpoint With Schema Containing "https://"3 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"4 ms006+66+6
Scenario: Creating Endpoint With Too Long "Schema"3 ms006+66+6
Scenario: Creating Endpoint Without "Domain Name"4 ms006+66+6
Scenario: Creating Endpoint Without "Port"5 ms006+66+6
Scenario: Creating Endpoint Without "Schema"4 ms006+66+6
Scenario: Creating Endpoint Without Long "Schema"3 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 Description6 ms007+77+7
Scenario: Creating Group With Long Name With Valid Description5 ms006+66+6
Scenario: Creating Group With Long Name Without Description6 ms006+66+6
Scenario: Creating Group With Numbers In Name With Valid Description6 ms008+88+8
Scenario: Creating Group With Permitted Symbols And Numbers In Name Without Description5 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 Description6 ms006+66+6
Scenario: Creating Group With Short Name Without Description10 ms006+66+6
Scenario: Creating Group With Too Long Name With Valid Description7 ms007+77+7
Scenario: Creating Group With Too Long Name Without Description5 ms007+77+7
Scenario: Creating Group With Too Short Name With Valid Description5 ms007+77+7
Scenario: Creating Group With Too Short Name Without Description6 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 Groups6 ms0011+1111+11
Scenario: Creating Groups And Then Changing InfiniteChildGroups To False And Set MaxNumberChildGroups5 ms0010+1010+10
Scenario: Creating Groups Under Account That Allows Infinite Child Groups5 ms009+99+9
Scenario: Creating Groups Under Account That Does Not Allow Groups6 ms009+99+9
Scenario: Creating Groups Under Account That Has Limited Child Groups6 ms0012+1212+12
Scenario: Creating Jobs And Than Setting Job Service So It Does Not Allow Jobs5 ms0012+1212+12
Scenario: Creating Jobs And Then Changing Job Service Values4 ms0010+1010+10
Scenario: Creating Jobs Under Account That Allows Infinite Child Devices4 ms0010+1010+10
Scenario: Creating Jobs Under Account That Does Not Allow Jobs7 ms009+99+9
Scenario: Creating Jobs Under Account That Has Limited Child Jobs4 ms0013+1313+13
Scenario: Creating Non-Unique Group With Valid Description5 ms008+88+8
Scenario: Creating Non-Unique Tag With Valid Description4 ms005+55+5
Scenario: Creating Non-unique Group Without Description8 ms008+88+8
Scenario: Creating Non-unique Tag Without Description7 ms004+44+4
Scenario: Creating Roles And Than Setting Role Service So It Does Not Allow Roles5 ms0011+1111+11
Scenario: Creating Roles And Then Changing Role Service Values5 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 Roles5 ms009+99+9
Scenario: Creating Roles Under Account That Has Limited Child Roles5 ms0012+1212+12
Scenario: Creating Sub-accounts When InfiniteChildAccoounts Is Set To False And maxNumberChildAccounts Is Set4 ms0013+1313+13
Scenario: Creating Sub-accounts When InfiniteChildAccoounts Is Set To True And maxNumberChildAccounts Is Set4 ms0014+1414+14
Scenario: Creating Sub-accounts When InfiniteChildAccounts Is Set To False4 ms009+99+9
Scenario: Creating Sub-accounts when InfiniteChildAccounts Is Set To True4 ms0012+1212+12
Scenario: Creating Tag With Invalid Symbols In Name With Valid Description5 ms004+44+4
Scenario: Creating Tag With Invalid Symbols In Name Without Description4 ms004+44+4
Scenario: Creating Tag With Long Name With Valid Description4 ms004+44+4
Scenario: Creating Tag With Long Name Without Description5 ms004+44+4
Scenario: Creating Tag With Numbers In Name With Valid Description3 ms004+44+4
Scenario: Creating Tag With Numbers In Name Without Description4 ms004+44+4
Scenario: Creating Tag With Permitted Symbols In Name With Valid Description3 ms004+44+4
Scenario: Creating Tag With Permitted Symbols In Name Without Description12 ms004+44+4
Scenario: Creating Tag With Short Name With Valid Description4 ms004+44+4
Scenario: Creating Tag With Short Name Without Description7 ms004+44+4
Scenario: Creating Tag With Too Long Name With Valid Description4 ms004+44+4
Scenario: Creating Tag With Too Long Name Without Description6 ms004+44+4
Scenario: Creating Tag With Too Short Name With Valid Description2 ms004+44+4
Scenario: Creating Tag With Too Short Name Without Description6 ms004+44+4
Scenario: Creating Tag Without a Name And With Valid Description4 ms004+44+4
Scenario: Creating Tag Without a Name And Without Description5 ms004+44+4
Scenario: Creating Tags And Than Setting Tag Service So It Does Not Allow Tags6 ms0011+1111+11
Scenario: Creating Tags And Then Changing Tag Service Values4 ms0010+1010+10
Scenario: Creating Tags Under Account That Allows Infinite Child Devices5 ms0010+1010+10
Scenario: Creating Tags Under Account That Does Not Allow Tags5 ms009+99+9
Scenario: Creating Tags Under Account That Has Limited Child Tags4 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 Description7 ms006+66+6
Scenario: Creating Unique Group With Unique Description5 ms006+66+6
Scenario: Creating Unique Group Without Description6 ms006+66+6
Scenario: Creating Unique Tag With Long Description3 ms004+44+4
Scenario: Creating Unique Tag With Non-unique Description12 ms005+55+5
Scenario: Creating Unique Tag With Short Description4 ms004+44+4
Scenario: Creating Unique Tag With Unique Description4 ms004+44+4
Scenario: Creating Unique Tag Without Description13 ms004+44+4
Scenario: Creating Users And Than Setting User Service So It Does Not Allow Users7 ms0011+1111+11
Scenario: Creating Users And Then Changing User Service Values4 ms0010+1010+10
Scenario: Creating Users Under Account That Allows Infinite Child Users5 ms0010+1010+10
Scenario: Creating Users Under Account That Does Not Allow Users6 ms009+99+9
Scenario: Creating Users Under Account That Has Limited Child Users4 ms0012+1212+12
Scenario: Creating Valid Endpoint3 ms006+66+6
Scenario: Creating a Access Group with invalid special symbols in name0 ms004+44+4
Scenario: Creating a Device With Permitted Symbols in its Display Name5 ms007+77+7
Scenario: Creating a Device With Unique Display Name4 ms008+88+8
Scenario: Creating a job with name only18 ms006+66+6
Scenario: Creating a job with null name14 ms005+55+5
Scenario: Creating a job without name with valid description5 ms005+55+5
Scenario: Creating a new PASSWORD Credential meeting a custom length requirement4 ms004+44+4
Scenario: Creating a new PASSWORD Credential meeting the standard length requirement15 ms003+33+3
Scenario: Creating a new PASSWORD Credential not meeting a custom length requirement8 ms005+55+5
Scenario: Creating a new PASSWORD Credential not meeting the standard length requirement8 ms004+44+4
Scenario: Creating a role name with allowed symbols in its name3 ms005+55+5
Scenario: Creating a role with 255 characters long description2 ms005+55+5
Scenario: Creating a role with a name and description that contain digits only3 ms005+55+5
Scenario: Creating a role with forbidden symbols in its name0 ms004+44+4
Scenario: Creating a role with name only2 ms005+55+5
Scenario: Creating a role with null name2 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 description26 ms004+44+4
Scenario: Creating a role with the name that contains digits1 ms005+55+5
Scenario: Creating a role with too long name1 ms005+55+5
Scenario: Creating a role with too short name2 ms005+55+5
Scenario: Creating a role with valid name and with too long description3 ms003+33+3
Scenario: Creating a role wtih 255 characters long name2 ms005+55+5
Scenario: Creating a single device with case sensitive clientID3 ms005+55+5
Scenario: Creating a single device with clientID that contains 255 characters14 ms005+55+5
Scenario: Creating a single device with clientID that contains 256 characters2 ms004+44+4
Scenario: Creating a single device with clientID that contains invalid character3 ms004+44+4
Scenario: Creating a single device with clientID that contains invalid characters3 ms004+44+4
Scenario: Creating a single device with spaces in clientID4 ms005+55+5
Scenario: Creating a single device with valid clientID8 ms005+55+5
Scenario: Creating a valid Access Group with numbers in name3 ms005+55+5
Scenario: Creating a valid Access Group with only numbers in name4 ms005+55+5
Scenario: Creating a valid Access Group with unique name4 ms005+55+5
Scenario: Creating a valid Access Group with valid special symbols in name3 ms005+55+5
Scenario: Creating a valid role2 ms005+55+5
Scenario: Creating an Access Group with empty name4 ms004+44+4
Scenario: Creating an Access Group with long name4 ms005+55+5
Scenario: Creating an Access Group with short name3 ms005+55+5
Scenario: Creating an Access Group with too long name3 ms004+44+4
Scenario: Creating an Access Group with too short name3 ms004+44+4
Scenario: Creating an Access Group without name and with description3 ms004+44+4
Scenario: Creating and Deleting Endpoint Two Times7 ms0025+2525+25
Scenario: Creating index with regular user5 ms002525
Scenario: Creating job with invalid symbols in name without description0 ms004+44+4
Scenario: Creating job with long name and valid description5 ms006+66+6
Scenario: Creating job with long name without description7 ms006+66+6
Scenario: Creating job with numbers in name and valid description5 ms006+66+6
Scenario: Creating job with numbers in name without description6 ms006+66+6
Scenario: Creating job with permitted symbols in name without description7 ms003+33+3
Scenario: Creating job with short name and valid job description6 ms006+66+6
Scenario: Creating job with short name without description7 ms006+66+6
Scenario: Creating job with too long name and valid description5 ms005+55+5
Scenario: Creating job with too long name without description2 ms005+55+5
Scenario: Creating job with too short name and valid description6 ms005+55+5
Scenario: Creating job with too short name without description8 ms005+55+5
Scenario: Creating job without name and without description6 ms005+55+5
Scenario: Creating new device and tagging it with specific Tag5 ms001414
Scenario: Creating new device, tagging it with specific Tag and then deleting this Tag3 ms001616
Scenario: Creating non-unique Access Group4 ms005+55+5
Scenario: Creating non-unique Access Group with unique description4 ms005+55+5
Scenario: Creating non-unique job name with valid job description5 ms007+77+7
Scenario: Creating two device with the same clientID4 ms005+55+5
Scenario: Creating two indexes with daily index6 ms001717
Scenario: Creating two indexes with hourly index6 ms001717
Scenario: Creating two indexes with weekly index6 ms001717
Scenario: Creating two roles with the same description2 ms006+66+6
Scenario: Creating two roles with the same name3 ms007+77+7
Scenario: Creating unique Access Group with long description3 ms005+55+5
Scenario: Creating unique Access Group with non-unique description3 ms006+66+6
Scenario: Creating unique Access Group with numbers in description3 ms005+55+5
Scenario: Creating unique Access Group with only numbers in description3 ms005+55+5
Scenario: Creating unique Access Group with short description3 ms005+55+5
Scenario: Creating unique Access Group with special symbols in description10 ms2+21+11+14+4
Scenario: Creating unique Access Group with unique description4 ms005+55+5
Scenario: Creating unique job with long description10 ms006+66+6
Scenario: Creating unique job with non-unique description5 ms0010+1010+10
Scenario: Creating unique job with short description5 ms006+66+6
Scenario: Creating user11 ms0055
Scenario: Creation of access role with neither acess info and role entities7 ms0012+412+4
Scenario: Creation of access role without an acess info entity7 ms0012+412+4
Scenario: D1 Device publish to CTRL_ACC_REPLY3 ms0-20-29+49
Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI5 ms0099
Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed6 ms0-20-29+49
Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed5 ms0077
Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY6 ms0-20-29+49
Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY4 ms0099
Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account3 ms0-20-29+49
Scenario: D5 Device subscribe - publish - admin on CTRL_ACC3 ms0099
Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI5 ms0099
Scenario: D7 Device publish to ACL_DATA_ACC is not allowed5 ms0-20-29+49
Scenario: D8 Device create sub-topic on ACL_DATA_ACC is not allowed5 ms0-20-29+49
Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed5 ms0-20-28+48
Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed4 ms0-20-29+49
Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI6 ms0099
Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed5 ms0-20-29+49
Scenario: DM13 Data manage subscribe on ACL_CTRL_ACC_NOTIFY is not allowed3 ms0-20-28+48
Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY6 ms0-20-29+49
Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY6 ms0099
Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account5 ms0-20-29+49
Scenario: DM5 Data manage publish to CTRL_ACC is not allowed6 ms0099
Scenario: DM6 Data manage create sub-topic on CTRL_ACC is not allowed5 ms0099
Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed4 ms0-20-28+48
Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI3 ms0099
Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC5 ms0099
Scenario: DV1 Data view publish to CTRL_ACC_REPLY3 ms0-20-29+49
Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed5 ms0-20-29+49
Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed2 ms001010
Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed3 ms0099
Scenario: DV13 Data view create sub-topic on ACL_CTRL_ACC_CLI is not allowed5 ms0099
Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed4 ms0-20-29+49
Scenario: DV17 Data view subscribe on ACL_CTRL_ACC_NOTIFY is not allowed4 ms0-20-28+48
Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY4 ms0-20-29+49
Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY3 ms0099
Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account6 ms0-20-29+49
Scenario: DV5 Data view publish to CTRL_ACC is not allowed3 ms0099
Scenario: DV6 Data view create sub-topic on CTRL_ACC is not allowed3 ms0099
Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed5 ms0-20-28+48
Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI3 ms0099
Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed5 ms0-20-29+49
Scenario: Decreasing MaxNumberChildAccounts When Sub-accounts Are Already Created5 ms0015+1515+15
Scenario: Delete Kapua system user5 ms0055
Scenario: Delete a access info entity with permissions and roles11 ms0017+817+8
Scenario: Delete a connection from the database3 ms008+18+1
Scenario: Delete a group from the database6 ms0010+410+4
Scenario: Delete a group from the database - Unknown group ID5 ms006+26+2
Scenario: Delete a job2 ms0011+311+3
Scenario: Delete a job execution item3 ms008+28+2
Scenario: Delete a job execution item twice4 ms009+29+2
Scenario: Delete a job twice3 ms0010+310+3
Scenario: Delete a non existent event8 ms007-47-4
Scenario: Delete a non existing connection3 ms007+17+1
Scenario: Delete a non existing permission entity7 ms0016+416+4
Scenario: Delete a non existing role entry6 ms0011+311+3
Scenario: Delete a non-existing step3 ms0012+312+3
Scenario: Delete a nonexistent domain8 ms005+15+1
Scenario: Delete a step definition4 ms0088
Scenario: Delete a step definition twice4 ms0077
Scenario: Delete access role from user12 ms0012+1212+12
Scenario: Delete an access info entity twice12 ms0011+311+3
Scenario: Delete an access info entity using the wrong scope ID14 ms0011+311+3
Scenario: Delete an existing access info entity10 ms0012+312+3
Scenario: Delete an existing access permission entity8 ms0015+415+4
Scenario: Delete an existing access role entry10 ms0022+422+4
Scenario: Delete an existing account5 ms0055
Scenario: Delete an existing device from the registry4 ms0044
Scenario: Delete an existing event5 ms009-49-4
Scenario: Delete an existing role5 ms0010+510+5
Scenario: Delete an existing role twice7 ms0016+516+5
Scenario: Delete an existing step3 ms0011+311+3
Scenario: Delete items based on query results11 ms0084+4284+42
Scenario: Delete items by date ranges0.69 sec00132+132132+132
Scenario: Delete items by the datastore ID9 ms0066+3366+33
Scenario: Delete middle child expiration7 ms001515
Scenario: Delete nonexisting account15 ms0044
Scenario: Delete nonexisting role permission5 ms0013+313+3
Scenario: Delete parent expiration41 ms001414
Scenario: Delete permissions from role11 ms0018+1818+18
Scenario: Delete role permissions4 ms0010+310+3
Scenario: Delete scheduler5 ms008+88+8
Scenario: Delete scheduler which doesn't exist6 ms005+55+5
Scenario: Delete the Kapua system account3 ms0055
Scenario: Delete the last created domain entry7 ms008+18+1
Scenario: Delete user4 ms0066
Scenario: Delete user that doesn't exist6 ms0055
Scenario: Deleting "Cron Schedule" Triggering2 ms2+24+47+713+13
Scenario: Deleting "Device Schedule" Triggering5 ms0011+1111+11
Scenario: Deleting "Interval Schedule" Triggering3 ms2+24+47+713+13
Scenario: Deleting Device With Disabled Status4 ms0010+1010+10
Scenario: Deleting Device With Enabled Status5 ms0010+1010+10
Scenario: Deleting Endpoint Domain Name And Leaving it Empty3 ms008+88+8
Scenario: Deleting Endpoint Which Does Not Exist4 ms006+66+6
Scenario: Deleting Existing Group5 ms008+88+8
Scenario: Deleting Existing Group And Creating It Again With Same Name5 ms0012+1212+12
Scenario: Deleting Existing Tag And Creating It Again With Same Name3 ms007+77+7
Scenario: Deleting Group's Name And Leaving It Empty Without Changing Description5 ms008+88+8
Scenario: Deleting Non-Existent Tag3 ms007+77+7
Scenario: Deleting Tag From Device3 ms008+88+8
Scenario: Deleting Tag's Name And Leaving It Empty Without Description4 ms005+55+5
Scenario: Deleting Unexisitng Group4 ms0011+1111+11
Scenario: Deleting a Permission12 ms0021+2121+21
Scenario: Deleting a non-existing Access Group2 ms006+66+6
Scenario: Deleting a role twice0 ms007+77+7
Scenario: Deleting admin role11 ms007+77+7
Scenario: Deleting an existing Access Group2 ms005+55+5
Scenario: Deleting an existing Access Group and creating it again with the same name2 ms007+77+7
Scenario: Deleting an existing role2 ms006+66+6
Scenario: Deleting default permissions from admin role14 ms0012+1212+12
Scenario: Deleting existing tag6 ms009+99+9
Scenario: Deleting role after adding it to user12 ms0014+1414+14
Scenario: Deleting role after it has been added to user in child account12 ms0016+1616+16
Scenario: Deleting user in account that is higher in hierarchy0.94 sec1+122+220-2323
Scenario: Deleting user in account that is lower in hierarchy0.91 sec1+123+230-2424
Scenario: Device connection update3 ms007+17+1
Scenario: Device factory sanity checks2 ms0022
Scenario: Device queries3 ms0010-310-3
Scenario: Device query - find by BIOS version3 ms0077
Scenario: Domain entry query6 ms005+15+1
Scenario: Domain with null actions6 ms005+15+1
Scenario: Domain with null name6 ms005+15+1
Scenario: Domains with duplicate names14 ms008+18+1
Scenario: Duplicate group name in root scope7 ms0010+210+2
Scenario: Duplicate role names4 ms007+37+3
Scenario: Editing Access Group description to description with numbers2 ms005+55+5
Scenario: Editing Access Group description to description with only numbers2 ms005+55+5
Scenario: Editing Access Group description to description with special symbols2 ms004+44+4
Scenario: Editing Access Group description to long description2 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 one2 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 numbers10 ms007+77+7
Scenario: Editing Access Group name to name that contains only numbers2 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 symbols7 ms007+77+7
Scenario: Editing Access Group name to non-unique one4 ms006+66+6
Scenario: Editing Access Group name to short one2 ms007+77+7
Scenario: Editing Access Group name to too short one7 ms005+55+5
Scenario: Editing Access Group name to valid one3 ms007+77+7
Scenario: Editing Endpoint Domain Name So It Contains Invalid Symbols3 ms008+88+8
Scenario: Editing Endpoint Domain Name So It Contains Only Numbers4 ms008+88+8
Scenario: Editing Endpoint Domain Name So It Has Max Value3 ms007+77+7
Scenario: Editing Endpoint Domain Name So It Has Min Value5 ms007+77+7
Scenario: Editing Endpoint Domain Name To Non-unique Value2 ms009+99+9
Scenario: Editing Endpoint Domain Name To Unique Value3 ms007+77+7
Scenario: Editing Endpoint Port To Non-unique Value3 ms009+99+9
Scenario: Editing Endpoint Port To Unique Value4 ms007+77+7
Scenario: Editing Endpoint Schema And Leaving It Empty3 ms008+88+8
Scenario: Editing Endpoint Schema So It Contains "http://"3 ms008+88+8
Scenario: Editing Endpoint Schema So It Contains "https://"4 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 Length3 ms007+77+7
Scenario: Editing Endpoint Schema So It Has Min Length3 ms007+77+7
Scenario: Editing Endpoint Schema To Non-unique Value3 ms008+88+8
Scenario: Editing Endpoint Schema To Unique Value4 ms007+77+7
Scenario: Editing Endpoint Secure Field To Non-unique Value4 ms009+99+9
Scenario: Editing Endpoint Secure Field To Unique Value3 ms007+77+7
Scenario: Editing Endpoint To NULL Values3 ms0014+1414+14
Scenario: Editing Endpoint To Non-unique Endpoint3 ms0010+1010+10
Scenario: Editing Group's Name To Contain Numbers Without Changing Description6 ms007+77+7
Scenario: Editing Tag's Name To Contain Numbers Without Description3 ms007+77+7
Scenario: Empty query results are supported4 ms008+38+3
Scenario: Event factory sanity checks15 ms002-42-4
Scenario: Event service domain check4 ms002-42-4
Scenario: Every account must have the default configuration items5 ms0033
Scenario: Execute possible docker steps to show its usage1 ms2+231+31033+33
Scenario: Executing Job And Then Restarting Device9 ms0045+4545+45
Scenario: Executing Job When Device Connected After End Date And Time9 ms0039+3939+39
Scenario: Executing Job When Device Connected After The Specified Start Date And Time10 ms0038+3838+38
Scenario: Executing Job When Device Connected Before End Date And Time8 ms0039+3939+39
Scenario: Executing Job When Device Connected Before The Specified Start Date And Time11 ms0037+3737+37
Scenario: Executing Job Without Steps10 ms0040+4040+40
Scenario: Extra long continuous test with multiple subscenarios with LOOSE default connection mode9 ms0-20-404419+407419+1
Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode10 ms0-20-382397+385397+1
Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode and no previously defined devices5 ms0-20-293305+296305+1
Scenario: Find a connection by its IDs4 ms006+16+1
Scenario: Find a connection by its client ID10 ms006+16+1
Scenario: Find a group entry in the database6 ms009+29+2
Scenario: Find a non existing event6 ms006-46-4
Scenario: Find account by Id4 ms0044
Scenario: Find account by Ids4 ms0044
Scenario: Find account by name4 ms0044
Scenario: Find account by random Id3 ms0033
Scenario: Find all child accounts7 ms0033
Scenario: Find an access info entity12 ms0011+311+3
Scenario: Find an access info entity by user ID10 ms0010+310+3
Scenario: Find an event by its ID6 ms006-46-4
Scenario: Find an existing access role entity7 ms0013+413+4
Scenario: Find by name nonexisting account19 ms0033
Scenario: Find correct number of messages by corresponding metric0.22 sec0058+5858+58
Scenario: Find device by client ID5 ms0033
Scenario: Find device by registry ID3 ms0044
Scenario: Find last created permission10 ms0012+1212+12
Scenario: Find multiple users2 ms0055
Scenario: Find role by ID4 ms007+37+3
Scenario: Find self account by id5 ms0011+1111+11
Scenario: Find self account by id and scope id5 ms0011+1111+11
Scenario: Find self account by name4 ms0011+1111+11
Scenario: Find the last created domain entry13 ms005+15+1
Scenario: Find user by id3 ms0055
Scenario: Find user by its email3 ms006+66+6
Scenario: Find user by its phone number4 ms006+66+6
Scenario: Find user by name3 ms0055
Scenario: Find user by name that doesn't exist3 ms0033
Scenario: Find user with id and scope id that doesn't exist3 ms0033
Scenario: Finding all messages by selecting all metrics0.2 sec0040+4040+40
Scenario: Finding correct number of messages by corresponding two metrics0.22 sec0052+5252+52
Scenario: Finding messages with incorrect metric parameters0.21 sec0072+7272+72
Scenario: Finding user by expiration date in the future16 ms005+55+5
Scenario: Finding user by expiration date in the past3 ms006+66+6
Scenario: Finding user by expiration date in the present3 ms006+66+6
Scenario: Generic connection query4 ms008+18+1
Scenario: Get metadata4 ms0033
Scenario: Group with a null name5 ms007+27+2
Scenario: Handle account creation13 ms0033
Scenario: Handle duplicate account names10 ms0055
Scenario: Handle null account name93 ms0044
Scenario: Handling of 2 birth messages11 ms001212
Scenario: Handling of a disconnect message from a non existing device4 ms001010
Scenario: Have Two Devices in The Same Group Without Description4 ms0013+1313+13
Scenario: I try to find a non-existing connection6 ms006+16+1
Scenario: If user credential expiration date is before today, user can not login3 ms001414
Scenario: If user credential expiration date is today, user can not login it is day inclusive3 ms001414
Scenario: If user credential expiration date is tomorrow, user can login3 ms001313
Scenario: If user credential is in state disabled, user can not login2 ms001414
Scenario: If user credential is in state enabled, user can login3 ms001313
Scenario: If user expiration date is before today, user can not login3 ms001313
Scenario: If user expiration date is today, user can not login because expiration date was reached4 ms001313
Scenario: If user expiration date is tomorrow, user can login3 ms001212
Scenario: Init Security Context for all scenarios1.3 sec1+11+146+4648+48
Scenario: Installing a package14 ms0-20-713+913
Scenario: Interval Job" Schedule With Too Long Name5 ms0011+1111+11
Scenario: It must be possible to query for specific entries in the role database4 ms008+38+3
Scenario: It should not be possible to change the configuration items4 ms005+55+5
Scenario: Job execution factory sanity checks1 ms0022
Scenario: Job factory sanity checks2 ms0033
Scenario: Job with a duplicate name4 ms009+39+3
Scenario: Job with a null name4 ms008+38+3
Scenario: Job with a null scope ID3 ms009+39+3
Scenario: Job with an empty name3 ms008+28+2
Scenario: List Endpoints Created From Sub-Account3 ms2+223+231+126+26
Scenario: List Endpoints From "kapua-sys" Account2 ms2+24+45+511+11
Scenario: List Endpoints From Sub-Account Of Another Sub-Account3 ms2+223+231+126+26
Scenario: List Endpoints From Sub-account3 ms2+212+121+115+15
Scenario: MetricsInfo client ID and topic data based on the client id8 ms0034+1734+17
Scenario: MetricsInfo last published date9 ms0048+2448+24
Scenario: Modify a role that was deleted4 ms009+39+3
Scenario: Modify an existing account3 ms0044
Scenario: Modify last child expiration so that it still expires before parent5 ms001414
Scenario: Modify middle child expiration so that it still expires before parent5 ms001414
Scenario: Modify middle child expiration to outlive parent5 ms001515
Scenario: Modify nonexisting account14 ms0066
Scenario: Modify parent expiration so that it still expires after child4 ms001414
Scenario: Modify parent expiration to before child expiration5 ms001515
Scenario: Modifying Sub-account of a different parent account8 ms0025+2525+25
Scenario: Moving Device From One Group With Description to Another5 ms0014+1414+14
Scenario: Nameless role entry5 ms007+37+3
Scenario: Negative scenario when client connects twice with same client id10 ms001111
Scenario: New connection with reserved ID5 ms0-20-1934+2234+1
Scenario: Permission factory sanity checks5 ms0033
Scenario: Positive scenario without stealing link13 ms001212
Scenario: Query based on message ordering10 ms0020+1020+10
Scenario: Query based on metrics ordering8 ms0020+1020+10
Scenario: Query before schema search4 ms0082+4182+41
Scenario: Query for a specific group by name11 ms0016+216+2
Scenario: Query for all the access info entities of a specific user9 ms0018+318+3
Scenario: Query for all the access info entities of an invalid user7 ms0010+310+3
Scenario: Query for executions of a specific job3 ms0018+218+2
Scenario: Query for jobs with specified name5 ms009+39+3
Scenario: Query for step definitions3 ms0077
Scenario: Query user3 ms0066
Scenario: Querying Other Items With All Account Permissions9 ms0039+3939+39
Scenario: Regular connection3 ms007+17+1
Scenario: Regular creation of Access Role entity23 ms0014+414+4
Scenario: Regular domain8 ms005+15+1
Scenario: Regular group in random scope5 ms007+27+2
Scenario: Regular group in root scope8 ms007+27+2
Scenario: Regular job creation3 ms0010+310+3
Scenario: Regular job execution creation2 ms007+27+2
Scenario: Regular role creation5 ms009+39+3
Scenario: Regular step creation2 ms0011+311+3
Scenario: Regular step definition creation5 ms0077
Scenario: Regular step definition with a property list4 ms0044
Scenario: Reset Security Context for all scenarios0.99 sec1+11+146+4648+48
Scenario: Restarting a job with Asset Write and Bundle Start steps10 ms0028+2828+28
Scenario: Restarting a job with Command Execution and Bundle Start steps10 ms0028+2828+28
Scenario: Restarting a job with Configuration Put and Bundle Start steps10 ms0028+2828+28
Scenario: Restarting a job with Package Uninstall and Bundle Start steps10 ms0028+2828+28
Scenario: Restarting a job with invalid Configuration Put and multiple devices two times12 ms0033+3333+33
Scenario: Restarting a job with invalid Configuration Put step two times16 ms0036+3636+36
Scenario: Restarting a job with invalid Package Install step and multiple devices two times10 ms0031+3131+31
Scenario: Restarting a job with invalid Package Install step two times19 ms0034+3434+34
Scenario: Restarting a job with invalid Package Uninstall step and multiple devices two times61 ms0032+3232+32
Scenario: Restarting a job with invalid Package Uninstall step two times18 ms0034+3434+34
Scenario: Restarting a job with valid Configuration Put step and multiple devices two times22 ms0033+3333+33
Scenario: Restarting a job with valid Configuration Put step two times15 ms0036+3636+36
Scenario: Restarting a job with valid Package Install step and multiple devices two times9 ms2+24+423+2329+29
Scenario: Restarting a job with valid Package Install step two times13 ms0034+3434+34
Scenario: Restarting a job with valid Package Uninstall step and multiple devices two times9 ms0030+3030+30
Scenario: Restarting a job with valid Package Uninstall step two times9 ms0032+3232+32
Scenario: Restarting job With invalid Asset Write and multiple two times18 ms0034+3434+34
Scenario: Restarting job With valid Asset Write step two times10 ms0036+3636+36
Scenario: Restarting job with Asset Write and Bundle Start steps and multiple devices10 ms0031+3131+31
Scenario: Restarting job with Asset Write step13 ms0025+2525+25
Scenario: Restarting job with Asset Write step and multiple devices11 ms0028+2828+28
Scenario: Restarting job with Bundle Start step10 ms0025+2525+25
Scenario: Restarting job with Bundle Start step and multiple devices10 ms0027+2727+27
Scenario: Restarting job with Bundle Stop and Bundle Start step and multiple devices9 ms0031+3131+31
Scenario: Restarting job with Bundle Stop and Bundle Start steps10 ms0029+2929+29
Scenario: Restarting job with Bundle Stop step16 ms0025+2525+25
Scenario: Restarting job with Bundle Stop step and multiple devices9 ms0027+2727+27
Scenario: Restarting job with Command Execution and Bundle Start steps and multiple devices8 ms0031+3131+31
Scenario: Restarting job with Command Execution step16 ms0025+2525+25
Scenario: Restarting job with Command Execution step and multiple devices12 ms0027+2727+27
Scenario: Restarting job with Configuration Put and Bundle Start steps and multiple devices9 ms0031+3131+31
Scenario: Restarting job with Configuration Put step10 ms0025+2525+25
Scenario: Restarting job with Configuration Put step and multiple devices10 ms0027+2727+27
Scenario: Restarting job with Package Download/Install and Bundle Start steps and multiple devices21 ms0059+5959+59
Scenario: Restarting job with Package Download/Install step and multiple devices12 ms0027+2727+27
Scenario: Restarting job with Package Install step10 ms0025+2525+25
Scenario: Restarting job with Package Uninstall and Bundle start steps and multiple device9 ms0031+3131+31
Scenario: Restarting job with Package Uninstall step11 ms0025+2525+25
Scenario: Restarting job with Package Uninstall step and multiple device11 ms0027+2727+27
Scenario: Restarting job with invalid Asset Write step two times13 ms0036+3636+36
Scenario: Restarting job with invalid Bundle Start and Bundle Stop steps and multiple devices two times50 ms0041+4141+41
Scenario: Restarting job with invalid Bundle Start and Bundle Stop steps two times19 ms0043+4343+43
Scenario: Restarting job with invalid Bundle Start step and multiple devices two times13 ms0035+3535+35
Scenario: Restarting job with invalid Bundle Start step two times17 ms0037+3737+37
Scenario: Restarting job with invalid Bundle Stop step and multiple devices two times31 ms0035+3535+35
Scenario: Restarting job with invalid Bundle Stop step two times17 ms0037+3737+37
Scenario: Restarting job with invalid Command Execution and Package Install step two times26 ms0036+3636+36
Scenario: Restarting job with invalid Command Execution and Package Install steps and multiple devices two times12 ms0037+3737+37
Scenario: Restarting job with invalid Command Execution step and multiple devices two times17 ms0031+3131+31
Scenario: Restarting job with invalid Command Execution step two times13 ms0032+3232+32
Scenario: Restarting job with invalid Configuration Put And Command Execution steps two times17 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 times26 ms0038+3838+38
Scenario: Restarting job with invalid Package Uninstall and Asset Write steps two times12 ms0040+4040+40
Scenario: Restarting job with two Bundle Start steps12 ms0029+2929+29
Scenario: Restarting job with two Bundle Start steps and multiple devices12 ms0031+3131+31
Scenario: Restarting job with valid Asset Write step and multiple devices two times23 ms0034+3434+34
Scenario: Restarting job with valid Bundle Start And Bundle Stop steps two times19 ms0043+4343+43
Scenario: Restarting job with valid Bundle Start and Bundle Stop steps and multiple devices two times13 ms0041+4141+41
Scenario: Restarting job with valid Bundle Start step and multiple devices two times0.1 sec0035+3535+35
Scenario: Restarting job with valid Bundle Start step two times10 ms0037+3737+37
Scenario: Restarting job with valid Bundle Stop step and multiple devices two times32 ms0035+3535+35
Scenario: Restarting job with valid Bundle Stop step two times15 ms0037+3737+37
Scenario: Restarting job with valid Command Execution and Package Install steps and multiple devices two times11 ms0033+3333+33
Scenario: Restarting job with valid Command Execution and Package Install steps two times21 ms0034+3434+34
Scenario: Restarting job with valid Command Execution step and multiple devices two times27 ms0031+3131+31
Scenario: Restarting job with valid Command Execution step two times18 ms0032+3232+32
Scenario: Restarting job with valid Configuration Put and Command Execution steps and multiple devices two times25 ms0037+3737+37
Scenario: Restarting job with valid Configuration Put and Command Execution steps two times11 ms0038+3838+38
Scenario: Restarting job with valid Package Uninstall and Asset Write steps and multiple devices two times60 ms0036+3636+36
Scenario: Restarting job with valid Package Uninstall and Asset Write steps two times17 ms2+27+729+2938+38
Scenario: Role creator sanity checks3 ms0022
Scenario: Role entry with no actions6 ms006+26+2
Scenario: Role object equality check4 ms0022
Scenario: Role service related objects sanity checks4 ms0044
Scenario: Search By Client ID And Get Multiple Matches13 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 Name4 ms0012+1212+12
Scenario: Search By Client ID and Serial Number3 ms0012+1212+12
Scenario: Search By Client ID and Status5 ms0012+1212+12
Scenario: Search By Client ID, Display Name and Serial Number5 ms0012+1212+12
Scenario: Search By Client ID, Display Name and Status4 ms0012+1212+12
Scenario: Search By Client ID, Display Name, Serial Number and Status4 ms0012+1212+12
Scenario: Search By Device Status And Get No Matches4 ms008+88+8
Scenario: Search By Device's Display Name And Get One Match4 ms008+88+8
Scenario: Search By Display Name and Serial Number6 ms0012+1212+12
Scenario: Search By Display Name and Status5 ms0012+1212+12
Scenario: Search By Full Client ID And Get One Match4 ms0010+1010+10
Scenario: Search By Non-existing Client ID And Get No Matches3 ms008+88+8
Scenario: Search By One Letter Of Display Name5 ms008+88+8
Scenario: Search By One Letter Of Serial Number4 ms0012+1212+12
Scenario: Search By Serial Number And Get Multiple Matches5 ms0014+1414+14
Scenario: Search By Serial Number And Get No Matches5 ms0010+1010+10
Scenario: Search By Serial Number And Get One Match4 ms0011+1111+11
Scenario: Search By Serial Number and Status4 ms0012+1212+12
Scenario: Search By Serial Number, Display Name and Status5 ms0012+1212+12
Scenario: Search By Specific Serial Number4 ms0010+1010+10
Scenario: Search By Status And Get Multiple Matches5 ms0010+1010+10
Scenario: Search by Device Status And Get One Match4 ms0010+1010+10
Scenario: Search for a non existent client ID2 ms006+16+1
Scenario: Search for an access info entity by an incorrect user ID12 ms0011+311+3
Scenario: Search the role database for a random ID5 ms007+37+3
Scenario: Send BIRTH message and then DC message16 ms0-20-715+915
Scenario: Send BIRTH message and then DC message while broker ip is NOT set10 ms0066
Scenario: Send BIRTH message and then DC message while broker ip is set by System21 ms0-20-28+48
Scenario: Send BIRTH message and then DC message while broker ip is set by config file26 ms0-20-28+48
Scenario: Set a correct minimum for password length6 ms003+33+3
Scenario: Set an incorrect minimum for password length6 ms006+66+6
Scenario: Set environment variables81 ms0061+1861+18
Scenario: Setting InfiniteChildAccounts To False And Increasing MaxNumberChildAccounts When Sub-accounts Are Already Created5 ms0014+1414+14
Scenario: Setting InfiniteChildAccounts To False When Sub-accounts Are Already Created5 ms0015+1515+15
Scenario: Setting InfiniteChildAccounts To True And Decreasing MaxNumberChildAccounts When Sub-accounts Are Already Created5 ms0014+1414+14
Scenario: Setting Lockout Duration To 0 Seconds6 ms0015+1515+15
Scenario: Setting Lockout Duration To Negative Value7 ms007+77+7
Scenario: Setting Max Failures To 06 ms0015+1515+15
Scenario: Setting Max Failures To 15 ms0015+1515+15
Scenario: Setting Max Failures To 1006 ms0015+1515+15
Scenario: Setting Max Failures To Negative Value5 ms007+77+7
Scenario: Setting Reset After Login Counter To 0 Seconds4 ms0017+1717+17
Scenario: Setting Reset After Login Counter To Negative Value5 ms007+77+7
Scenario: Setting configuration without mandatory items must raise an error2 ms0055
Scenario: Simple Jetty with rest-api war3 ms2+23+31+16+6
Scenario: Simple create14 ms0011+411+4
Scenario: Simple positive scenario for creating daily index5 ms001414
Scenario: Simple positive scenario for creating default - weekly index6 ms001212
Scenario: Simple positive scenario for creating hourly index5 ms001414
Scenario: Start Jetty server for all scenarios2 ms2+2002+2
Scenario: Start broker for all scenarios0.16 sec0-30044+4244+12
Scenario: Start datastore for all scenarios0.16 sec2+2028-230
Scenario: Start event broker for all scenarios1 sec1+11+150+1452+16
Scenario: Starting a job with Asset Write and Bundle Start steps11 ms0036+3636+36
Scenario: Starting a job with Asset Write step9 ms0025+2525+25
Scenario: Starting a job with Bundle Start step9 ms0034+3434+34
Scenario: Starting a job with Bundle Stop and Bundle Start steps10 ms0039+3939+39
Scenario: Starting a job with Bundle Stop step8 ms0035+3535+35
Scenario: Starting a job with Command Execution and Bundle Start steps9 ms0037+3737+37
Scenario: Starting a job with Command Execution step10 ms0025+2525+25
Scenario: Starting a job with Configuration Put and Bundle Start steps10 ms0037+3737+37
Scenario: Starting a job with Configuration Put step11 ms0025+2525+25
Scenario: Starting a job with Package Install and Bundle Start steps11 ms0039+3939+39
Scenario: Starting a job with Package Install step10 ms0032+3232+32
Scenario: Starting a job with Package Uninstall and Bundle Start steps10 ms0036+3636+36
Scenario: Starting a job with Package Uninstall step12 ms0033+3333+33
Scenario: Starting a job with invalid Asset Write step11 ms0031+3131+31
Scenario: Starting a job with invalid Asset Write step and multiple targets14 ms0029+2929+29
Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps18 ms0036+3636+36
Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps and multiple devices88 ms0035+3535+35
Scenario: Starting a job with invalid Bundle Start step13 ms0031+3131+31
Scenario: Starting a job with invalid Bundle Stop step12 ms0031+3131+31
Scenario: Starting a job with invalid Bundle Stop step and multiple devices20 ms0029+2929+29
Scenario: Starting a job with invalid Command Execution step15 ms0027+2727+27
Scenario: Starting a job with invalid Configuration Put step11 ms0030+3030+30
Scenario: Starting a job with invalid Configuration Put step and multiple devices15 ms0028+2828+28
Scenario: Starting a job with invalid Package Install step11 ms0029+2929+29
Scenario: Starting a job with invalid Package Install step and multiple devices49 ms0026+2626+26
Scenario: Starting a job with invalid Package Uninstall and Asset Write steps10 ms0034+3434+34
Scenario: Starting a job with invalid Package Uninstall and Asset Write steps and multiple devices36 ms0032+3232+32
Scenario: Starting a job with invalid Package Uninstall step9 ms0029+2929+29
Scenario: Starting a job with invalid Package Uninstall step and multiple targets13 ms0026+2626+26
Scenario: Starting a job with two Bundle Start steps8 ms0039+3939+39
Scenario: Starting a job with valid Asset Write step15 ms0031+3131+31
Scenario: Starting a job with valid Asset Write step and multiple targets18 ms0029+2929+29
Scenario: Starting a job with valid Bundle Start and Bundle Stop steps10 ms0036+3636+36
Scenario: Starting a job with valid Bundle Start and Bundle Stop steps and multiple devices11 ms0034+3434+34
Scenario: Starting a job with valid Bundle Start step13 ms0031+3131+31
Scenario: Starting a job with valid Bundle Stop step10 ms0031+3131+31
Scenario: Starting a job with valid Bundle Stop step and multiple devices3 ms2+220+207+729+29
Scenario: Starting a job with valid Command Execution step10 ms0027+2727+27
Scenario: Starting a job with valid Configuration Put step13 ms0031+3131+31
Scenario: Starting a job with valid Configuration Put step and multiple devices13 ms0026+2626+26
Scenario: Starting a job with valid Package Install step16 ms0029+2929+29
Scenario: Starting a job with valid Package Install step and multiple devices21 ms0026+2626+26
Scenario: Starting a job with valid Package Uninstall and Asset Write steps12 ms0033+3333+33
Scenario: Starting a job with valid Package Uninstall and Asset Write steps and multiple devices26 ms0032+3232+32
Scenario: Starting a job with valid Package Uninstall step16 ms0030+3030+30
Scenario: Starting a job with valid Package Uninstall step and multiple targets71 ms0026+2626+26
Scenario: Starting and stopping the simulator should create a device entry and properly set its status3 ms0-20-1420+1620
Scenario: Starting job with Asset Write and Bundle Start steps and multiple devices15 ms0032+3232+32
Scenario: Starting job with Asset Write step and multiple devices12 ms0028+2828+28
Scenario: Starting job with Bundle Start step and multiple devices12 ms0028+2828+28
Scenario: Starting job with Bundle Stop and Bundle Start step and multiple devices9 ms0032+3232+32
Scenario: Starting job with Bundle Stop step and multiple devices10 ms0028+2828+28
Scenario: Starting job with Command Execution and Bundle Start steps and multiple devices9 ms0032+3232+32
Scenario: Starting job with Command Execution step and multiple devices11 ms0028+2828+28
Scenario: Starting job with Configuration Put and Bundle Start steps and multiple devices8 ms0032+3232+32
Scenario: Starting job with Configuration Put step and multiple devices8 ms0028+2828+28
Scenario: Starting job with Package Download/Install and Bundle Start steps and multiple devices11 ms0038+3838+38
Scenario: Starting job with Package Download/Install step and multiple devices64 ms0034+3434+34
Scenario: Starting job with Package Uninstall and Bundle start steps and multiple device11 ms0032+3232+32
Scenario: Starting job with Package Uninstall step and multiple device8 ms0027+2727+27
Scenario: Starting job with invalid Bundle Start step and multiple devices59 ms0029+2929+29
Scenario: Starting job with invalid Command Execution and Package Install steps16 ms0031+3131+31
Scenario: Starting job with invalid Command Execution step and multiple devices29 ms0028+2828+28
Scenario: Starting job with invalid Command Execution, invalid Package Install steps and multiple devices16 ms0029+2929+29
Scenario: Starting job with invalid Configuration Put and Command Execution steps10 ms0032+3232+32
Scenario: Starting job with invalid Configuration Put and Command Execution steps and multiple devices12 ms0031+3131+31
Scenario: Starting job with two Bundle Start steps and multiple devices9 ms0032+3232+32
Scenario: Starting job with valid Bundle Start step and multiple devices14 ms0029+2929+29
Scenario: Starting job with valid Command Execution and Package Install steps10 ms0031+3131+31
Scenario: Starting job with valid Command Execution step and multiple devices22 ms0026+2626+26
Scenario: Starting job with valid Command Execution, valid Package Install steps and multiple devices63 ms0029+2929+29
Scenario: Starting job with valid Configuration Put and Command Execution steps12 ms0032+3232+32
Scenario: Starting job with valid Configuration Put and Command Execution steps and multiple devices44 ms0030+3030+30
Scenario: Stealing link scenario5 ms0-20-1428+1628
Scenario: Step definition factory sanity checks4 ms0022
Scenario: Step definition with a duplicate name4 ms0066
Scenario: Step definition with a null name9 ms0066
Scenario: Step definition with a null scope ID4 ms0066
Scenario: Step definition with an empty name7 ms0055
Scenario: Step factory sanity checks2 ms0022
Scenario: Step with a null scope ID3 ms0011+311+3
Scenario: Stop Jetty server for all scenarios2 ms002+22+2
Scenario: Stop broker after all scenarios0.1 sec0046+1446+14
Scenario: Stop datastore after all scenarios0.11 sec003030
Scenario: Stop event broker for all scenarios1 sec1+11+150+1452+16
Scenario: Stop job with multiple Asset Write and Package Install steps and one target12 ms0037+3737+37
Scenario: Stop job with multiple Bundle Start and Package Install steps and one target17 ms0037+3737+37
Scenario: Stop job with multiple Bundle Stop and Package Uninstall steps and one target14 ms0037+3737+37
Scenario: Stop job with multiple Command Execution and Package Install steps and one target18 ms0034+3434+34
Scenario: Stop job with multiple Configuration Put and Package Uninstall steps and one target14 ms0035+3535+35
Scenario: Stop job with multiple targets and Asset Write and Package Install steps and one target24 ms0037+3737+37
Scenario: Stop job with multiple targets and Bundle Start and Package Install steps1 ms2+29+925+2536+36
Scenario: Stop job with multiple targets and Bundle Stop and Package Uninstall steps2 ms2+29+926+2637+37
Scenario: Stop job with multiple targets and Command Execution and Package Install steps14 ms0034+3434+34
Scenario: Stop job with multiple targets and Configuration Put and Package Uninstall steps2 ms2+228+287+737+37
Scenario: Test LOOSE user coupling on single connection3 ms0-20-1328+1628+1
Scenario: Test LOOSE user coupling with 3 connections4 ms0-20-2338+2638+1
Scenario: Test STRICT user coupling on single connection8 ms0-20-1025+1325+1
Scenario: Test STRICT user coupling with 3 connections and a reserved user7 ms0-20-4863+5163+1
Scenario: Test STRICT user coupling with user change allowed on single connection4 ms0-20-2136+2436+1
Scenario: Test account query3 ms0044
Scenario: Test the message store with server timestamp indexing8 ms0026+1326+13
Scenario: Test the message store with timestamp indexing11 ms0026+1326+13
Scenario: The Client ID is case sensitive2 ms008+18+1
Scenario: To be defined4 ms00-1513+1213-3
Scenario: Translating "CommandRequestMessage" to "KuraRequestMessage"29 ms004+44+4
Scenario: Translating CommandRequestMessage to null7 ms004+44+4
Scenario: Translating empty message to empty message5 ms004+44+4
Scenario: Translating from "AssetRequestMessage" to "AssetResponseMessage"4 ms004+44+4
Scenario: Translating invalid jms data message with valid channel, body and metrics into kura data message3 ms005+55+5
Scenario: Translating invalid kura data message with valid channel, body and metrics into jms message3 ms005+55+5
Scenario: Translating invalid kura data message with valid channel, body and metrics into mqtt message5 ms005+55+5
Scenario: Translating kura data message with null channel, and payload without body and with metrics2 ms005+55+5
Scenario: Translating kura data message with valid channel and with null payload4 ms005+55+5
Scenario: Translating kura data message with valid channel and without body and metrics into jms message2 ms005+55+5
Scenario: Translating kura data message with valid channel, and with null payload3 ms005+55+5
Scenario: Translating kura data message with valid channel, body and metrics into jms message2 ms005+55+5
Scenario: Translating kura data message with valid channel, metrics and without body into jms message4 ms005+55+5
Scenario: Translating kura data message with valid channel, metrics and without body into mqtt message5 ms005+55+5
Scenario: Translating null to KuraRequestMessage5 ms004+44+4
Scenario: Translating of jms message with empty payload and invalid topic that contain only userName into kura data message2 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 message3 ms006+66+6
Scenario: Translating of mqtt message with invalid payload and invalid topic into kura data message2 ms005+55+5
Scenario: Translating of mqtt message with invalid payload and with null topic into kura data message5 ms005+55+5
Scenario: Translation of kura data message with valid channel and without body and metrics into mqtt message5 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 message4 ms005+55+5
Scenario: Translation of mqtt message with invalid payload and valid topic into kura data message6 ms006+66+6
Scenario: Translation of mqtt message with invalid payload and valid topic into kura response message3 ms006+66+6
Scenario: Translation of mqtt message with valid payload and invalid topic into kura response message3 ms005+55+5
Scenario: Translation of mqtt message with valid payload and valid topic into kura data message6 ms006+66+6
Scenario: Translation of mqtt message with valid payload and valid topic into kura response message4 ms006+66+6
Scenario: Try to add two different roles with same permissions11 ms0021+2121+21
Scenario: Try to change an existing connection ID3 ms007+17+1
Scenario: Try to create an access into entity with an invalid role id35 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 ID4 ms0033
Scenario: Try to find a device with an invalid registry ID3 ms0033
Scenario: Try to find users granted to "admin" role14 ms0012+1212+12
Scenario: Try to find users that have assigned specific role12 ms0012+1212+12
Scenario: Try to modify the connection client ID5 ms007+17+1
Scenario: Try to update the device client ID3 ms0044
Scenario: Uncorrect Login While Lockout Policy Is Disabled5 ms0017+1717+17
Scenario: Uncorrect Login While Lockout Policy Is Enabled6 ms0017+1717+17
Scenario: Update a group entry in the database5 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 description2 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 definition3 ms0077
Scenario: Update a step definition name4 ms0077
Scenario: Update a step definition processor name4 ms0088
Scenario: Update a step definition target type4 ms0088
Scenario: Update existing role name5 ms008+38+3
Scenario: Update job id of an existing execution item2 ms008+28+2
Scenario: Update schedule which doesn't exist5 ms005+55+5
Scenario: Update scheduler end date3 ms2+21+16+69+9
Scenario: Update scheduler name5 ms008+88+8
Scenario: Update scheduler start date5 ms008+88+8
Scenario: Update the end time of an existing execution item8 ms009+29+2
Scenario: Update trigger definition3 ms2+21+15+58+8
Scenario: Update user6 ms0077
Scenario: Update user that doesn't exist3 ms0055
Scenario: User locking itself out by using out login attempts3 ms001616
Scenario: User locking itself out with failed attempts and not waiting to unlock4 ms001717
Scenario: User locking itself out with failed attempts and waiting to unlock3 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 attempts4 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 ID3 ms005+15+1
Scenario: Validate a device client search with null scope3 ms005+15+1
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 ID4 ms004-14-1
Scenario: Validate a device search with a null device ID4 ms006+26+2
Scenario: Validate a device search with a null scope ID2 ms006+26+2
Scenario: Validate a null creator3 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 search2 ms004+14+1
Scenario: Validate a regular device count3 ms0044
Scenario: Validate a regular device query3 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 ID3 ms006+26+2
Scenario: Waiting For Lock Duration Time To Pass5 ms0019+1919+19
Scenario: Waiting For Reset After Login Counter To Pass5 ms0018+1818+18
empty) scope0 ms004-44-4