Test Result : (root)

57 failures (+16) , 398 skipped (+190)
16,563 tests (±0)
Took 22 sec.

All Failed Tests

Test NameDurationAge
 Scenario: Add datastore permissions to the role.And I search for data message with id "fake-id"1 ms20
 Scenario: Add datastore permissions to the role.Scenario: Add datastore permissions to the role2 ms20
 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 id2 ms22
 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 ms22
 Scenario: Create same user in different accounts.Scenario: Create same user in different accounts1.1 sec20
 Scenario: Create scheduler with correct end date.Scenario: Create scheduler with correct end date0 ms18
 Scenario: Create scheduler with correct end date.Then I create a new trigger from the existing creator with previously defined date properties0 ms18
 Scenario: Create scheduler with end date before start date.Scenario: Create scheduler with end date before start date6 ms18
 Scenario: Create scheduler with end date before start date.Then I create a new trigger from the existing creator with previously defined date properties6 ms18
 Scenario: Creating unique Access Group with special symbols in description.Scenario: Creating unique Access Group with special symbols in description4 ms40
 Scenario: Creating unique Access Group with special symbols in description.Then I find the group with name "groupName53"4 ms40
 Scenario: Deleting user in account that is higher in hierarchy.Scenario: Deleting user in account that is higher in hierarchy0.96 sec20
 Scenario: Deleting user in account that is lower in hierarchy.Scenario: Deleting user in account that is lower in hierarchy0.91 sec20
 Scenario: Execute possible docker steps to show its usage.Given List images by name "kapua/kapua-broker:1.5.0-SNAPSHOT"1 ms27
 Scenario: Execute possible docker steps to show its usage.Scenario: Execute possible docker steps to show its usage2 ms27
 Scenario: Init Security Context for all scenarios.Scenario: Init Security Context for all scenarios1 sec20
 Scenario: List Endpoints Created From Sub-Account.And I create endpoint with schema "Schema1", domain "abc.com" and port 22221 ms20
 Scenario: List Endpoints Created From Sub-Account.Scenario: List Endpoints Created From Sub-Account1 ms20
 Scenario: List Endpoints From "kapua-sys" Account.Scenario: List Endpoints From "kapua-sys" Account1 ms20
 Scenario: List Endpoints From "kapua-sys" Account.Then I find 3 endpoints1 ms20
 Scenario: List Endpoints From Sub-Account Of Another Sub-Account.And I create endpoint with schema "Schema1", domain "abc.com" and port 22221 ms20
 Scenario: List Endpoints From Sub-Account Of Another Sub-Account.Scenario: List Endpoints From Sub-Account Of Another Sub-Account2 ms20
 Scenario: List Endpoints From Sub-account.And I create endpoint with schema "Schema1", domain "abc.com" and port 22222 ms20
 Scenario: List Endpoints From Sub-account.Scenario: List Endpoints From Sub-account3 ms20
 Scenario: Reset Security Context for all scenarios.Scenario: Reset Security Context for all scenarios0.95 sec20
 Scenario: Simple Jetty with rest-api war.Scenario: Simple Jetty with rest-api war1 ms22
 Scenario: Simple Jetty with rest-api war.When REST POST call at "/v1/authentication/user" with JSON "{"password": "kapua-password", "username": "kapua-sys"}"1 ms22
 Scenario: Start Jetty server for all scenarios.Given Start Jetty Server on host "127.0.0.1" at port "8081"1 ms22
 Scenario: Start Jetty server for all scenarios.Scenario: Start Jetty server for all scenarios1 ms22
 Scenario: Start datastore for all scenarios.Given Start Datastore1 ms20
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios1 ms20
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios1 sec20
 Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps.And Bundles are requested1 ms1
 Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps.Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps2 ms1
 Scenario: Starting a job with invalid Bundle Start step.And Bundles are requested1 ms1
 Scenario: Starting a job with invalid Bundle Start step.Scenario: Starting a job with invalid Bundle Start step1 ms1
 Scenario: Starting a job with invalid Bundle Stop step.And Bundles are requested1 ms1
 Scenario: Starting a job with invalid Bundle Stop step.Scenario: Starting a job with invalid Bundle Stop step2 ms1
 Scenario: Starting a job with invalid Command Execution step.Scenario: Starting a job with invalid Command Execution step2 ms1
 Scenario: Starting a job with invalid Command Execution step.When I search for events from device "rpione3" in account "kapua-sys"1 ms1
 Scenario: Starting a job with valid Bundle Start step.And Bundles are requested1 ms1
 Scenario: Starting a job with valid Bundle Start step.Scenario: Starting a job with valid Bundle Start step2 ms1
 Scenario: Starting a job with valid Bundle Stop step.And Bundles are requested1 ms1
 Scenario: Starting a job with valid Bundle Stop step.Scenario: Starting a job with valid Bundle Stop step2 ms1
 Scenario: Starting a job with valid Command Execution step.Scenario: Starting a job with valid Command Execution step7 ms1
 Scenario: Starting a job with valid Command Execution step.When I search for events from device "rpione3" in account "kapua-sys"7 ms1
 Scenario: Starting a job with valid Configuration Put step.Scenario: Starting a job with valid Configuration Put step1 ms1
 Scenario: Starting a job with valid Configuration Put step.When Configuration is requested1 ms1
 Scenario: Starting job with invalid Configuration Put and Command Execution steps.Scenario: Starting job with invalid Configuration Put and Command Execution steps1 ms1
 Scenario: Starting job with invalid Configuration Put and Command Execution steps.Then Configuration is requested0 ms1
 Scenario: Starting job with valid Configuration Put and Command Execution steps.And Configuration is requested0 ms1
 Scenario: Starting job with valid Configuration Put and Command Execution steps.Scenario: Starting job with valid Configuration Put and Command Execution steps1 ms1
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios1 sec20
 Scenario: Update scheduler end date.And I try to edit end date to 13-12-2020 at 10:001 ms18
 Scenario: Update scheduler end date.Scenario: Update scheduler end date1 ms18
 Scenario: Update trigger definition.And I try to edit trigger definition to "Cron Job"0 ms18
 Scenario: Update trigger definition.Scenario: Update trigger definition1 ms18

All Tests

ClassDurationFail(diff)Skip(diff)Pass(diff)Total(diff)
Scenario: A fresh database must contain 1 default role in the root scope5 ms0044
Scenario: A newly created account must have some metadata3 ms0033
Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic4 ms0088
Scenario: Access info service sanity checks5 ms0044
Scenario: Access service comparison sanity checks5 ms0033
Scenario: Account based ClientInfo data check12 ms002424
Scenario: Account exactly on its expiration date5 ms001414
Scenario: Account name must not be mutable3 ms0066
Scenario: Account past its expiration date6 ms001414
Scenario: Account wide metrics check9 ms002828
Scenario: Account with future expiration date6 ms001313
Scenario: Account with no expiration date6 ms001313
Scenario: Add Access Info domain permissions to new user8 ms002626
Scenario: Add Account permissions to the role in child account15 ms002828
Scenario: Add Credential domain permissions to new user8 ms001818
Scenario: Add Datastore domain permissions to new user0.14 sec001919
Scenario: Add Device Connection domain permissions to kapua-sys user11 ms001111
Scenario: Add Device Connection domain permissions to new user9 ms002323
Scenario: Add Device Event domain permissions to new user11 ms001616
Scenario: Add Device domain permissions to new user14 ms001717
Scenario: Add Domain domain permissions to kapua-sys user16 ms001717
Scenario: Add Domain domain permissions to new user9 ms003232
Scenario: Add Endpoint Permission To The User14 ms003030
Scenario: Add Endpoint_info permissions to the role in child account13 ms003030
Scenario: Add Group domain permissions to new user11 ms001717
Scenario: Add Group permissions to the role in child account15 ms002626
Scenario: Add Job domain permissions to new user11 ms001919
Scenario: Add Role domain permissions to new user14 ms001717
Scenario: Add Role permissions to the role in child account13 ms002626
Scenario: Add Scheduler Permissions With Job Permissions11 ms003131
Scenario: Add Scheduler Permissions Without Job Permissions9 ms002121
Scenario: Add Scheduler permissions to the role in child account12 ms003636
Scenario: Add Tag domain permissions to new user11 ms001515
Scenario: Add Tag permissions to the role in child account11 ms002626
Scenario: Add User domain permissions to new user10 ms002020
Scenario: Add account permissions to the role15 ms001919
Scenario: Add admin role to the user14 ms004444
Scenario: Add and delete Account permissions from the "admin" role17 ms001414
Scenario: Add and delete Device permissions from the "admin" role16 ms001414
Scenario: Add and delete Endpoint_info permissions from the "admin" role14 ms001414
Scenario: Add and delete Group permissions from the "admin" role21 ms001414
Scenario: Add and delete Job permissions from the "admin" role13 ms001414
Scenario: Add and delete Role permissions from the "admin" role15 ms001414
Scenario: Add and delete User permissions from the "admin" role11 ms001515
Scenario: Add datastore permissions to the role3 ms232227
Scenario: Add deleted role again11 ms001010
Scenario: Add device event permissions to the role13 ms003232
Scenario: Add device permissions to the role15 ms001919
Scenario: Add device permissions to the role in child account12 ms002626
Scenario: Add domain, user and access_info permissions to the role14 ms002323
Scenario: Add endpoint_info permissions to the role14 ms003131
Scenario: Add group permissions to the role13 ms001818
Scenario: Add job permissions to the role14 ms001919
Scenario: Add job permissions to the role in child account13 ms002626
Scenario: Add role permissions to the role14 ms001919
Scenario: Add same permission twice to the same role12 ms001414
Scenario: Add same role to user twice14 ms001313
Scenario: Add scheduler permissions to the role12 ms003131
Scenario: Add tag permissions to the role13 ms001818
Scenario: Add user permissions to the role14 ms001919
Scenario: Add user permissions to the role in child account17 ms002626
Scenario: Adding "Cron Job" Schedule With All Valid Parameters7 ms001010
Scenario: Adding "Cron Job" Schedule With All Valid Parameters And Null Cron Value4 ms001010
Scenario: Adding "Cron Job" Schedule With All Valid Parameters Except Cron Format6 ms001111
Scenario: Adding "Cron Job" Schedule With End Date Only4 ms001010
Scenario: Adding "Cron Job" Schedule With End Time before Start time4 ms001212
Scenario: Adding "Cron Job" Schedule With Non-Unique End Date Parameter5 ms001616
Scenario: Adding "Cron Job" Schedule With Non-Unique Start Date Parameter4 ms001515
Scenario: Adding "Cron Job" Schedule With Start Date Only5 ms001111
Scenario: Adding "Cron Job" Schedule With the same Start and End time5 ms001212
Scenario: Adding "Cron Job" Schedule Without The Start Date Parameter4 ms001010
Scenario: Adding "Device Connect" Schedule With All Valid Parameters5 ms0088
Scenario: Adding "Device Connect" Schedule With End Date Only4 ms001010
Scenario: Adding "Device Connect" Schedule With End Time before Start time5 ms001111
Scenario: Adding "Device Connect" Schedule With Max Length Name7 ms0088
Scenario: Adding "Device Connect" Schedule With Min Length Name5 ms0088
Scenario: Adding "Device Connect" Schedule With Name Only6 ms0099
Scenario: Adding "Device Connect" Schedule With Non-Unique End Date Parameter4 ms001313
Scenario: Adding "Device Connect" Schedule With Non-Unique Name5 ms001414
Scenario: Adding "Device Connect" Schedule With Non-Unique Start Date Parameter5 ms001111
Scenario: Adding "Device Connect" Schedule With Start Date Only5 ms001010
Scenario: Adding "Device Connect" Schedule With the same Start and End time4 ms001111
Scenario: Adding "Device Connect" Schedule Without Name10 ms001010
Scenario: Adding "Device Connect" Schedule Without The Start Date Parameter4 ms0099
Scenario: Adding "Empty" Tag To Device3 ms0055
Scenario: Adding "Interval Job" Schedule With All Valid Parameters6 ms001010
Scenario: Adding "Interval Job" Schedule With End Date Only7 ms001010
Scenario: Adding "Interval Job" Schedule With End Time before Start time4 ms001212
Scenario: Adding "Interval Job" Schedule With Max Length Name4 ms001010
Scenario: Adding "Interval Job" Schedule With Min Length Name5 ms001010
Scenario: Adding "Interval Job" Schedule With Name Only5 ms001010
Scenario: Adding "Interval Job" Schedule With Non-Unique End Date Parameter8 ms001616
Scenario: Adding "Interval Job" Schedule With Non-Unique Name5 ms001515
Scenario: Adding "Interval Job" Schedule With Non-Unique Start Date Parameter6 ms001515
Scenario: Adding "Interval Job" Schedule With Null Interval Number4 ms001212
Scenario: Adding "Interval Job" Schedule With Start Date Only6 ms001111
Scenario: Adding "Interval Job" Schedule With the same Start and End time7 ms001212
Scenario: Adding "Interval Job" Schedule Without Interval Number5 ms001111
Scenario: Adding "Interval Job" Schedule Without The Start Date Parameter5 ms0099
Scenario: Adding "Interval Job" Schedule Without a Name6 ms001111
Scenario: Adding "admin" role to a user in a child account14 ms001414
Scenario: Adding "admin" role to multiple users18 ms001818
Scenario: Adding "admin" role twice16 ms001313
Scenario: Adding Account:Delete permission to user in same scope14 ms002525
Scenario: Adding Account:Delete permission to user in sub-account scope15 ms003030
Scenario: Adding Account:Read and Account:Delete permissions to user in same scope12 ms002121
Scenario: Adding Account:Read and Account:Write permissions to user in same scope10 ms001919
Scenario: Adding Account:Read permission to user in same scope11 ms002323
Scenario: Adding Account:Read permission to user in sub-account scope11 ms002929
Scenario: Adding Account:Write and Account:Delete permission to user in same scope16 ms002323
Scenario: Adding Account:Write permission to user in same scope16 ms002525
Scenario: Adding Account:Write permission to user in sub-account scope9 ms003131
Scenario: Adding Multiple Permissions To User12 ms002020
Scenario: Adding One Permission To User14 ms001111
Scenario: Adding Permissions To Child User9 ms001818
Scenario: Adding Permissions To Parallel User11 ms001818
Scenario: Adding Previously Deleted Permission8 ms002828
Scenario: Adding Previously Deleted Tag From Device Again2 ms001111
Scenario: Adding Regular Device to a Group With Description4 ms001010
Scenario: Adding Regular Device to a Group Without a Description6 ms001212
Scenario: Adding Regular Group Without Description to Device7 ms001010
Scenario: Adding Regular Tag Without Description To Device3 ms0066
Scenario: Adding Same Regular Group Without Description to Device7 ms001414
Scenario: Adding Tag With Long Name Without Description To Device3 ms0066
Scenario: Adding Tag With Numbers Without Description To Device3 ms0066
Scenario: Adding Tag With Short Name Without Description To Device2 ms0066
Scenario: Adding Tag With Special Symbols Without Description To Device3 ms0066
Scenario: Adding all Account permissions to user in same scope10 ms001717
Scenario: Adding all Account permissions to user in sub-account scope9 ms002424
Scenario: Adding existing roles to user14 ms001515
Scenario: Adding role from child account to user in new child account11 ms001515
Scenario: Adding role to multiple users in child account12 ms001818
Scenario: Adding same role twice to user in child account12 ms001515
Scenario: Adding the same role to user twice in child account15 ms001313
Scenario: All device parameters must match the device creator3 ms0033
Scenario: Assign 100 Devices to One Group11 ms001111
Scenario: B1 Broker publish to CTRL_ACC_REPLY4 ms0099
Scenario: B10 Broker create sub-topic on ACL_DATA_ACC is not allowed5 ms0099
Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed3 ms0088
Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI2 ms0099
Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed2 ms0099
Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed3 ms0088
Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY3 ms0099
Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY4 ms0099
Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account4 ms0099
Scenario: B5 Broker publish to CTRL_ACC is not allowed6 ms0099
Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed3 ms0099
Scenario: B7 Broker subscribe on CTRL_ACC is not allowed3 ms0088
Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI3 ms0099
Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed5 ms0099
Scenario: Basic Device Event queries5 ms001010
Scenario: Birth and applications event handling6 ms001212
Scenario: Birth and death message handling5 ms001212
Scenario: Birth and missing event handling5 ms001212
Scenario: Birth message handling from a new device6 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 date4 ms001111
Scenario: Bug when user can retrieve user in another account if it has other account's user id3 ms2121933
Scenario: Captured date based ClientInfo data check8 ms003030
Scenario: Case sensitiveness of named device searches3 ms0044
Scenario: Change an existing step name3 ms001111
Scenario: Change role name so it is too short2 ms0066
Scenario: Change the account parent path4 ms0055
Scenario: Changing Client ID5 ms0099
Scenario: Changing Description On Group With Long Description5 ms0077
Scenario: Changing Description On Group With Long Name4 ms0077
Scenario: Changing Description On Group With Numbers In Name5 ms001010
Scenario: Changing Description On Group With Permitted Symbols5 ms0077
Scenario: Changing Description On Group With Short Description6 ms0077
Scenario: Changing Description On Group With Short Name5 ms0077
Scenario: Changing Description On Tag With Long Description3 ms0044
Scenario: Changing Description On Tag With Long Name2 ms0055
Scenario: Changing Description On Tag With Numbers In Name2 ms0066
Scenario: Changing Description On Tag With Permitted Symbols In Name3 ms0044
Scenario: Changing Description On Tag With Short Description3 ms0044
Scenario: Changing Description On Tag With Short Name3 ms0044
Scenario: Changing Device Status To Disabled3 ms0099
Scenario: Changing Device Status To Enabled5 ms0099
Scenario: Changing Group's Description To Non-Uniqe One6 ms0077
Scenario: Changing Group's Description To Uniqe One5 ms0077
Scenario: Changing Group's Name To Contain Invalid Symbols In Name Without Changing Description5 ms0088
Scenario: Changing Group's Name To Contain Permitted Symbols In Name Without Changing Description5 ms0077
Scenario: Changing Group's Name To Non-Unique One5 ms0099
Scenario: Changing Group's Name To Short One Without Changing Description5 ms0077
Scenario: Changing Group's Name To Unique One6 ms0077
Scenario: Changing Group's Name To a Long One Without Changing Description5 ms0077
Scenario: Changing Group's Name To a Too Long One Without Changing Description5 ms0088
Scenario: Changing Group's Name To a Too Short One Without Changing Description4 ms0088
Scenario: Changing Tag's Description To Non-Unique One3 ms0055
Scenario: Changing Tag's Description To Unique One3 ms0077
Scenario: Changing Tag's Name To Contain Invalid Symbols In Name Without Description3 ms0055
Scenario: Changing Tag's Name To Contain Permitted Symbols In Name Without Description3 ms0055
Scenario: Changing Tag's Name To Non-Unique One4 ms0066
Scenario: Changing Tag's Name To Short One Without Description3 ms0077
Scenario: Changing Tag's Name To Unique One3 ms0077
Scenario: Changing Tag's Name To a Long One Without Description4 ms0077
Scenario: Changing Tag's Name To a Too Long One Without Description3 ms0055
Scenario: Changing Tag's Name To a Too Short One Without Description5 ms0055
Scenario: Changing description of a nonexisting role2 ms0077
Scenario: Changing job description to non-unique one8 ms0077
Scenario: Changing job description to the long one4 ms0066
Scenario: Changing job description to unique one5 ms0066
Scenario: Changing job description to very short one4 ms0077
Scenario: Changing job name to a long one without description4 ms0077
Scenario: Changing job name to a too long one without description4 ms0055
Scenario: Changing job name to a too short one without description5 ms0066
Scenario: Changing job name to contain invalid symbols in name without description5 ms0044
Scenario: Changing job name to contain permitted symbols in name without description4 ms0055
Scenario: Changing job name to non-unique one5 ms0088
Scenario: Changing job name to short one without description5 ms0077
Scenario: Changing job name to unique one4 ms0099
Scenario: Changing name of a nonexisting role2 ms0077
Scenario: Changing role description to a valid one2 ms0066
Scenario: Changing role name so it is too long2 ms0066
Scenario: Changing role name to contain special character2 ms0044
Scenario: Changing role name to null2 ms0066
Scenario: Changing role's name to a valid one2 ms0066
Scenario: Channel info queries based on datastore channel filters8 ms005050
Scenario: ChannelInfo client ID and topic data based on the client id13 ms002828
Scenario: ChannelInfo client ID based on the account id10 ms002626
Scenario: ChannelInfo last published date10 ms003030
Scenario: ChannelInfo topic data based on the account id11 ms002626
Scenario: Check account properties4 ms0044
Scenario: Check the Device Connection Domain data seetting3 ms0022
Scenario: Check the database cache coherency11 ms003030
Scenario: Check the mapping for message semantic topics10 ms003030
Scenario: Check the message store10 ms002020
Scenario: Check the sanity of the Device Connection Domain data initialization2 ms0022
Scenario: Child account expires after parent5 ms0099
Scenario: Child account expires before parent6 ms001111
Scenario: Child account has null expiration date4 ms0099
Scenario: Client Id based ClientInfo data check8 ms002828
Scenario: Compare domain entries7 ms0033
Scenario: Connect to the system and publish some data0.2 sec002222
Scenario: Connection Service factory sanity checks2 ms0022
Scenario: Count access info entities in a specific scope34 ms002424
Scenario: Count access role entities by scope10 ms003939
Scenario: Count connections in empty scope2 ms0044
Scenario: Count connections in scope3 ms0055
Scenario: Count devices with a specific BIOS version4 ms0066
Scenario: Count domains in a blank database7 ms0044
Scenario: Count domains in the database6 ms0077
Scenario: Count events in empty scope4 ms0066
Scenario: Count groups9 ms001414
Scenario: Count groups in a blank database6 ms0055
Scenario: Count job items3 ms0077
Scenario: Count job items in wrong - empty - scope3 ms0088
Scenario: Count role permissions in specific scopes4 ms001818
Scenario: Count roles in specific scopes5 ms001515
Scenario: Count step definition items4 ms0044
Scenario: Count step definitions in wrong (empty) scope3 ms0011
Scenario: Count steps in the database3 ms001414
Scenario: Count user3 ms0066
Scenario: Counting created roles items in the DB2 ms0055
Scenario: Create a regular event14 ms0088
Scenario: Create a single device with an empty string for clientID4 ms0044
Scenario: Create a single device with null clientID value4 ms0044
Scenario: Create a valid job entry18 ms0066
Scenario: Create an event with a null scope ID7 ms0077
Scenario: Create and count several execution items for a job2 ms001111
Scenario: Create index with specific prefix5 ms001212
Scenario: Create multiple users3 ms0055
Scenario: Create regular access permissions10 ms002020
Scenario: Create same user in different accounts1.1 sec114015
Scenario: Create scheduler with correct end date0 ms2158
Scenario: Create scheduler with empty schedule name9 ms0088
Scenario: Create scheduler with end date before start date13 ms2169
Scenario: Create scheduler with invalid Retry Interval property5 ms0099
Scenario: Create scheduler with invalid cron job trigger property11 ms0099
Scenario: Create scheduler with invalid schedule name30 ms0088
Scenario: Create scheduler with short schedule name8 ms0088
Scenario: Create scheduler with too long schedule name20 ms0088
Scenario: Create scheduler with valid Retry Interval property5 ms0077
Scenario: Create scheduler with valid cron job trigger property9 ms0077
Scenario: Create scheduler with valid schedule name18 ms0066
Scenario: Create scheduler without Cron Job Trigger property7 ms0099
Scenario: Create scheduler without Retry Interval property6 ms0099
Scenario: Create scheduler without start date24 ms0077
Scenario: Create some regular role permissions4 ms0099
Scenario: Create user that already exist4 ms0077
Scenario: Create user that has more than DB allowed length7 ms0055
Scenario: Create user with short name31 ms0055
Scenario: Create user with special characters in his name4 ms0055
Scenario: Create with permissions10 ms001414
Scenario: Create with permissions and a role11 ms001717
Scenario: Create with permissions and a role in the wrong scope11 ms001515
Scenario: Creating 100 Sub-accounts While InfiniteChildAccounts Is Set To True6 ms0077
Scenario: Creating A Device With Disabled Status4 ms0077
Scenario: Creating A Device With Enabled Status5 ms0077
Scenario: Creating A Device With Long Display Name4 ms0077
Scenario: Creating A Device With Long Name7 ms0077
Scenario: Creating A Device With Name Containing Invalid Symbols6 ms0088
Scenario: Creating A Device With Name Containing Permitted Symbols4 ms0077
Scenario: Creating A Device With No Name3 ms0088
Scenario: Creating A Device With Non-unique Display Name5 ms0077
Scenario: Creating A Device With Non-unique Name4 ms001010
Scenario: Creating A Device With Short Display Name5 ms0077
Scenario: Creating A Device With Short Name4 ms0077
Scenario: Creating A Device With Too Long Display Name7 ms0088
Scenario: Creating A Device With Too Long Name5 ms0088
Scenario: Creating A Device With Unique Name6 ms0099
Scenario: Creating A Valid Account5 ms0055
Scenario: Creating An Account With Long Name5 ms0055
Scenario: Creating An Account With Long Organization Name4 ms0055
Scenario: Creating An Account With Non-unique Name4 ms0088
Scenario: Creating An Account With Numbers And Valid Symbols In Name5 ms0055
Scenario: Creating An Account With Short Name4 ms0055
Scenario: Creating An Account With Short Organization Name4 ms0055
Scenario: Creating An Account With Special Symbols In Organization Name5 ms0055
Scenario: Creating An Account With Too Long Organization Name4 ms0066
Scenario: Creating An Account With Unique Name7 ms0077
Scenario: Creating An Account With Wrong TLD Format In Email6 ms001010
Scenario: Creating An Account Without Email4 ms0066
Scenario: Creating An Account Without Name5 ms0066
Scenario: Creating An Account Without Ogranization Name6 ms0066
Scenario: Creating And Account Without "@" In Email5 ms0066
Scenario: Creating Devices And Than Setting Device Service So It Does Not Allow Devices5 ms001212
Scenario: Creating Devices And Then Changing Device Service Values6 ms001010
Scenario: Creating Devices Under Account That Allows Infinite Child Devices8 ms001010
Scenario: Creating Devices Under Account That Does Not Allow Devices7 ms0099
Scenario: Creating Devices Under Account That Has Limited Child Devices4 ms001313
Scenario: Creating Endpoint Non-Unique "Domain Name"3 ms0088
Scenario: Creating Endpoint Non-Unique "Port"4 ms0088
Scenario: Creating Endpoint Non-Unique "Schema"10 ms0099
Scenario: Creating Endpoint With "Domain Name" Only3 ms0066
Scenario: Creating Endpoint With "Port" Only3 ms0066
Scenario: Creating Endpoint With "Schema" Only3 ms0066
Scenario: Creating Endpoint With Disabled Secure Field5 ms0066
Scenario: Creating Endpoint With Enabled Secure Field3 ms0066
Scenario: Creating Endpoint With Invalid "Domain Name"4 ms0066
Scenario: Creating Endpoint With Invalid "Schema" containing symbols2 ms0066
Scenario: Creating Endpoint With Long "Domain Name"3 ms0055
Scenario: Creating Endpoint With Max Length "Port"4 ms0055
Scenario: Creating Endpoint With NULL parameters8 ms0066
Scenario: Creating Endpoint With Schema Containing "http://"3 ms0066
Scenario: Creating Endpoint With Schema Containing "https://"3 ms0066
Scenario: Creating Endpoint With Short "Domain Name"5 ms0066
Scenario: Creating Endpoint With Short "Schema"5 ms0066
Scenario: Creating Endpoint With Small Number "Port"4 ms0066
Scenario: Creating Endpoint With Too Big "Port"3 ms0066
Scenario: Creating Endpoint With Too Long "Domain Name"5 ms0066
Scenario: Creating Endpoint With Too Long "Schema"4 ms0066
Scenario: Creating Endpoint Without "Domain Name"4 ms0066
Scenario: Creating Endpoint Without "Port"3 ms0066
Scenario: Creating Endpoint Without "Schema"3 ms0066
Scenario: Creating Endpoint Without Long "Schema"3 ms0055
Scenario: Creating Endpoint with invalid "Schema" which contains only numbers4 ms0066
Scenario: Creating Group Invalid Symbols In Name Without Description6 ms0077
Scenario: Creating Group With Invalid Symbols In Name With Valid Description5 ms0077
Scenario: Creating Group With Long Name With Valid Description5 ms0066
Scenario: Creating Group With Long Name Without Description5 ms0066
Scenario: Creating Group With Numbers In Name With Valid Description5 ms0088
Scenario: Creating Group With Permitted Symbols And Numbers In Name Without Description6 ms0066
Scenario: Creating Group With Permitted Symbols In Name With Valid Description6 ms0066
Scenario: Creating Group With Short Name With Valid Description5 ms0066
Scenario: Creating Group With Short Name Without Description5 ms0066
Scenario: Creating Group With Too Long Name With Valid Description5 ms0077
Scenario: Creating Group With Too Long Name Without Description5 ms0077
Scenario: Creating Group With Too Short Name With Valid Description6 ms0077
Scenario: Creating Group With Too Short Name Without Description6 ms0077
Scenario: Creating Group Without a Name And With Valid Description7 ms0077
Scenario: Creating Group Without a Name And Without Description5 ms0077
Scenario: Creating Groups And Than Setting Group Service So It Does Not Allow Groups5 ms001111
Scenario: Creating Groups And Then Changing InfiniteChildGroups To False And Set MaxNumberChildGroups7 ms001010
Scenario: Creating Groups Under Account That Allows Infinite Child Groups4 ms0099
Scenario: Creating Groups Under Account That Does Not Allow Groups6 ms0099
Scenario: Creating Groups Under Account That Has Limited Child Groups4 ms001212
Scenario: Creating Jobs And Than Setting Job Service So It Does Not Allow Jobs6 ms001212
Scenario: Creating Jobs And Then Changing Job Service Values6 ms001010
Scenario: Creating Jobs Under Account That Allows Infinite Child Devices4 ms001010
Scenario: Creating Jobs Under Account That Does Not Allow Jobs5 ms0099
Scenario: Creating Jobs Under Account That Has Limited Child Jobs4 ms001313
Scenario: Creating Non-Unique Group With Valid Description5 ms0088
Scenario: Creating Non-Unique Tag With Valid Description5 ms0055
Scenario: Creating Non-unique Group Without Description7 ms0088
Scenario: Creating Non-unique Tag Without Description7 ms0044
Scenario: Creating Roles And Than Setting Role Service So It Does Not Allow Roles6 ms001111
Scenario: Creating Roles And Then Changing Role Service Values6 ms001010
Scenario: Creating Roles Under Account That Allows Infinite Child Roles6 ms001010
Scenario: Creating Roles Under Account That Does Not Allow Roles5 ms0099
Scenario: Creating Roles Under Account That Has Limited Child Roles5 ms001212
Scenario: Creating Sub-accounts When InfiniteChildAccoounts Is Set To False And maxNumberChildAccounts Is Set5 ms001313
Scenario: Creating Sub-accounts When InfiniteChildAccoounts Is Set To True And maxNumberChildAccounts Is Set6 ms001414
Scenario: Creating Sub-accounts When InfiniteChildAccounts Is Set To False4 ms0099
Scenario: Creating Sub-accounts when InfiniteChildAccounts Is Set To True5 ms001212
Scenario: Creating Tag With Invalid Symbols In Name With Valid Description5 ms0044
Scenario: Creating Tag With Invalid Symbols In Name Without Description3 ms0044
Scenario: Creating Tag With Long Name With Valid Description4 ms0044
Scenario: Creating Tag With Long Name Without Description6 ms0044
Scenario: Creating Tag With Numbers In Name With Valid Description3 ms0044
Scenario: Creating Tag With Numbers In Name Without Description5 ms0044
Scenario: Creating Tag With Permitted Symbols In Name With Valid Description3 ms0044
Scenario: Creating Tag With Permitted Symbols In Name Without Description5 ms0044
Scenario: Creating Tag With Short Name With Valid Description6 ms0044
Scenario: Creating Tag With Short Name Without Description6 ms0044
Scenario: Creating Tag With Too Long Name With Valid Description3 ms0044
Scenario: Creating Tag With Too Long Name Without Description6 ms0044
Scenario: Creating Tag With Too Short Name With Valid Description4 ms0044
Scenario: Creating Tag With Too Short Name Without Description5 ms0044
Scenario: Creating Tag Without a Name And With Valid Description4 ms0044
Scenario: Creating Tag Without a Name And Without Description4 ms0044
Scenario: Creating Tags And Than Setting Tag Service So It Does Not Allow Tags5 ms001111
Scenario: Creating Tags And Then Changing Tag Service Values5 ms001010
Scenario: Creating Tags Under Account That Allows Infinite Child Devices5 ms001010
Scenario: Creating Tags Under Account That Does Not Allow Tags5 ms0099
Scenario: Creating Tags Under Account That Has Limited Child Tags5 ms001212
Scenario: Creating Unique Group With Long Description5 ms0066
Scenario: Creating Unique Group With Non-unique Description5 ms0077
Scenario: Creating Unique Group With Short Description6 ms0066
Scenario: Creating Unique Group With Unique Description5 ms0066
Scenario: Creating Unique Group Without Description5 ms0066
Scenario: Creating Unique Tag With Long Description11 ms0044
Scenario: Creating Unique Tag With Non-unique Description4 ms0055
Scenario: Creating Unique Tag With Short Description4 ms0044
Scenario: Creating Unique Tag With Unique Description4 ms0044
Scenario: Creating Unique Tag Without Description12 ms0044
Scenario: Creating Users And Than Setting User Service So It Does Not Allow Users6 ms001111
Scenario: Creating Users And Then Changing User Service Values6 ms001010
Scenario: Creating Users Under Account That Allows Infinite Child Users6 ms001010
Scenario: Creating Users Under Account That Does Not Allow Users5 ms0099
Scenario: Creating Users Under Account That Has Limited Child Users9 ms001212
Scenario: Creating Valid Endpoint5 ms0066
Scenario: Creating a Access Group with invalid special symbols in name0 ms0044
Scenario: Creating a Device With Permitted Symbols in its Display Name5 ms0077
Scenario: Creating a Device With Unique Display Name4 ms0088
Scenario: Creating a job with name only8 ms0066
Scenario: Creating a job with null name32 ms0055
Scenario: Creating a job without name with valid description5 ms0055
Scenario: Creating a new PASSWORD Credential meeting a custom length requirement5 ms0044
Scenario: Creating a new PASSWORD Credential meeting the standard length requirement15 ms0033
Scenario: Creating a new PASSWORD Credential not meeting a custom length requirement5 ms0055
Scenario: Creating a new PASSWORD Credential not meeting the standard length requirement6 ms0044
Scenario: Creating a role name with allowed symbols in its name3 ms0055
Scenario: Creating a role with 255 characters long description2 ms0055
Scenario: Creating a role with a name and description that contain digits only2 ms0055
Scenario: Creating a role with forbidden symbols in its name0 ms0044
Scenario: Creating a role with name only3 ms0055
Scenario: Creating a role with null name3 ms0055
Scenario: Creating a role with regular name and very short description" as description cannot be too short, as even one character is enough3 ms0055
Scenario: Creating a role with special characters in the description2 ms0044
Scenario: Creating a role with the name that contains digits2 ms0055
Scenario: Creating a role with too long name3 ms0055
Scenario: Creating a role with too short name2 ms0055
Scenario: Creating a role with valid name and with too long description4 ms0033
Scenario: Creating a role wtih 255 characters long name3 ms0055
Scenario: Creating a single device with case sensitive clientID4 ms0055
Scenario: Creating a single device with clientID that contains 255 characters5 ms0055
Scenario: Creating a single device with clientID that contains 256 characters4 ms0044
Scenario: Creating a single device with clientID that contains invalid character3 ms0044
Scenario: Creating a single device with clientID that contains invalid characters6 ms0044
Scenario: Creating a single device with spaces in clientID4 ms0055
Scenario: Creating a single device with valid clientID3 ms0055
Scenario: Creating a valid Access Group with numbers in name3 ms0055
Scenario: Creating a valid Access Group with only numbers in name3 ms0055
Scenario: Creating a valid Access Group with unique name4 ms0055
Scenario: Creating a valid Access Group with valid special symbols in name3 ms0055
Scenario: Creating a valid role2 ms0055
Scenario: Creating an Access Group with empty name3 ms0044
Scenario: Creating an Access Group with long name3 ms0055
Scenario: Creating an Access Group with short name3 ms0055
Scenario: Creating an Access Group with too long name3 ms0044
Scenario: Creating an Access Group with too short name3 ms0044
Scenario: Creating an Access Group without name and with description3 ms0044
Scenario: Creating and Deleting Endpoint Two Times7 ms002525
Scenario: Creating index with regular user5 ms002525
Scenario: Creating job with invalid symbols in name without description25 ms0044
Scenario: Creating job with long name and valid description7 ms0066
Scenario: Creating job with long name without description7 ms0066
Scenario: Creating job with numbers in name and valid description5 ms0066
Scenario: Creating job with numbers in name without description6 ms0066
Scenario: Creating job with permitted symbols in name without description6 ms0033
Scenario: Creating job with short name and valid job description6 ms0066
Scenario: Creating job with short name without description7 ms0066
Scenario: Creating job with too long name and valid description7 ms0055
Scenario: Creating job with too long name without description7 ms0055
Scenario: Creating job with too short name and valid description6 ms0055
Scenario: Creating job with too short name without description22 ms0055
Scenario: Creating job without name and without description7 ms0055
Scenario: Creating new device and tagging it with specific Tag13 ms001414
Scenario: Creating new device, tagging it with specific Tag and then deleting this Tag6 ms001616
Scenario: Creating non-unique Access Group5 ms0055
Scenario: Creating non-unique Access Group with unique description3 ms0055
Scenario: Creating non-unique job name with valid job description11 ms0077
Scenario: Creating two device with the same clientID3 ms0055
Scenario: Creating two indexes with daily index5 ms001717
Scenario: Creating two indexes with hourly index8 ms001717
Scenario: Creating two indexes with weekly index8 ms001717
Scenario: Creating two roles with the same description2 ms0066
Scenario: Creating two roles with the same name2 ms0077
Scenario: Creating unique Access Group with long description2 ms0055
Scenario: Creating unique Access Group with non-unique description2 ms0066
Scenario: Creating unique Access Group with numbers in description3 ms0055
Scenario: Creating unique Access Group with only numbers in description2 ms0055
Scenario: Creating unique Access Group with short description2 ms0055
Scenario: Creating unique Access Group with special symbols in description8 ms2114
Scenario: Creating unique Access Group with unique description3 ms0055
Scenario: Creating unique job with long description5 ms0066
Scenario: Creating unique job with non-unique description5 ms001010
Scenario: Creating unique job with short description5 ms0066
Scenario: Creating user11 ms0055
Scenario: Creation of access role with neither acess info and role entities7 ms001212
Scenario: Creation of access role without an acess info entity7 ms001212
Scenario: D1 Device publish to CTRL_ACC_REPLY5 ms0099
Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI6 ms0099
Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed2 ms0099
Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed2 ms0077
Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY6 ms0099
Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY3 ms0099
Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account3 ms0099
Scenario: D5 Device subscribe - publish - admin on CTRL_ACC6 ms0099
Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI3 ms0099
Scenario: D7 Device publish to ACL_DATA_ACC is not allowed5 ms0099
Scenario: D8 Device create sub-topic on ACL_DATA_ACC is not allowed4 ms0099
Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed5 ms0088
Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed4 ms0099
Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI2 ms0099
Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed4 ms0099
Scenario: DM13 Data manage subscribe on ACL_CTRL_ACC_NOTIFY is not allowed4 ms0088
Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY3 ms0099
Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY7 ms0099
Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account5 ms0099
Scenario: DM5 Data manage publish to CTRL_ACC is not allowed4 ms0099
Scenario: DM6 Data manage create sub-topic on CTRL_ACC is not allowed6 ms0099
Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed5 ms0088
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_REPLY8 ms0099
Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed5 ms0099
Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed3 ms001010
Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed5 ms0099
Scenario: DV13 Data view create sub-topic on ACL_CTRL_ACC_CLI is not allowed4 ms0099
Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed4 ms0099
Scenario: DV17 Data view subscribe on ACL_CTRL_ACC_NOTIFY is not allowed14 ms0088
Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY6 ms0099
Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY10 ms0099
Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account7 ms0099
Scenario: DV5 Data view publish to CTRL_ACC is not allowed4 ms0099
Scenario: DV6 Data view create sub-topic on CTRL_ACC is not allowed8 ms0099
Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed3 ms0088
Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI3 ms0099
Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed5 ms0099
Scenario: Decreasing MaxNumberChildAccounts When Sub-accounts Are Already Created4 ms001515
Scenario: Delete Kapua system user4 ms0055
Scenario: Delete a access info entity with permissions and roles8 ms001717
Scenario: Delete a connection from the database2 ms0088
Scenario: Delete a group from the database8 ms001010
Scenario: Delete a group from the database - Unknown group ID5 ms0066
Scenario: Delete a job4 ms001111
Scenario: Delete a job execution item3 ms0088
Scenario: Delete a job execution item twice2 ms0099
Scenario: Delete a job twice5 ms001010
Scenario: Delete a non existent event5 ms0077
Scenario: Delete a non existing connection3 ms0077
Scenario: Delete a non existing permission entity6 ms001616
Scenario: Delete a non existing role entry4 ms001111
Scenario: Delete a non-existing step3 ms001212
Scenario: Delete a nonexistent domain6 ms0055
Scenario: Delete a step definition5 ms0088
Scenario: Delete a step definition twice4 ms0077
Scenario: Delete access role from user12 ms001212
Scenario: Delete an access info entity twice10 ms001111
Scenario: Delete an access info entity using the wrong scope ID7 ms001111
Scenario: Delete an existing access info entity9 ms001212
Scenario: Delete an existing access permission entity8 ms001515
Scenario: Delete an existing access role entry6 ms002222
Scenario: Delete an existing account3 ms0055
Scenario: Delete an existing device from the registry2 ms0044
Scenario: Delete an existing event5 ms0099
Scenario: Delete an existing role5 ms001010
Scenario: Delete an existing role twice7 ms001616
Scenario: Delete an existing step3 ms001111
Scenario: Delete items based on query results13 ms008484
Scenario: Delete items by date ranges0.87 sec00132132
Scenario: Delete items by the datastore ID13 ms006666
Scenario: Delete middle child expiration4 ms001515
Scenario: Delete nonexisting account6 ms0044
Scenario: Delete nonexisting role permission5 ms001313
Scenario: Delete parent expiration5 ms001414
Scenario: Delete permissions from role14 ms001818
Scenario: Delete role permissions5 ms001010
Scenario: Delete scheduler5 ms0088
Scenario: Delete scheduler which doesn't exist5 ms0055
Scenario: Delete the Kapua system account3 ms0055
Scenario: Delete the last created domain entry6 ms0088
Scenario: Delete user3 ms0066
Scenario: Delete user that doesn't exist4 ms0055
Scenario: Deleting "Cron Schedule" Triggering6 ms001313
Scenario: Deleting "Device Schedule" Triggering6 ms001111
Scenario: Deleting "Interval Schedule" Triggering4 ms001313
Scenario: Deleting Device With Disabled Status6 ms001010
Scenario: Deleting Device With Enabled Status4 ms001010
Scenario: Deleting Endpoint Domain Name And Leaving it Empty3 ms0088
Scenario: Deleting Endpoint Which Does Not Exist4 ms0066
Scenario: Deleting Existing Group4 ms0088
Scenario: Deleting Existing Group And Creating It Again With Same Name4 ms001212
Scenario: Deleting Existing Tag And Creating It Again With Same Name2 ms0077
Scenario: Deleting Group's Name And Leaving It Empty Without Changing Description4 ms0088
Scenario: Deleting Non-Existent Tag3 ms0077
Scenario: Deleting Tag From Device3 ms0088
Scenario: Deleting Tag's Name And Leaving It Empty Without Description4 ms0055
Scenario: Deleting Unexisitng Group5 ms001111
Scenario: Deleting a Permission10 ms002121
Scenario: Deleting a non-existing Access Group3 ms0066
Scenario: Deleting a role twice2 ms0077
Scenario: Deleting admin role14 ms0077
Scenario: Deleting an existing Access Group2 ms0055
Scenario: Deleting an existing Access Group and creating it again with the same name2 ms0077
Scenario: Deleting an existing role2 ms0066
Scenario: Deleting default permissions from admin role18 ms001212
Scenario: Deleting existing tag2 ms0099
Scenario: Deleting role after adding it to user12 ms001414
Scenario: Deleting role after it has been added to user in child account10 ms001616
Scenario: Deleting user in account that is higher in hierarchy0.96 sec122023
Scenario: Deleting user in account that is lower in hierarchy0.91 sec123024
Scenario: Device connection update3 ms0077
Scenario: Device factory sanity checks2 ms0022
Scenario: Device queries3 ms001010
Scenario: Device query - find by BIOS version3 ms0077
Scenario: Domain entry query6 ms0055
Scenario: Domain with null actions7 ms0055
Scenario: Domain with null name7 ms0055
Scenario: Domains with duplicate names6 ms0088
Scenario: Duplicate group name in root scope5 ms001010
Scenario: Duplicate role names5 ms0077
Scenario: Editing Access Group description to description with numbers2 ms0055
Scenario: Editing Access Group description to description with only numbers2 ms0055
Scenario: Editing Access Group description to description with special symbols2 ms0044
Scenario: Editing Access Group description to long description2 ms0055
Scenario: Editing Access Group description to non-unique one2 ms0055
Scenario: Editing Access Group description to short description2 ms0055
Scenario: Editing Access Group description to unique one4 ms0077
Scenario: Editing Access Group name to a long one2 ms0077
Scenario: Editing Access Group name to a too long one2 ms0055
Scenario: Editing Access Group name to empty name3 ms0055
Scenario: Editing Access Group name to name that contains numbers3 ms0077
Scenario: Editing Access Group name to name that contains only numbers3 ms0077
Scenario: Editing Access Group name to name with invalid special symbols in name0 ms0055
Scenario: Editing Access Group name to name with valid special symbols3 ms0077
Scenario: Editing Access Group name to non-unique one4 ms0066
Scenario: Editing Access Group name to short one2 ms0077
Scenario: Editing Access Group name to too short one3 ms0055
Scenario: Editing Access Group name to valid one2 ms0077
Scenario: Editing Endpoint Domain Name So It Contains Invalid Symbols4 ms0088
Scenario: Editing Endpoint Domain Name So It Contains Only Numbers4 ms0088
Scenario: Editing Endpoint Domain Name So It Has Max Value5 ms0077
Scenario: Editing Endpoint Domain Name So It Has Min Value3 ms0077
Scenario: Editing Endpoint Domain Name To Non-unique Value3 ms0099
Scenario: Editing Endpoint Domain Name To Unique Value4 ms0077
Scenario: Editing Endpoint Port To Non-unique Value3 ms0099
Scenario: Editing Endpoint Port To Unique Value4 ms0077
Scenario: Editing Endpoint Schema And Leaving It Empty4 ms0088
Scenario: Editing Endpoint Schema So It Contains "http://"4 ms0088
Scenario: Editing Endpoint Schema So It Contains "https://"4 ms0088
Scenario: Editing Endpoint Schema So It Contains Invalid Symbols4 ms0088
Scenario: Editing Endpoint Schema So It Contains Only Numbers5 ms0088
Scenario: Editing Endpoint Schema So It Has Max Length3 ms0077
Scenario: Editing Endpoint Schema So It Has Min Length3 ms0077
Scenario: Editing Endpoint Schema To Non-unique Value15 ms0088
Scenario: Editing Endpoint Schema To Unique Value4 ms0077
Scenario: Editing Endpoint Secure Field To Non-unique Value3 ms0099
Scenario: Editing Endpoint Secure Field To Unique Value4 ms0077
Scenario: Editing Endpoint To NULL Values5 ms001414
Scenario: Editing Endpoint To Non-unique Endpoint6 ms001010
Scenario: Editing Group's Name To Contain Numbers Without Changing Description6 ms0077
Scenario: Editing Tag's Name To Contain Numbers Without Description3 ms0077
Scenario: Empty query results are supported6 ms0088
Scenario: Event factory sanity checks4 ms0022
Scenario: Event service domain check26 ms0022
Scenario: Every account must have the default configuration items5 ms0033
Scenario: Execute possible docker steps to show its usage3 ms231033
Scenario: Executing Job And Then Restarting Device10 ms004545
Scenario: Executing Job When Device Connected After End Date And Time9 ms003939
Scenario: Executing Job When Device Connected After The Specified Start Date And Time13 ms003838
Scenario: Executing Job When Device Connected Before End Date And Time9 ms003939
Scenario: Executing Job When Device Connected Before The Specified Start Date And Time8 ms003737
Scenario: Executing Job Without Steps8 ms004040
Scenario: Extra long continuous test with multiple subscenarios with LOOSE default connection mode12 ms00419419
Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode10 ms00397397
Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode and no previously defined devices6 ms00305305
Scenario: Find a connection by its IDs2 ms0066
Scenario: Find a connection by its client ID3 ms0066
Scenario: Find a group entry in the database6 ms0099
Scenario: Find a non existing event6 ms0066
Scenario: Find account by Id4 ms0044
Scenario: Find account by Ids4 ms0044
Scenario: Find account by name3 ms0044
Scenario: Find account by random Id0 ms0033
Scenario: Find all child accounts6 ms0033
Scenario: Find an access info entity9 ms001111
Scenario: Find an access info entity by user ID10 ms001010
Scenario: Find an event by its ID6 ms0066
Scenario: Find an existing access role entity7 ms001313
Scenario: Find by name nonexisting account4 ms0033
Scenario: Find correct number of messages by corresponding metric0.25 sec005858
Scenario: Find device by client ID3 ms0033
Scenario: Find device by registry ID2 ms0044
Scenario: Find last created permission8 ms001212
Scenario: Find multiple users3 ms0055
Scenario: Find role by ID5 ms0077
Scenario: Find self account by id5 ms001111
Scenario: Find self account by id and scope id6 ms001111
Scenario: Find self account by name4 ms001111
Scenario: Find the last created domain entry6 ms0055
Scenario: Find user by id3 ms0055
Scenario: Find user by its email3 ms0066
Scenario: Find user by its phone number3 ms0066
Scenario: Find user by name3 ms0055
Scenario: Find user by name that doesn't exist3 ms0033
Scenario: Find user with id and scope id that doesn't exist3 ms0033
Scenario: Finding all messages by selecting all metrics0.22 sec0-20-1040+1240
Scenario: Finding correct number of messages by corresponding two metrics0.24 sec005252
Scenario: Finding messages with incorrect metric parameters0.23 sec007272
Scenario: Finding user by expiration date in the future3 ms0055
Scenario: Finding user by expiration date in the past2 ms0066
Scenario: Finding user by expiration date in the present4 ms0066
Scenario: Generic connection query2 ms0088
Scenario: Get metadata3 ms0033
Scenario: Group with a null name6 ms0077
Scenario: Handle account creation13 ms0033
Scenario: Handle duplicate account names5 ms0055
Scenario: Handle null account name23 ms0044
Scenario: Handling of 2 birth messages5 ms001212
Scenario: Handling of a disconnect message from a non existing device8 ms001010
Scenario: Have Two Devices in The Same Group Without Description6 ms001313
Scenario: I try to find a non-existing connection2 ms0066
Scenario: If user credential expiration date is before today, user can not login6 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 login4 ms001313
Scenario: If user expiration date is before today, user can not login4 ms001313
Scenario: If user expiration date is today, user can not login because expiration date was reached3 ms001313
Scenario: If user expiration date is tomorrow, user can login3 ms001212
Scenario: Init Security Context for all scenarios1.4 sec114648
Scenario: Installing a package13 ms001313
Scenario: Interval Job" Schedule With Too Long Name4 ms001111
Scenario: It must be possible to query for specific entries in the role database6 ms0088
Scenario: It should not be possible to change the configuration items3 ms0055
Scenario: Job execution factory sanity checks2 ms0022
Scenario: Job factory sanity checks2 ms0033
Scenario: Job with a duplicate name4 ms0099
Scenario: Job with a null name3 ms0088
Scenario: Job with a null scope ID2 ms0099
Scenario: Job with an empty name2 ms0088
Scenario: List Endpoints Created From Sub-Account3 ms223126
Scenario: List Endpoints From "kapua-sys" Account2 ms24511
Scenario: List Endpoints From Sub-Account Of Another Sub-Account3 ms223126
Scenario: List Endpoints From Sub-account5 ms212115
Scenario: MetricsInfo client ID and topic data based on the client id9 ms003434
Scenario: MetricsInfo last published date15 ms004848
Scenario: Modify a role that was deleted5 ms0099
Scenario: Modify an existing account4 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 parent4 ms001515
Scenario: Modify nonexisting account4 ms0066
Scenario: Modify parent expiration so that it still expires after child6 ms001414
Scenario: Modify parent expiration to before child expiration4 ms001515
Scenario: Modifying Sub-account of a different parent account11 ms002525
Scenario: Moving Device From One Group With Description to Another5 ms001414
Scenario: Nameless role entry4 ms0077
Scenario: Negative scenario when client connects twice with same client id4 ms001111
Scenario: New connection with reserved ID5 ms003434
Scenario: Permission factory sanity checks4 ms0033
Scenario: Positive scenario without stealing link8 ms001212
Scenario: Query based on message ordering10 ms002020
Scenario: Query based on metrics ordering9 ms002020
Scenario: Query before schema search4 ms008282
Scenario: Query for a specific group by name5 ms001616
Scenario: Query for all the access info entities of a specific user13 ms001818
Scenario: Query for all the access info entities of an invalid user10 ms001010
Scenario: Query for executions of a specific job3 ms001818
Scenario: Query for jobs with specified name4 ms0099
Scenario: Query for step definitions4 ms0077
Scenario: Query user0.11 sec0066
Scenario: Querying Other Items With All Account Permissions7 ms003939
Scenario: Regular connection2 ms0077
Scenario: Regular creation of Access Role entity7 ms001414
Scenario: Regular domain6 ms0055
Scenario: Regular group in random scope6 ms0077
Scenario: Regular group in root scope5 ms0077
Scenario: Regular job creation4 ms001010
Scenario: Regular job execution creation5 ms0077
Scenario: Regular role creation5 ms0099
Scenario: Regular step creation3 ms001111
Scenario: Regular step definition creation6 ms0077
Scenario: Regular step definition with a property list4 ms0044
Scenario: Reset Security Context for all scenarios1 sec114648
Scenario: Restarting a job with Asset Write and Bundle Start steps10 ms002828
Scenario: Restarting a job with Command Execution and Bundle Start steps11 ms002828
Scenario: Restarting a job with Configuration Put and Bundle Start steps9 ms002828
Scenario: Restarting a job with Package Uninstall and Bundle Start steps11 ms002828
Scenario: Restarting a job with invalid Configuration Put and multiple devices two times12 ms003333
Scenario: Restarting a job with invalid Configuration Put step two times12 ms003636
Scenario: Restarting a job with invalid Package Install step and multiple devices two times10 ms003131
Scenario: Restarting a job with invalid Package Install step two times11 ms003434
Scenario: Restarting a job with invalid Package Uninstall step and multiple devices two times49 ms003232
Scenario: Restarting a job with invalid Package Uninstall step two times13 ms003434
Scenario: Restarting a job with valid Configuration Put step and multiple devices two times29 ms003333
Scenario: Restarting a job with valid Configuration Put step two times12 ms003636
Scenario: Restarting a job with valid Package Install step and multiple devices two times53 ms002929
Scenario: Restarting a job with valid Package Install step two times13 ms003434
Scenario: Restarting a job with valid Package Uninstall step and multiple devices two times65 ms003030
Scenario: Restarting a job with valid Package Uninstall step two times10 ms003232
Scenario: Restarting job With invalid Asset Write and multiple two times20 ms003434
Scenario: Restarting job With valid Asset Write step two times18 ms003636
Scenario: Restarting job with Asset Write and Bundle Start steps and multiple devices10 ms003131
Scenario: Restarting job with Asset Write step10 ms002525
Scenario: Restarting job with Asset Write step and multiple devices8 ms002828
Scenario: Restarting job with Bundle Start step11 ms002525
Scenario: Restarting job with Bundle Start step and multiple devices10 ms002727
Scenario: Restarting job with Bundle Stop and Bundle Start step and multiple devices9 ms003131
Scenario: Restarting job with Bundle Stop and Bundle Start steps9 ms002929
Scenario: Restarting job with Bundle Stop step9 ms002525
Scenario: Restarting job with Bundle Stop step and multiple devices10 ms002727
Scenario: Restarting job with Command Execution and Bundle Start steps and multiple devices7 ms003131
Scenario: Restarting job with Command Execution step13 ms002525
Scenario: Restarting job with Command Execution step and multiple devices11 ms002727
Scenario: Restarting job with Configuration Put and Bundle Start steps and multiple devices8 ms003131
Scenario: Restarting job with Configuration Put step8 ms002525
Scenario: Restarting job with Configuration Put step and multiple devices9 ms002727
Scenario: Restarting job with Package Download/Install and Bundle Start steps and multiple devices18 ms005959
Scenario: Restarting job with Package Download/Install step and multiple devices10 ms002727
Scenario: Restarting job with Package Install step8 ms002525
Scenario: Restarting job with Package Uninstall and Bundle start steps and multiple device9 ms003131
Scenario: Restarting job with Package Uninstall step8 ms002525
Scenario: Restarting job with Package Uninstall step and multiple device9 ms002727
Scenario: Restarting job with invalid Asset Write step two times12 ms003636
Scenario: Restarting job with invalid Bundle Start and Bundle Stop steps and multiple devices two times36 ms004141
Scenario: Restarting job with invalid Bundle Start and Bundle Stop steps two times18 ms004343
Scenario: Restarting job with invalid Bundle Start step and multiple devices two times40 ms003535
Scenario: Restarting job with invalid Bundle Start step two times11 ms003737
Scenario: Restarting job with invalid Bundle Stop step and multiple devices two times14 ms003535
Scenario: Restarting job with invalid Bundle Stop step two times15 ms003737
Scenario: Restarting job with invalid Command Execution and Package Install step two times20 ms003636
Scenario: Restarting job with invalid Command Execution and Package Install steps and multiple devices two times13 ms003737
Scenario: Restarting job with invalid Command Execution step and multiple devices two times70 ms003131
Scenario: Restarting job with invalid Command Execution step two times17 ms003232
Scenario: Restarting job with invalid Configuration Put And Command Execution steps two times12 ms003838
Scenario: Restarting job with invalid Configuration Put and Command Execution steps and multiple devices two times11 ms003737
Scenario: Restarting job with invalid Package Uninstall and Asset Write steps and multiple devices two times20 ms003838
Scenario: Restarting job with invalid Package Uninstall and Asset Write steps two times14 ms004040
Scenario: Restarting job with two Bundle Start steps11 ms002929
Scenario: Restarting job with two Bundle Start steps and multiple devices8 ms003131
Scenario: Restarting job with valid Asset Write step and multiple devices two times27 ms003434
Scenario: Restarting job with valid Bundle Start And Bundle Stop steps two times10 ms004343
Scenario: Restarting job with valid Bundle Start and Bundle Stop steps and multiple devices two times13 ms004141
Scenario: Restarting job with valid Bundle Start step and multiple devices two times64 ms003535
Scenario: Restarting job with valid Bundle Start step two times14 ms003737
Scenario: Restarting job with valid Bundle Stop step and multiple devices two times79 ms003535
Scenario: Restarting job with valid Bundle Stop step two times12 ms003737
Scenario: Restarting job with valid Command Execution and Package Install steps and multiple devices two times74 ms003333
Scenario: Restarting job with valid Command Execution and Package Install steps two times65 ms003434
Scenario: Restarting job with valid Command Execution step and multiple devices two times28 ms003131
Scenario: Restarting job with valid Command Execution step two times14 ms003232
Scenario: Restarting job with valid Configuration Put and Command Execution steps and multiple devices two times64 ms003737
Scenario: Restarting job with valid Configuration Put and Command Execution steps two times15 ms003838
Scenario: Restarting job with valid Package Uninstall and Asset Write steps and multiple devices two times94 ms003636
Scenario: Restarting job with valid Package Uninstall and Asset Write steps two times11 ms003838
Scenario: Role creator sanity checks3 ms0022
Scenario: Role entry with no actions5 ms0066
Scenario: Role object equality check5 ms0022
Scenario: Role service related objects sanity checks4 ms0044
Scenario: Search By Client ID And Get Multiple Matches17 ms003737
Scenario: Search By Client ID And Get No Matches3 ms001010
Scenario: Search By Client ID And Get One Match4 ms0088
Scenario: Search By Client ID and Display Name15 ms001212
Scenario: Search By Client ID and Serial Number5 ms001212
Scenario: Search By Client ID and Status5 ms001212
Scenario: Search By Client ID, Display Name and Serial Number4 ms001212
Scenario: Search By Client ID, Display Name and Status4 ms001212
Scenario: Search By Client ID, Display Name, Serial Number and Status5 ms001212
Scenario: Search By Device Status And Get No Matches4 ms0088
Scenario: Search By Device's Display Name And Get One Match5 ms0088
Scenario: Search By Display Name and Serial Number5 ms001212
Scenario: Search By Display Name and Status4 ms001212
Scenario: Search By Full Client ID And Get One Match5 ms001010
Scenario: Search By Non-existing Client ID And Get No Matches4 ms0088
Scenario: Search By One Letter Of Display Name6 ms0088
Scenario: Search By One Letter Of Serial Number3 ms001212
Scenario: Search By Serial Number And Get Multiple Matches5 ms001414
Scenario: Search By Serial Number And Get No Matches3 ms001010
Scenario: Search By Serial Number And Get One Match5 ms001111
Scenario: Search By Serial Number and Status10 ms001212
Scenario: Search By Serial Number, Display Name and Status6 ms001212
Scenario: Search By Specific Serial Number3 ms001010
Scenario: Search By Status And Get Multiple Matches4 ms001010
Scenario: Search by Device Status And Get One Match4 ms001010
Scenario: Search for a non existent client ID2 ms0066
Scenario: Search for an access info entity by an incorrect user ID10 ms001111
Scenario: Search the role database for a random ID4 ms0077
Scenario: Send BIRTH message and then DC message20 ms001515
Scenario: Send BIRTH message and then DC message while broker ip is NOT set9 ms0066
Scenario: Send BIRTH message and then DC message while broker ip is set by System21 ms0088
Scenario: Send BIRTH message and then DC message while broker ip is set by config file24 ms0088
Scenario: Set a correct minimum for password length6 ms0033
Scenario: Set an incorrect minimum for password length5 ms0066
Scenario: Set environment variables87 ms006161
Scenario: Setting InfiniteChildAccounts To False And Increasing MaxNumberChildAccounts When Sub-accounts Are Already Created5 ms001414
Scenario: Setting InfiniteChildAccounts To False When Sub-accounts Are Already Created4 ms001515
Scenario: Setting InfiniteChildAccounts To True And Decreasing MaxNumberChildAccounts When Sub-accounts Are Already Created5 ms001414
Scenario: Setting Lockout Duration To 0 Seconds5 ms001515
Scenario: Setting Lockout Duration To Negative Value5 ms0077
Scenario: Setting Max Failures To 07 ms001515
Scenario: Setting Max Failures To 15 ms001515
Scenario: Setting Max Failures To 1007 ms001515
Scenario: Setting Max Failures To Negative Value10 ms0077
Scenario: Setting Reset After Login Counter To 0 Seconds6 ms001717
Scenario: Setting Reset After Login Counter To Negative Value4 ms0077
Scenario: Setting configuration without mandatory items must raise an error8 ms0055
Scenario: Simple Jetty with rest-api war2 ms2316
Scenario: Simple create13 ms001111
Scenario: Simple positive scenario for creating daily index7 ms001414
Scenario: Simple positive scenario for creating default - weekly index6 ms001212
Scenario: Simple positive scenario for creating hourly index7 ms001414
Scenario: Start Jetty server for all scenarios2 ms2002
Scenario: Start broker for all scenarios0.2 sec004444
Scenario: Start datastore for all scenarios0.27 sec202830
Scenario: Start event broker for all scenarios1.1 sec115052
Scenario: Starting a job with Asset Write and Bundle Start steps15 ms003636
Scenario: Starting a job with Asset Write step10 ms002525
Scenario: Starting a job with Bundle Start step9 ms003434
Scenario: Starting a job with Bundle Stop and Bundle Start steps8 ms003939
Scenario: Starting a job with Bundle Stop step10 ms003535
Scenario: Starting a job with Command Execution and Bundle Start steps8 ms003737
Scenario: Starting a job with Command Execution step11 ms002525
Scenario: Starting a job with Configuration Put and Bundle Start steps9 ms003737
Scenario: Starting a job with Configuration Put step10 ms002525
Scenario: Starting a job with Package Install and Bundle Start steps11 ms003939
Scenario: Starting a job with Package Install step10 ms003232
Scenario: Starting a job with Package Uninstall and Bundle Start steps42 ms003636
Scenario: Starting a job with Package Uninstall step8 ms003333
Scenario: Starting a job with invalid Asset Write step10 ms003131
Scenario: Starting a job with invalid Asset Write step and multiple targets36 ms002929
Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps4 ms2+227+277-2936
Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps and multiple devices13 ms003535
Scenario: Starting a job with invalid Bundle Start step2 ms2+222+227-2431
Scenario: Starting a job with invalid Bundle Stop step3 ms2+222+227-2431
Scenario: Starting a job with invalid Bundle Stop step and multiple devices17 ms002929
Scenario: Starting a job with invalid Command Execution step3 ms2+218+187-2027
Scenario: Starting a job with invalid Configuration Put step13 ms003030
Scenario: Starting a job with invalid Configuration Put step and multiple devices18 ms0-20-1928+2128
Scenario: Starting a job with invalid Package Install step10 ms002929
Scenario: Starting a job with invalid Package Install step and multiple devices27 ms002626
Scenario: Starting a job with invalid Package Uninstall and Asset Write steps11 ms003434
Scenario: Starting a job with invalid Package Uninstall and Asset Write steps and multiple devices10 ms003232
Scenario: Starting a job with invalid Package Uninstall step11 ms002929
Scenario: Starting a job with invalid Package Uninstall step and multiple targets21 ms002626
Scenario: Starting a job with two Bundle Start steps9 ms003939
Scenario: Starting a job with valid Asset Write step11 ms003131
Scenario: Starting a job with valid Asset Write step and multiple targets16 ms002929
Scenario: Starting a job with valid Bundle Start and Bundle Stop steps8 ms003636
Scenario: Starting a job with valid Bundle Start and Bundle Stop steps and multiple devices21 ms003434
Scenario: Starting a job with valid Bundle Start step4 ms2+222+227-2431
Scenario: Starting a job with valid Bundle Stop step3 ms2+222+227-2431
Scenario: Starting a job with valid Bundle Stop step and multiple devices20 ms002929
Scenario: Starting a job with valid Command Execution step14 ms2+218+187-2027
Scenario: Starting a job with valid Configuration Put step2 ms2+222+227-2431
Scenario: Starting a job with valid Configuration Put step and multiple devices31 ms002626
Scenario: Starting a job with valid Package Install step9 ms002929
Scenario: Starting a job with valid Package Install step and multiple devices10 ms002626
Scenario: Starting a job with valid Package Uninstall and Asset Write steps12 ms003333
Scenario: Starting a job with valid Package Uninstall and Asset Write steps and multiple devices13 ms003232
Scenario: Starting a job with valid Package Uninstall step23 ms003030
Scenario: Starting a job with valid Package Uninstall step and multiple targets20 ms002626
Scenario: Starting and stopping the simulator should create a device entry and properly set its status4 ms002020
Scenario: Starting job with Asset Write and Bundle Start steps and multiple devices15 ms003232
Scenario: Starting job with Asset Write step and multiple devices8 ms002828
Scenario: Starting job with Bundle Start step and multiple devices8 ms002828
Scenario: Starting job with Bundle Stop and Bundle Start step and multiple devices10 ms003232
Scenario: Starting job with Bundle Stop step and multiple devices9 ms002828
Scenario: Starting job with Command Execution and Bundle Start steps and multiple devices11 ms003232
Scenario: Starting job with Command Execution step and multiple devices10 ms002828
Scenario: Starting job with Configuration Put and Bundle Start steps and multiple devices8 ms003232
Scenario: Starting job with Configuration Put step and multiple devices8 ms002828
Scenario: Starting job with Package Download/Install and Bundle Start steps and multiple devices9 ms003838
Scenario: Starting job with Package Download/Install step and multiple devices30 ms003434
Scenario: Starting job with Package Uninstall and Bundle start steps and multiple device10 ms003232
Scenario: Starting job with Package Uninstall step and multiple device8 ms002727
Scenario: Starting job with invalid Bundle Start step and multiple devices18 ms002929
Scenario: Starting job with invalid Command Execution and Package Install steps10 ms003131
Scenario: Starting job with invalid Command Execution step and multiple devices13 ms002828
Scenario: Starting job with invalid Command Execution, invalid Package Install steps and multiple devices11 ms002929
Scenario: Starting job with invalid Configuration Put and Command Execution steps1 ms2+223+237-2532
Scenario: Starting job with invalid Configuration Put and Command Execution steps and multiple devices21 ms003131
Scenario: Starting job with two Bundle Start steps and multiple devices9 ms003232
Scenario: Starting job with valid Bundle Start step and multiple devices29 ms002929
Scenario: Starting job with valid Command Execution and Package Install steps22 ms003131
Scenario: Starting job with valid Command Execution step and multiple devices33 ms002626
Scenario: Starting job with valid Command Execution, valid Package Install steps and multiple devices58 ms002929
Scenario: Starting job with valid Configuration Put and Command Execution steps1 ms2+223+237-2532
Scenario: Starting job with valid Configuration Put and Command Execution steps and multiple devices18 ms003030
Scenario: Stealing link scenario4 ms002828
Scenario: Step definition factory sanity checks4 ms0022
Scenario: Step definition with a duplicate name4 ms0066
Scenario: Step definition with a null name4 ms0066
Scenario: Step definition with a null scope ID8 ms0066
Scenario: Step definition with an empty name4 ms0055
Scenario: Step factory sanity checks2 ms0022
Scenario: Step with a null scope ID8 ms001111
Scenario: Stop Jetty server for all scenarios2 ms0022
Scenario: Stop broker after all scenarios0.1 sec004646
Scenario: Stop datastore after all scenarios3.9 sec003030
Scenario: Stop event broker for all scenarios1.1 sec115052
Scenario: Stop job with multiple Asset Write and Package Install steps and one target12 ms003737
Scenario: Stop job with multiple Bundle Start and Package Install steps and one target9 ms003737
Scenario: Stop job with multiple Bundle Stop and Package Uninstall steps and one target13 ms003737
Scenario: Stop job with multiple Command Execution and Package Install steps and one target15 ms003434
Scenario: Stop job with multiple Configuration Put and Package Uninstall steps and one target10 ms003535
Scenario: Stop job with multiple targets and Asset Write and Package Install steps and one target24 ms003737
Scenario: Stop job with multiple targets and Bundle Start and Package Install steps20 ms003636
Scenario: Stop job with multiple targets and Bundle Stop and Package Uninstall steps8 ms003737
Scenario: Stop job with multiple targets and Command Execution and Package Install steps33 ms003434
Scenario: Stop job with multiple targets and Configuration Put and Package Uninstall steps9 ms003737
Scenario: Test LOOSE user coupling on single connection4 ms002828
Scenario: Test LOOSE user coupling with 3 connections7 ms003838
Scenario: Test STRICT user coupling on single connection9 ms002525
Scenario: Test STRICT user coupling with 3 connections and a reserved user7 ms006363
Scenario: Test STRICT user coupling with user change allowed on single connection4 ms003636
Scenario: Test account query2 ms0044
Scenario: Test the message store with server timestamp indexing12 ms002626
Scenario: Test the message store with timestamp indexing13 ms002626
Scenario: The Client ID is case sensitive2 ms0088
Scenario: To be defined6 ms001313
Scenario: Translating "CommandRequestMessage" to "KuraRequestMessage"20 ms0044
Scenario: Translating CommandRequestMessage to null5 ms0044
Scenario: Translating empty message to empty message6 ms0044
Scenario: Translating from "AssetRequestMessage" to "AssetResponseMessage"4 ms0044
Scenario: Translating invalid jms data message with valid channel, body and metrics into kura data message3 ms0055
Scenario: Translating invalid kura data message with valid channel, body and metrics into jms message3 ms0055
Scenario: Translating invalid kura data message with valid channel, body and metrics into mqtt message3 ms0055
Scenario: Translating kura data message with null channel, and payload without body and with metrics2 ms0055
Scenario: Translating kura data message with valid channel and with null payload3 ms0055
Scenario: Translating kura data message with valid channel and without body and metrics into jms message4 ms0055
Scenario: Translating kura data message with valid channel, and with null payload2 ms0055
Scenario: Translating kura data message with valid channel, body and metrics into jms message3 ms0055
Scenario: Translating kura data message with valid channel, metrics and without body into jms message2 ms0055
Scenario: Translating kura data message with valid channel, metrics and without body into mqtt message3 ms0055
Scenario: Translating null to KuraRequestMessage7 ms0044
Scenario: Translating of jms message with empty payload and invalid topic that contain only userName into kura data message3 ms0055
Scenario: Translating of jms message with empty payload and valid topic into kura data message3 ms0066
Scenario: Translating of jms message with invalid payload and valid topic into kura data message4 ms0066
Scenario: Translating of jms message with valid payload and valid topic into kura data message4 ms0066
Scenario: Translating of mqtt message with invalid payload and invalid topic into kura data message4 ms0055
Scenario: Translating of mqtt message with invalid payload and with null topic into kura data message3 ms0055
Scenario: Translation of kura data message with valid channel and without body and metrics into mqtt message4 ms0055
Scenario: Translation of kura data message with valid channel, body and metrics into mqtt message3 ms0055
Scenario: Translation of kura data message with valid channel, metrics and without body into mqtt message5 ms0055
Scenario: Translation of mqtt message with empty payload into kura data message4 ms0066
Scenario: Translation of mqtt message with invalid payload and invalid topic into kura response message3 ms0055
Scenario: Translation of mqtt message with invalid payload and valid topic into kura data message4 ms0066
Scenario: Translation of mqtt message with invalid payload and valid topic into kura response message3 ms0066
Scenario: Translation of mqtt message with valid payload and invalid topic into kura response message3 ms0055
Scenario: Translation of mqtt message with valid payload and valid topic into kura data message4 ms0066
Scenario: Translation of mqtt message with valid payload and valid topic into kura response message3 ms0066
Scenario: Try to add two different roles with same permissions13 ms002121
Scenario: Try to change an existing connection ID2 ms0077
Scenario: Try to create an access into entity with an invalid role id9 ms001212
Scenario: Try to delete a non existing device from the registry3 ms0044
Scenario: Try to find a device with an invalid client ID3 ms0033
Scenario: Try to find a device with an invalid registry ID3 ms0033
Scenario: Try to find users granted to "admin" role13 ms001212
Scenario: Try to find users that have assigned specific role12 ms001212
Scenario: Try to modify the connection client ID3 ms0077
Scenario: Try to update the device client ID3 ms0044
Scenario: Uncorrect Login While Lockout Policy Is Disabled8 ms001717
Scenario: Uncorrect Login While Lockout Policy Is Enabled7 ms001717
Scenario: Update a group entry in the database7 ms0099
Scenario: Update a group entry with a false ID5 ms001010
Scenario: Update a job XML definition2 ms001010
Scenario: Update a job description2 ms001010
Scenario: Update a job name5 ms001010
Scenario: Update a non existing device3 ms0055
Scenario: Update a nonexistent job4 ms001010
Scenario: Update a nonexistent step definition4 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 name6 ms0088
Scenario: Update job id of an existing execution item5 ms0088
Scenario: Update schedule which doesn't exist5 ms0055
Scenario: Update scheduler end date2 ms2169
Scenario: Update scheduler name7 ms0088
Scenario: Update scheduler start date20 ms0088
Scenario: Update the end time of an existing execution item3 ms0099
Scenario: Update trigger definition1 ms2158
Scenario: Update user5 ms0077
Scenario: Update user that doesn't exist4 ms0055
Scenario: User locking itself out by using out login attempts3 ms001616
Scenario: User locking itself out with failed attempts and not waiting to unlock3 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 failures7 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 ID2 ms0055
Scenario: Validate a device client based search with an empty client ID3 ms0055
Scenario: Validate a device client search with null scope3 ms0055
Scenario: Validate a device creator with a null client ID2 ms0066
Scenario: Validate a device creator with a null scope ID4 ms0066
Scenario: Validate a device query with a null Scope ID3 ms0044
Scenario: Validate a device search with a null device ID2 ms0066
Scenario: Validate a device search with a null scope ID3 ms0066
Scenario: Validate a null creator2 ms0055
Scenario: Validate a null device2 ms0055
Scenario: Validate a null device count3 ms0055
Scenario: Validate a null device query2 ms0055
Scenario: Validate a regular creator2 ms0044
Scenario: Validate a regular device client search2 ms0044
Scenario: Validate a regular device count3 ms0044
Scenario: Validate a regular device query3 ms0044
Scenario: Validate a regular device search2 ms0055
Scenario: Validate deleting a device with a null device ID2 ms0066
Scenario: Validate deleting a device with a null scope ID3 ms0066
Scenario: Waiting For Lock Duration Time To Pass6 ms001919
Scenario: Waiting For Reset After Login Counter To Pass5 ms001818
empty) scope0 ms0044