Test Result : (root)

20 failures (+2) , 159 skipped (+37)
16,514 tests (-6)
Took 20 sec.

All Failed Tests

Test NameDurationAge
 Scenario: Creating unique Access Group with special symbols in description.Scenario: Creating unique Access Group with special symbols in description9 ms28
 Scenario: Creating unique Access Group with special symbols in description.Then I find the group with name "groupName53"9 ms28
 Scenario: Delete items by date ranges.Scenario: Delete items by date ranges34 ms1
 Scenario: Delete items by date ranges.Then I store the messages from list "TestMessages" and remember the IDs as "StoredMessageIDs"32 ms1
 Scenario: Execute possible docker steps to show its usage.Given List images by name "kapua/kapua-broker:1.4.0-SNAPSHOT"3 ms5
 Scenario: Execute possible docker steps to show its usage.Scenario: Execute possible docker steps to show its usage4 ms5
 Scenario: Executing Job And Then Restarting Device.Scenario: Executing Job And Then Restarting Device4 ms5
 Scenario: Executing Job And Then Restarting Device.Then I find 4 device events3 ms5
 Scenario: Executing Job When Device Connected After The Specified Start Date And Time.And I confirm the executed job is finished6 ms5
 Scenario: Executing Job When Device Connected After The Specified Start Date And Time.Scenario: Executing Job When Device Connected After The Specified Start Date And Time7 ms5
 Scenario: Executing Job When Device Connected Before End Date And Time.And I confirm the executed job is finished5 ms5
 Scenario: Executing Job When Device Connected Before End Date And Time.Scenario: Executing Job When Device Connected Before End Date And Time6 ms5
 Scenario: List Endpoints Created From Sub-Account.And I create endpoint with schema "Schema1", domain "abc.com" and port 22222 ms5
 Scenario: List Endpoints Created From Sub-Account.Scenario: List Endpoints Created From Sub-Account4 ms5
 Scenario: List Endpoints From "kapua-sys" Account.Scenario: List Endpoints From "kapua-sys" Account5 ms5
 Scenario: List Endpoints From "kapua-sys" Account.Then I find 3 endpoints2 ms5
 Scenario: List Endpoints From Sub-Account Of Another Sub-Account.And I create endpoint with schema "Schema1", domain "abc.com" and port 22222 ms5
 Scenario: List Endpoints From Sub-Account Of Another Sub-Account.Scenario: List Endpoints From Sub-Account Of Another Sub-Account4 ms5
 Scenario: List Endpoints From Sub-account.And I create endpoint with schema "Schema1", domain "abc.com" and port 22221 ms5
 Scenario: List Endpoints From Sub-account.Scenario: List Endpoints From Sub-account3 ms5

All Tests

ClassDurationFail(diff)Skip(diff)Pass(diff)Total(diff)
Scenario: A fresh database must contain 1 default role in the root scope6 ms0044
Scenario: A newly created account must have some metadata4 ms0033
Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic10 ms0088
Scenario: Access info service sanity checks5 ms0044
Scenario: Access service comparison sanity checks5 ms0033
Scenario: Account based ClientInfo data check30 ms002424
Scenario: Account exactly on its expiration date9 ms001414
Scenario: Account name must not be mutable3 ms0066
Scenario: Account past its expiration date19 ms001414
Scenario: Account wide metrics check46 ms002828
Scenario: Account with future expiration date15 ms001313
Scenario: Account with no expiration date13 ms001313
Scenario: Add Access Info domain permissions to new user19 ms002626
Scenario: Add Account permissions to the role in child account13 ms002828
Scenario: Add Credential domain permissions to new user14 ms001818
Scenario: Add Datastore domain permissions to new user0.41 sec001919
Scenario: Add Device Connection domain permissions to kapua-sys user16 ms001111
Scenario: Add Device Connection domain permissions to new user11 ms002323
Scenario: Add Device Event domain permissions to new user19 ms001616
Scenario: Add Device domain permissions to new user11 ms001717
Scenario: Add Domain domain permissions to kapua-sys user19 ms001717
Scenario: Add Domain domain permissions to new user13 ms003232
Scenario: Add Endpoint Permission To The User16 ms003030
Scenario: Add Endpoint_info permissions to the role in child account10 ms003030
Scenario: Add Group domain permissions to new user16 ms001717
Scenario: Add Group permissions to the role in child account12 ms002626
Scenario: Add Job domain permissions to new user12 ms001919
Scenario: Add Role domain permissions to new user13 ms001717
Scenario: Add Role permissions to the role in child account17 ms002626
Scenario: Add Scheduler Permissions With Job Permissions20 ms003131
Scenario: Add Scheduler Permissions Without Job Permissions14 ms002121
Scenario: Add Scheduler permissions to the role in child account21 ms003636
Scenario: Add Tag domain permissions to new user39 ms001515
Scenario: Add Tag permissions to the role in child account8 ms002626
Scenario: Add User domain permissions to new user10 ms002020
Scenario: Add account permissions to the role14 ms001919
Scenario: Add admin role to the user29 ms004444
Scenario: Add and delete Account permissions from the "admin" role11 ms001414
Scenario: Add and delete Device permissions from the "admin" role9 ms001414
Scenario: Add and delete Endpoint_info permissions from the "admin" role16 ms001414
Scenario: Add and delete Group permissions from the "admin" role13 ms001414
Scenario: Add and delete Job permissions from the "admin" role12 ms001414
Scenario: Add and delete Role permissions from the "admin" role11 ms001414
Scenario: Add and delete User permissions from the "admin" role14 ms001515
Scenario: Add datastore permissions to the role19 ms002727
Scenario: Add deleted role again16 ms001010
Scenario: Add device event permissions to the role14 ms003232
Scenario: Add device permissions to the role13 ms001919
Scenario: Add device permissions to the role in child account31 ms002626
Scenario: Add domain, user and access_info permissions to the role16 ms002323
Scenario: Add endpoint_info permissions to the role11 ms003131
Scenario: Add group permissions to the role21 ms001818
Scenario: Add job permissions to the role12 ms001919
Scenario: Add job permissions to the role in child account15 ms002626
Scenario: Add role permissions to the role18 ms001919
Scenario: Add same permission twice to the same role18 ms001414
Scenario: Add same role to user twice10 ms001313
Scenario: Add scheduler permissions to the role12 ms003131
Scenario: Add tag permissions to the role19 ms001818
Scenario: Add user permissions to the role17 ms001919
Scenario: Add user permissions to the role in child account12 ms002626
Scenario: Adding "Cron Job" Schedule With All Valid Parameters9 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 Format7 ms001111
Scenario: Adding "Cron Job" Schedule With End Date Only6 ms001010
Scenario: Adding "Cron Job" Schedule With End Time before Start time7 ms001212
Scenario: Adding "Cron Job" Schedule With Non-Unique End Date Parameter21 ms001616
Scenario: Adding "Cron Job" Schedule With Non-Unique Start Date Parameter6 ms001515
Scenario: Adding "Cron Job" Schedule With Start Date Only7 ms001111
Scenario: Adding "Cron Job" Schedule With the same Start and End time11 ms001212
Scenario: Adding "Cron Job" Schedule Without The Start Date Parameter5 ms001010
Scenario: Adding "Device Connect" Schedule With All Valid Parameters8 ms0088
Scenario: Adding "Device Connect" Schedule With End Date Only7 ms001010
Scenario: Adding "Device Connect" Schedule With End Time before Start time6 ms001111
Scenario: Adding "Device Connect" Schedule With Max Length Name13 ms0088
Scenario: Adding "Device Connect" Schedule With Min Length Name7 ms0088
Scenario: Adding "Device Connect" Schedule With Name Only9 ms0099
Scenario: Adding "Device Connect" Schedule With Non-Unique End Date Parameter8 ms001313
Scenario: Adding "Device Connect" Schedule With Non-Unique Name8 ms001313
Scenario: Adding "Device Connect" Schedule With Non-Unique Start Date Parameter9 ms001111
Scenario: Adding "Device Connect" Schedule With Start Date Only8 ms001010
Scenario: Adding "Device Connect" Schedule With the same Start and End time7 ms001111
Scenario: Adding "Device Connect" Schedule Without Name10 ms001010
Scenario: Adding "Device Connect" Schedule Without The Start Date Parameter9 ms0099
Scenario: Adding "Empty" Tag To Device4 ms0055
Scenario: Adding "Interval Job" Schedule With All Valid Parameters9 ms001010
Scenario: Adding "Interval Job" Schedule With End Date Only7 ms001010
Scenario: Adding "Interval Job" Schedule With End Time before Start time9 ms001212
Scenario: Adding "Interval Job" Schedule With Max Length Name6 ms001010
Scenario: Adding "Interval Job" Schedule With Min Length Name7 ms001010
Scenario: Adding "Interval Job" Schedule With Name Only10 ms001010
Scenario: Adding "Interval Job" Schedule With Non-Unique End Date Parameter9 ms001616
Scenario: Adding "Interval Job" Schedule With Non-Unique Name4 ms001515
Scenario: Adding "Interval Job" Schedule With Non-Unique Start Date Parameter6 ms001515
Scenario: Adding "Interval Job" Schedule With Null Interval Number7 ms001212
Scenario: Adding "Interval Job" Schedule With Start Date Only6 ms001111
Scenario: Adding "Interval Job" Schedule With the same Start and End time9 ms001212
Scenario: Adding "Interval Job" Schedule Without Interval Number5 ms001111
Scenario: Adding "Interval Job" Schedule Without The Start Date Parameter6 ms0099
Scenario: Adding "Interval Job" Schedule Without a Name9 ms001111
Scenario: Adding "admin" role to a user in a child account11 ms001414
Scenario: Adding "admin" role to multiple users10 ms001818
Scenario: Adding "admin" role twice10 ms001313
Scenario: Adding Account:Delete permission to user in same scope19 ms002525
Scenario: Adding Account:Delete permission to user in sub-account scope47 ms003030
Scenario: Adding Account:Read and Account:Delete permissions to user in same scope8 ms002121
Scenario: Adding Account:Read and Account:Write permissions to user in same scope18 ms001919
Scenario: Adding Account:Read permission to user in same scope19 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 scope11 ms002323
Scenario: Adding Account:Write permission to user in same scope47 ms002525
Scenario: Adding Account:Write permission to user in sub-account scope8 ms003131
Scenario: Adding Multiple Permissions To User15 ms002020
Scenario: Adding One Permission To User16 ms001111
Scenario: Adding Permissions To Child User12 ms001818
Scenario: Adding Permissions To Parallel User9 ms001818
Scenario: Adding Previously Deleted Permission18 ms002828
Scenario: Adding Previously Deleted Tag From Device Again4 ms001111
Scenario: Adding Regular Device to a Group With Description5 ms001010
Scenario: Adding Regular Device to a Group Without a Description6 ms001212
Scenario: Adding Regular Group Without Description to Device13 ms001010
Scenario: Adding Regular Tag Without Description To Device5 ms0066
Scenario: Adding Same Regular Group Without Description to Device13 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 Device4 ms0066
Scenario: Adding Tag With Special Symbols Without Description To Device11 ms0066
Scenario: Adding all Account permissions to user in same scope15 ms001717
Scenario: Adding all Account permissions to user in sub-account scope10 ms002424
Scenario: Adding existing roles to user19 ms001515
Scenario: Adding role from child account to user in new child account12 ms001515
Scenario: Adding role to multiple users in child account15 ms001818
Scenario: Adding same role twice to user in child account16 ms001515
Scenario: Adding the same role to user twice in child account10 ms001313
Scenario: All device parameters must match the device creator3 ms0033
Scenario: Assign 100 Devices to One Group21 ms001111
Scenario: B1 Broker publish to CTRL_ACC_REPLY31 ms0099
Scenario: B10 Broker create sub-topic on ACL_DATA_ACC is not allowed24 ms0099
Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed5 ms0088
Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI20 ms0099
Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed15 ms0099
Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed8 ms0088
Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY29 ms0099
Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY21 ms0099
Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account11 ms0099
Scenario: B5 Broker publish to CTRL_ACC is not allowed15 ms0099
Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed9 ms0099
Scenario: B7 Broker subscribe on CTRL_ACC is not allowed7 ms0088
Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI11 ms0099
Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed18 ms0099
Scenario: Basic Device Event queries8 ms001010
Scenario: Birth and applications event handling9 ms001212
Scenario: Birth and death message handling5 ms001212
Scenario: Birth and missing event handling6 ms001212
Scenario: Birth message handling from a new device9 ms001313
Scenario: Birth message handling from an existing device7 ms001212
Scenario: Both the parent and child accounts do not expire7 ms001111
Scenario: Both the parent and child accounts have the same expiration date12 ms001111
Scenario: Captured date based ClientInfo data check32 ms003030
Scenario: Case sensitiveness of named device searches3 ms0044
Scenario: Change an existing step name14 ms0011-111-1
Scenario: Change role name so it is too short3 ms0066
Scenario: Change the account parent path5 ms0055
Scenario: Changing Client ID6 ms0099
Scenario: Changing Description On Group With Long Description5 ms0077
Scenario: Changing Description On Group With Long Name8 ms0077
Scenario: Changing Description On Group With Numbers In Name6 ms001010
Scenario: Changing Description On Group With Permitted Symbols7 ms0077
Scenario: Changing Description On Group With Short Description5 ms0077
Scenario: Changing Description On Group With Short Name9 ms0077
Scenario: Changing Description On Tag With Long Description6 ms0044
Scenario: Changing Description On Tag With Long Name3 ms0055
Scenario: Changing Description On Tag With Numbers In Name5 ms0066
Scenario: Changing Description On Tag With Permitted Symbols In Name4 ms0044
Scenario: Changing Description On Tag With Short Description3 ms0044
Scenario: Changing Description On Tag With Short Name4 ms0044
Scenario: Changing Device Status To Disabled13 ms0099
Scenario: Changing Device Status To Enabled9 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 Description14 ms0088
Scenario: Changing Group's Name To Contain Permitted Symbols In Name Without Changing Description5 ms0077
Scenario: Changing Group's Name To Non-Unique One9 ms0099
Scenario: Changing Group's Name To Short One Without Changing Description15 ms0077
Scenario: Changing Group's Name To Unique One12 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 Description6 ms0088
Scenario: Changing Group's Name To a Too Short One Without Changing Description6 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 Description4 ms0055
Scenario: Changing Tag's Name To Non-Unique One5 ms0066
Scenario: Changing Tag's Name To Short One Without Description6 ms0077
Scenario: Changing Tag's Name To Unique One4 ms0077
Scenario: Changing Tag's Name To a Long One Without Description3 ms0077
Scenario: Changing Tag's Name To a Too Long One Without Description3 ms0055
Scenario: Changing Tag's Name To a Too Short One Without Description3 ms0055
Scenario: Changing description of a nonexisting role4 ms0077
Scenario: Changing job description to non-unique one6 ms0077
Scenario: Changing job description to the long one7 ms0066
Scenario: Changing job description to unique one6 ms0066
Scenario: Changing job description to very short one6 ms0077
Scenario: Changing job name to a long one without description6 ms0077
Scenario: Changing job name to a too long one without description7 ms0055
Scenario: Changing job name to a too short one without description5 ms0066
Scenario: Changing job name to contain invalid symbols in name without description6 ms0044
Scenario: Changing job name to contain permitted symbols in name without description8 ms0055
Scenario: Changing job name to non-unique one5 ms0088
Scenario: Changing job name to short one without description8 ms0077
Scenario: Changing job name to unique one9 ms0099
Scenario: Changing name of a nonexisting role6 ms0077
Scenario: Changing role description to a valid one3 ms0066
Scenario: Changing role name so it is too long5 ms0066
Scenario: Changing role name to contain special character3 ms0044
Scenario: Changing role name to null3 ms0066
Scenario: Changing role's name to a valid one5 ms0066
Scenario: Channel info queries based on datastore channel filters46 ms005050
Scenario: ChannelInfo client ID and topic data based on the client id39 ms002828
Scenario: ChannelInfo client ID based on the account id31 ms002626
Scenario: ChannelInfo last published date53 ms003030
Scenario: ChannelInfo topic data based on the account id45 ms002626
Scenario: Check account properties5 ms0044
Scenario: Check the Device Connection Domain data seetting3 ms0022
Scenario: Check the database cache coherency35 ms003030
Scenario: Check the mapping for message semantic topics35 ms003030
Scenario: Check the message store36 ms002020
Scenario: Check the sanity of the Device Connection Domain data initialization3 ms0022
Scenario: Child account expires after parent5 ms0099
Scenario: Child account expires before parent7 ms001111
Scenario: Child account has null expiration date11 ms0099
Scenario: Client Id based ClientInfo data check24 ms002828
Scenario: Compare domain entries7 ms0033
Scenario: Connect to the system and publish some data0.16 sec002222
Scenario: Connection Service factory sanity checks2 ms0022
Scenario: Count access info entities in a specific scope11 ms002424
Scenario: Count access role entities by scope17 ms003939
Scenario: Count connections in empty scope4 ms0044
Scenario: Count connections in scope4 ms0055
Scenario: Count devices with a specific BIOS version3 ms0066
Scenario: Count domains in a blank database8 ms0044
Scenario: Count domains in the database6 ms0077
Scenario: Count events in empty scope6 ms0066
Scenario: Count groups10 ms001414
Scenario: Count groups in a blank database8 ms0055
Scenario: Count job items3 ms0077
Scenario: Count job items in wrong - empty - scope4 ms0088
Scenario: Count role permissions in specific scopes5 ms001818
Scenario: Count roles in specific scopes11 ms001515
Scenario: Count step definition items5 ms0044
Scenario: Count step definitions in wrong (empty) scope7 ms0011
Scenario: Count steps in the database3 ms0014-114-1
Scenario: Count user8 ms0066
Scenario: Counting created roles items in the DB4 ms0055
Scenario: Create a regular event34 ms0088
Scenario: Create a single device with an empty string for clientID4 ms0044
Scenario: Create a single device with null clientID value5 ms0044
Scenario: Create a valid job entry60 ms0066
Scenario: Create an event with a null scope ID7 ms0077
Scenario: Create and count several execution items for a job3 ms001111
Scenario: Create index with specific prefix20 ms001212
Scenario: Create multiple users7 ms0055
Scenario: Create regular access permissions8 ms002020
Scenario: Create same user in different accounts19 ms001515
Scenario: Create scheduler with correct end date9 ms0088
Scenario: Create scheduler with empty schedule name13 ms0088
Scenario: Create scheduler with end date before start date8 ms0099
Scenario: Create scheduler with invalid Retry Interval property10 ms0099
Scenario: Create scheduler with invalid cron job trigger property8 ms0099
Scenario: Create scheduler with invalid schedule name25 ms0088
Scenario: Create scheduler with short schedule name15 ms0088
Scenario: Create scheduler with too long schedule name13 ms0088
Scenario: Create scheduler with valid Retry Interval property6 ms0077
Scenario: Create scheduler with valid cron job trigger property10 ms0077
Scenario: Create scheduler with valid schedule name40 ms0066
Scenario: Create scheduler without Cron Job Trigger property6 ms0099
Scenario: Create scheduler without Retry Interval property8 ms0099
Scenario: Create scheduler without start date5 ms0077
Scenario: Create some regular role permissions5 ms0099
Scenario: Create user that already exist6 ms0077
Scenario: Create user that has more than DB allowed length10 ms0055
Scenario: Create user with short name8 ms0055
Scenario: Create user with special characters in his name7 ms0055
Scenario: Create with permissions5 ms001414
Scenario: Create with permissions and a role9 ms001717
Scenario: Create with permissions and a role in the wrong scope7 ms001515
Scenario: Creating 100 Sub-accounts While InfiniteChildAccounts Is Set To True7 ms0077
Scenario: Creating A Device With Disabled Status9 ms0077
Scenario: Creating A Device With Enabled Status15 ms0077
Scenario: Creating A Device With Long Display Name12 ms0077
Scenario: Creating A Device With Long Name12 ms0077
Scenario: Creating A Device With Name Containing Invalid Symbols12 ms0088
Scenario: Creating A Device With Name Containing Permitted Symbols13 ms0077
Scenario: Creating A Device With No Name8 ms0088
Scenario: Creating A Device With Non-unique Display Name6 ms0077
Scenario: Creating A Device With Non-unique Name7 ms001010
Scenario: Creating A Device With Short Display Name6 ms0077
Scenario: Creating A Device With Short Name10 ms0077
Scenario: Creating A Device With Too Long Display Name7 ms0088
Scenario: Creating A Device With Too Long Name6 ms0088
Scenario: Creating A Device With Unique Name7 ms0099
Scenario: Creating A Valid Account13 ms0055
Scenario: Creating An Account With Long Name10 ms0055
Scenario: Creating An Account With Long Organization Name6 ms0055
Scenario: Creating An Account With Non-unique Name11 ms0088
Scenario: Creating An Account With Numbers And Valid Symbols In Name11 ms0055
Scenario: Creating An Account With Short Name12 ms0055
Scenario: Creating An Account With Short Organization Name8 ms0055
Scenario: Creating An Account With Special Symbols In Organization Name7 ms0055
Scenario: Creating An Account With Too Long Organization Name6 ms0066
Scenario: Creating An Account With Unique Name7 ms0077
Scenario: Creating An Account With Wrong TLD Format In Email8 ms001010
Scenario: Creating An Account Without Email8 ms0066
Scenario: Creating An Account Without Name12 ms0066
Scenario: Creating An Account Without Ogranization Name7 ms0066
Scenario: Creating And Account Without "@" In Email9 ms0066
Scenario: Creating Devices And Than Setting Device Service So It Does Not Allow Devices16 ms001212
Scenario: Creating Devices And Then Changing Device Service Values13 ms001010
Scenario: Creating Devices Under Account That Allows Infinite Child Devices11 ms001010
Scenario: Creating Devices Under Account That Does Not Allow Devices7 ms0099
Scenario: Creating Devices Under Account That Has Limited Child Devices8 ms001313
Scenario: Creating Endpoint Non-Unique "Domain Name"5 ms0088
Scenario: Creating Endpoint Non-Unique "Port"7 ms0088
Scenario: Creating Endpoint Non-Unique "Schema"4 ms0099
Scenario: Creating Endpoint With "Domain Name" Only3 ms0066
Scenario: Creating Endpoint With "Port" Only7 ms0066
Scenario: Creating Endpoint With "Schema" Only4 ms0066
Scenario: Creating Endpoint With Disabled Secure Field11 ms0066
Scenario: Creating Endpoint With Enabled Secure Field6 ms0066
Scenario: Creating Endpoint With Invalid "Domain Name"7 ms0066
Scenario: Creating Endpoint With Invalid "Schema" containing symbols4 ms0066
Scenario: Creating Endpoint With Long "Domain Name"15 ms0055
Scenario: Creating Endpoint With Max Length "Port"4 ms0055
Scenario: Creating Endpoint With NULL parameters3 ms0066
Scenario: Creating Endpoint With Schema Containing "http://"13 ms0066
Scenario: Creating Endpoint With Schema Containing "https://"8 ms0066
Scenario: Creating Endpoint With Short "Domain Name"5 ms0066
Scenario: Creating Endpoint With Short "Schema"6 ms0066
Scenario: Creating Endpoint With Small Number "Port"11 ms0066
Scenario: Creating Endpoint With Too Big "Port"5 ms0066
Scenario: Creating Endpoint With Too Long "Domain Name"5 ms0066
Scenario: Creating Endpoint With Too Long "Schema"5 ms0066
Scenario: Creating Endpoint Without "Domain Name"8 ms0066
Scenario: Creating Endpoint Without "Port"4 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 numbers11 ms0066
Scenario: Creating Group Invalid Symbols In Name Without Description4 ms0077
Scenario: Creating Group With Invalid Symbols In Name With Valid Description6 ms0077
Scenario: Creating Group With Long Name With Valid Description6 ms0066
Scenario: Creating Group With Long Name Without Description6 ms0066
Scenario: Creating Group With Numbers In Name With Valid Description6 ms0088
Scenario: Creating Group With Permitted Symbols And Numbers In Name Without Description7 ms0066
Scenario: Creating Group With Permitted Symbols In Name With Valid Description5 ms0066
Scenario: Creating Group With Short Name With Valid Description7 ms0066
Scenario: Creating Group With Short Name Without Description13 ms0066
Scenario: Creating Group With Too Long Name With Valid Description6 ms0077
Scenario: Creating Group With Too Long Name Without Description6 ms0077
Scenario: Creating Group With Too Short Name With Valid Description5 ms0077
Scenario: Creating Group With Too Short Name Without Description5 ms0077
Scenario: Creating Group Without a Name And With Valid Description5 ms0077
Scenario: Creating Group Without a Name And Without Description10 ms0077
Scenario: Creating Groups And Than Setting Group Service So It Does Not Allow Groups8 ms001111
Scenario: Creating Groups And Then Changing InfiniteChildGroups To False And Set MaxNumberChildGroups10 ms001010
Scenario: Creating Groups Under Account That Allows Infinite Child Groups7 ms0099
Scenario: Creating Groups Under Account That Does Not Allow Groups8 ms0099
Scenario: Creating Groups Under Account That Has Limited Child Groups7 ms001212
Scenario: Creating Jobs And Than Setting Job Service So It Does Not Allow Jobs8 ms001212
Scenario: Creating Jobs And Then Changing Job Service Values8 ms001010
Scenario: Creating Jobs Under Account That Allows Infinite Child Devices8 ms001010
Scenario: Creating Jobs Under Account That Does Not Allow Jobs10 ms0099
Scenario: Creating Jobs Under Account That Has Limited Child Jobs12 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 Description14 ms0088
Scenario: Creating Non-unique Tag Without Description11 ms0044
Scenario: Creating Roles And Than Setting Role Service So It Does Not Allow Roles5 ms001111
Scenario: Creating Roles And Then Changing Role Service Values6 ms001010
Scenario: Creating Roles Under Account That Allows Infinite Child Roles7 ms001010
Scenario: Creating Roles Under Account That Does Not Allow Roles7 ms0099
Scenario: Creating Roles Under Account That Has Limited Child Roles7 ms001212
Scenario: Creating Sub-accounts When InfiniteChildAccoounts Is Set To False And maxNumberChildAccounts Is Set8 ms001313
Scenario: Creating Sub-accounts When InfiniteChildAccoounts Is Set To True And maxNumberChildAccounts Is Set5 ms001414
Scenario: Creating Sub-accounts When InfiniteChildAccounts Is Set To False6 ms0099
Scenario: Creating Sub-accounts when InfiniteChildAccounts Is Set To True14 ms001212
Scenario: Creating Tag With Invalid Symbols In Name With Valid Description4 ms0044
Scenario: Creating Tag With Invalid Symbols In Name Without Description7 ms0044
Scenario: Creating Tag With Long Name With Valid Description5 ms0044
Scenario: Creating Tag With Long Name Without Description9 ms0044
Scenario: Creating Tag With Numbers In Name With Valid Description3 ms0044
Scenario: Creating Tag With Numbers In Name Without Description8 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 Description4 ms0044
Scenario: Creating Tag With Short Name Without Description7 ms0044
Scenario: Creating Tag With Too Long Name With Valid Description4 ms0044
Scenario: Creating Tag With Too Long Name Without Description10 ms0044
Scenario: Creating Tag With Too Short Name With Valid Description4 ms0044
Scenario: Creating Tag With Too Short Name Without Description6 ms0044
Scenario: Creating Tag Without a Name And With Valid Description6 ms0044
Scenario: Creating Tag Without a Name And Without Description3 ms0044
Scenario: Creating Tags And Than Setting Tag Service So It Does Not Allow Tags11 ms001111
Scenario: Creating Tags And Then Changing Tag Service Values7 ms001010
Scenario: Creating Tags Under Account That Allows Infinite Child Devices8 ms001010
Scenario: Creating Tags Under Account That Does Not Allow Tags15 ms0099
Scenario: Creating Tags Under Account That Has Limited Child Tags6 ms001212
Scenario: Creating Unique Group With Long Description6 ms0066
Scenario: Creating Unique Group With Non-unique Description5 ms0077
Scenario: Creating Unique Group With Short Description6 ms0066
Scenario: Creating Unique Group With Unique Description13 ms0066
Scenario: Creating Unique Group Without Description9 ms0066
Scenario: Creating Unique Tag With Long Description5 ms0044
Scenario: Creating Unique Tag With Non-unique Description5 ms0055
Scenario: Creating Unique Tag With Short Description4 ms0044
Scenario: Creating Unique Tag With Unique Description8 ms0044
Scenario: Creating Unique Tag Without Description22 ms0044
Scenario: Creating Users And Than Setting User Service So It Does Not Allow Users7 ms001111
Scenario: Creating Users And Then Changing User Service Values8 ms001010
Scenario: Creating Users Under Account That Allows Infinite Child Users11 ms001010
Scenario: Creating Users Under Account That Does Not Allow Users8 ms0099
Scenario: Creating Users Under Account That Has Limited Child Users6 ms001212
Scenario: Creating Valid Endpoint7 ms0066
Scenario: Creating a Access Group with invalid special symbols in name0 ms0044
Scenario: Creating a Device With Permitted Symbols in its Display Name15 ms0077
Scenario: Creating a Device With Unique Display Name11 ms0088
Scenario: Creating a job with name only11 ms0066
Scenario: Creating a job with null name15 ms0055
Scenario: Creating a job without name with valid description6 ms0055
Scenario: Creating a new PASSWORD Credential meeting a custom length requirement6 ms0044
Scenario: Creating a new PASSWORD Credential meeting the standard length requirement18 ms0033
Scenario: Creating a new PASSWORD Credential not meeting a custom length requirement7 ms0055
Scenario: Creating a new PASSWORD Credential not meeting the standard length requirement11 ms0044
Scenario: Creating a role name with allowed symbols in its name6 ms0055
Scenario: Creating a role with 255 characters long description3 ms0055
Scenario: Creating a role with a name and description that contain digits only4 ms0055
Scenario: Creating a role with forbidden symbols in its name0 ms0044
Scenario: Creating a role with name only2 ms0055
Scenario: Creating a role with null name2 ms0055
Scenario: Creating a role with regular name and very short description" as description cannot be too short, as even one character is enough2 ms0055
Scenario: Creating a role with special characters in the description4 ms0044
Scenario: Creating a role with the name that contains digits2 ms0055
Scenario: Creating a role with too long name2 ms0055
Scenario: Creating a role with too short name2 ms0055
Scenario: Creating a role with valid name and with too long description4 ms0033
Scenario: Creating a role wtih 255 characters long name4 ms0055
Scenario: Creating a single device with case sensitive clientID6 ms0055
Scenario: Creating a single device with clientID that contains 255 characters6 ms0055
Scenario: Creating a single device with clientID that contains 256 characters4 ms0044
Scenario: Creating a single device with clientID that contains invalid character3 ms0044
Scenario: Creating a single device with clientID that contains invalid characters4 ms0044
Scenario: Creating a single device with spaces in clientID5 ms0055
Scenario: Creating a single device with valid clientID6 ms0055
Scenario: Creating a valid Access Group with numbers in name4 ms0055
Scenario: Creating a valid Access Group with only numbers in name4 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 role4 ms0055
Scenario: Creating an Access Group with empty name5 ms0044
Scenario: Creating an Access Group with long name4 ms0055
Scenario: Creating an Access Group with short name4 ms0055
Scenario: Creating an Access Group with too long name7 ms0044
Scenario: Creating an Access Group with too short name5 ms0044
Scenario: Creating an Access Group without name and with description4 ms0044
Scenario: Creating and Deleting Endpoint Two Times29 ms002525
Scenario: Creating index with regular user24 ms002525
Scenario: Creating job with invalid symbols in name without description8 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 description6 ms0066
Scenario: Creating job with numbers in name without description7 ms0066
Scenario: Creating job with permitted symbols in name without description10 ms0033
Scenario: Creating job with short name and valid job description5 ms0066
Scenario: Creating job with short name without description21 ms0066
Scenario: Creating job with too long name and valid description5 ms0055
Scenario: Creating job with too long name without description6 ms0055
Scenario: Creating job with too short name and valid description5 ms0055
Scenario: Creating job with too short name without description11 ms0055
Scenario: Creating job without name and without description11 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 Tag8 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 description5 ms0077
Scenario: Creating two device with the same clientID3 ms0055
Scenario: Creating two indexes with daily index12 ms001717
Scenario: Creating two indexes with hourly index21 ms001717
Scenario: Creating two indexes with weekly index18 ms001717
Scenario: Creating two roles with the same description3 ms0066
Scenario: Creating two roles with the same name3 ms0077
Scenario: Creating unique Access Group with long description6 ms0055
Scenario: Creating unique Access Group with non-unique description6 ms0066
Scenario: Creating unique Access Group with numbers in description6 ms0055
Scenario: Creating unique Access Group with only numbers in description5 ms0055
Scenario: Creating unique Access Group with short description4 ms0055
Scenario: Creating unique Access Group with special symbols in description18 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 description6 ms001010
Scenario: Creating unique job with short description5 ms0066
Scenario: Creating user42 ms0055
Scenario: Creation of access role with neither acess info and role entities4 ms001212
Scenario: Creation of access role without an acess info entity5 ms001212
Scenario: D1 Device publish to CTRL_ACC_REPLY8 ms0099
Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI12 ms0099
Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed15 ms0099
Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed11 ms0077
Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY16 ms0099
Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY12 ms0099
Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account13 ms0099
Scenario: D5 Device subscribe - publish - admin on CTRL_ACC10 ms0099
Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI17 ms0099
Scenario: D7 Device publish to ACL_DATA_ACC is not allowed9 ms0099
Scenario: D8 Device create sub-topic on ACL_DATA_ACC is not allowed7 ms0099
Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed8 ms0088
Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed17 ms0099
Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI12 ms0099
Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed13 ms0099
Scenario: DM13 Data manage subscribe on ACL_CTRL_ACC_NOTIFY is not allowed10 ms0088
Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY19 ms0099
Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY30 ms0099
Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account7 ms0099
Scenario: DM5 Data manage publish to CTRL_ACC is not allowed23 ms0099
Scenario: DM6 Data manage create sub-topic on CTRL_ACC is not allowed11 ms0099
Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed7 ms0088
Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI15 ms0099
Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC7 ms0099
Scenario: DV1 Data view publish to CTRL_ACC_REPLY13 ms0099
Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed21 ms0099
Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed10 ms001010
Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed19 ms0099
Scenario: DV13 Data view create sub-topic on ACL_CTRL_ACC_CLI is not allowed6 ms0099
Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed8 ms0099
Scenario: DV17 Data view subscribe on ACL_CTRL_ACC_NOTIFY is not allowed5 ms0088
Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY19 ms0099
Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY9 ms0099
Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account7 ms0099
Scenario: DV5 Data view publish to CTRL_ACC is not allowed6 ms0099
Scenario: DV6 Data view create sub-topic on CTRL_ACC is not allowed10 ms0099
Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed4 ms0088
Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI8 ms0099
Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed15 ms0099
Scenario: Decreasing MaxNumberChildAccounts When Sub-accounts Are Already Created14 ms001515
Scenario: Delete Kapua system user5 ms0055
Scenario: Delete a access info entity with permissions and roles7 ms001717
Scenario: Delete a connection from the database3 ms0088
Scenario: Delete a group from the database15 ms001010
Scenario: Delete a group from the database - Unknown group ID15 ms0066
Scenario: Delete a job3 ms001111
Scenario: Delete a job execution item11 ms0088
Scenario: Delete a job execution item twice13 ms0099
Scenario: Delete a job twice3 ms001010
Scenario: Delete a non existent event6 ms0077
Scenario: Delete a non existing connection3 ms0077
Scenario: Delete a non existing permission entity14 ms001616
Scenario: Delete a non existing role entry4 ms001111
Scenario: Delete a non-existing step3 ms0012-112-1
Scenario: Delete a nonexistent domain7 ms0055
Scenario: Delete a step definition6 ms0088
Scenario: Delete a step definition twice9 ms0077
Scenario: Delete access role from user15 ms001212
Scenario: Delete an access info entity twice5 ms001111
Scenario: Delete an access info entity using the wrong scope ID5 ms001111
Scenario: Delete an existing access info entity6 ms001212
Scenario: Delete an existing access permission entity5 ms001515
Scenario: Delete an existing access role entry6 ms002222
Scenario: Delete an existing account5 ms0055
Scenario: Delete an existing device from the registry3 ms0044
Scenario: Delete an existing event6 ms0099
Scenario: Delete an existing role5 ms001010
Scenario: Delete an existing role twice15 ms001616
Scenario: Delete an existing step8 ms0011-111-1
Scenario: Delete items based on query results54 ms008484
Scenario: Delete items by date ranges1 sec2+237+3793-39132
Scenario: Delete items by the datastore ID56 ms006666
Scenario: Delete middle child expiration16 ms001515
Scenario: Delete nonexisting account4 ms0044
Scenario: Delete nonexisting role permission4 ms001313
Scenario: Delete parent expiration14 ms001414
Scenario: Delete permissions from role19 ms001818
Scenario: Delete role permissions6 ms001010
Scenario: Delete scheduler6 ms0088
Scenario: Delete scheduler which doesn't exist7 ms0055
Scenario: Delete the Kapua system account6 ms0055
Scenario: Delete the last created domain entry6 ms0088
Scenario: Delete user6 ms0066
Scenario: Delete user that doesn't exist4 ms0055
Scenario: Deleting "Cron Schedule" Triggering5 ms001313
Scenario: Deleting "Device Schedule" Triggering7 ms001111
Scenario: Deleting "Interval Schedule" Triggering8 ms001313
Scenario: Deleting Device With Disabled Status8 ms001010
Scenario: Deleting Device With Enabled Status10 ms001010
Scenario: Deleting Endpoint Domain Name And Leaving it Empty7 ms0088
Scenario: Deleting Endpoint Which Does Not Exist12 ms0066
Scenario: Deleting Existing Group9 ms0088
Scenario: Deleting Existing Group And Creating It Again With Same Name6 ms001212
Scenario: Deleting Existing Tag And Creating It Again With Same Name3 ms0077
Scenario: Deleting Group's Name And Leaving It Empty Without Changing Description6 ms0088
Scenario: Deleting Non-Existent Tag3 ms0077
Scenario: Deleting Tag From Device4 ms0088
Scenario: Deleting Tag's Name And Leaving It Empty Without Description6 ms0055
Scenario: Deleting Unexisitng Group13 ms001111
Scenario: Deleting a Permission13 ms002121
Scenario: Deleting a non-existing Access Group3 ms0066
Scenario: Deleting a role twice8 ms0077
Scenario: Deleting admin role12 ms0077
Scenario: Deleting an existing Access Group3 ms0055
Scenario: Deleting an existing Access Group and creating it again with the same name4 ms0077
Scenario: Deleting an existing role3 ms0066
Scenario: Deleting default permissions from admin role13 ms001212
Scenario: Deleting existing tag4 ms0099
Scenario: Deleting role after adding it to user15 ms001414
Scenario: Deleting role after it has been added to user in child account15 ms001616
Scenario: Deleting user in account that is higher in hierarchy19 ms002323
Scenario: Deleting user in account that is lower in hierarchy28 ms002424
Scenario: Device connection update4 ms0077
Scenario: Device factory sanity checks2 ms0022
Scenario: Device queries6 ms001010
Scenario: Device query - find by BIOS version5 ms0077
Scenario: Domain entry query10 ms0055
Scenario: Domain with null actions8 ms0055
Scenario: Domain with null name6 ms0055
Scenario: Domains with duplicate names5 ms0088
Scenario: Duplicate group name in root scope15 ms001010
Scenario: Duplicate role names7 ms0077
Scenario: Editing Access Group description to description with numbers3 ms0055
Scenario: Editing Access Group description to description with only numbers3 ms0055
Scenario: Editing Access Group description to description with special symbols4 ms0044
Scenario: Editing Access Group description to long description3 ms0055
Scenario: Editing Access Group description to non-unique one3 ms0055
Scenario: Editing Access Group description to short description2 ms0055
Scenario: Editing Access Group description to unique one6 ms0077
Scenario: Editing Access Group name to a long one3 ms0077
Scenario: Editing Access Group name to a too long one3 ms0055
Scenario: Editing Access Group name to empty name4 ms0055
Scenario: Editing Access Group name to name that contains numbers3 ms0077
Scenario: Editing Access Group name to name that contains only numbers5 ms0077
Scenario: Editing Access Group name to name with invalid special symbols in name2 ms0055
Scenario: Editing Access Group name to name with valid special symbols13 ms0077
Scenario: Editing Access Group name to non-unique one4 ms0066
Scenario: Editing Access Group name to short one4 ms0077
Scenario: Editing Access Group name to too short one2 ms0055
Scenario: Editing Access Group name to valid one3 ms0077
Scenario: Editing Endpoint Domain Name So It Contains Invalid Symbols14 ms0088
Scenario: Editing Endpoint Domain Name So It Contains Only Numbers8 ms0088
Scenario: Editing Endpoint Domain Name So It Has Max Value14 ms0077
Scenario: Editing Endpoint Domain Name So It Has Min Value14 ms0077
Scenario: Editing Endpoint Domain Name To Non-unique Value4 ms0099
Scenario: Editing Endpoint Domain Name To Unique Value4 ms0077
Scenario: Editing Endpoint Port To Non-unique Value8 ms0099
Scenario: Editing Endpoint Port To Unique Value15 ms0077
Scenario: Editing Endpoint Schema And Leaving It Empty5 ms0088
Scenario: Editing Endpoint Schema So It Contains "http://"6 ms0088
Scenario: Editing Endpoint Schema So It Contains "https://"4 ms0088
Scenario: Editing Endpoint Schema So It Contains Invalid Symbols6 ms0088
Scenario: Editing Endpoint Schema So It Contains Only Numbers4 ms0088
Scenario: Editing Endpoint Schema So It Has Max Length4 ms0077
Scenario: Editing Endpoint Schema So It Has Min Length5 ms0077
Scenario: Editing Endpoint Schema To Non-unique Value4 ms0088
Scenario: Editing Endpoint Schema To Unique Value4 ms0077
Scenario: Editing Endpoint Secure Field To Non-unique Value7 ms0099
Scenario: Editing Endpoint Secure Field To Unique Value5 ms0077
Scenario: Editing Endpoint To NULL Values7 ms001414
Scenario: Editing Endpoint To Non-unique Endpoint4 ms001010
Scenario: Editing Group's Name To Contain Numbers Without Changing Description6 ms0077
Scenario: Editing Tag's Name To Contain Numbers Without Description5 ms0077
Scenario: Empty query results are supported6 ms0088
Scenario: Event factory sanity checks4 ms0022
Scenario: Event service domain check8 ms0022
Scenario: Every account must have the default configuration items6 ms0033
Scenario: Execute possible docker steps to show its usage7 ms231033
Scenario: Executing Job And Then Restarting Device8 ms2162745
Scenario: Executing Job When Device Connected After End Date And Time29 ms003838
Scenario: Executing Job When Device Connected After The Specified Start Date And Time13 ms263038
Scenario: Executing Job When Device Connected Before End Date And Time11 ms263139
Scenario: Executing Job When Device Connected Before The Specified Start Date And Time25 ms003737
Scenario: Executing Job Without Steps32 ms004040
Scenario: Extra long continuous test with multiple subscenarios with LOOSE default connection mode36 ms00419419
Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode31 ms00397397
Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode and no previously defined devices23 ms00305305
Scenario: Find a connection by its IDs3 ms0066
Scenario: Find a connection by its client ID3 ms0066
Scenario: Find a group entry in the database10 ms0099
Scenario: Find a non existing event8 ms0066
Scenario: Find account by Id5 ms0044
Scenario: Find account by Ids6 ms0044
Scenario: Find account by name8 ms0044
Scenario: Find account by random Id5 ms0033
Scenario: Find all child accounts10 ms0033
Scenario: Find an access info entity7 ms001111
Scenario: Find an access info entity by user ID4 ms001010
Scenario: Find an event by its ID10 ms0066
Scenario: Find an existing access role entity7 ms001313
Scenario: Find by name nonexisting account5 ms0033
Scenario: Find correct number of messages by corresponding metric0.51 sec005858
Scenario: Find device by client ID4 ms0033
Scenario: Find device by registry ID3 ms0044
Scenario: Find last created permission6 ms001212
Scenario: Find multiple users3 ms0055
Scenario: Find role by ID13 ms0077
Scenario: Find self account by id9 ms001111
Scenario: Find self account by id and scope id11 ms001111
Scenario: Find self account by name8 ms001111
Scenario: Find the last created domain entry7 ms0055
Scenario: Find user by id4 ms0055
Scenario: Find user by its email3 ms0066
Scenario: Find user by its phone number3 ms0066
Scenario: Find user by name4 ms0055
Scenario: Find user by name that doesn't exist5 ms0033
Scenario: Find user with id and scope id that doesn't exist6 ms0033
Scenario: Finding all messages by selecting all metrics0.47 sec004040
Scenario: Finding correct number of messages by corresponding two metrics0.65 sec005252
Scenario: Finding messages with incorrect metric parameters0.5 sec007272
Scenario: Finding user by expiration date in the future4 ms0055
Scenario: Finding user by expiration date in the past7 ms0066
Scenario: Finding user by expiration date in the present4 ms0066
Scenario: Generic connection query4 ms0088
Scenario: Get metadata4 ms0033
Scenario: Group with a null name7 ms0077
Scenario: Handle account creation22 ms0033
Scenario: Handle duplicate account names10 ms0055
Scenario: Handle null account name13 ms0044
Scenario: Handling of 2 birth messages4 ms001212
Scenario: Handling of a disconnect message from a non existing device7 ms001010
Scenario: Have Two Devices in The Same Group Without Description6 ms001313
Scenario: I try to find a non-existing connection3 ms0066
Scenario: If user credential expiration date is before today, user can not login10 ms001414
Scenario: If user credential expiration date is today, user can not login it is day inclusive8 ms001414
Scenario: If user credential expiration date is tomorrow, user can login4 ms001313
Scenario: If user credential is in state disabled, user can not login5 ms001414
Scenario: If user credential is in state enabled, user can login6 ms001313
Scenario: If user expiration date is before today, user can not login7 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 login11 ms001212
Scenario: Init Security Context for all scenarios0.19 sec004848
Scenario: Installing a package25 ms001313
Scenario: Interval Job" Schedule With Too Long Name6 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 items4 ms0055
Scenario: Job execution factory sanity checks4 ms0022
Scenario: Job factory sanity checks3 ms0033
Scenario: Job with a duplicate name3 ms0099
Scenario: Job with a null name3 ms0088
Scenario: Job with a null scope ID6 ms0099
Scenario: Job with an empty name4 ms0088
Scenario: List Endpoints Created From Sub-Account8 ms223126
Scenario: List Endpoints From "kapua-sys" Account7 ms24511
Scenario: List Endpoints From Sub-Account Of Another Sub-Account6 ms223126
Scenario: List Endpoints From Sub-account4 ms212115
Scenario: MetricsInfo client ID and topic data based on the client id30 ms003434
Scenario: MetricsInfo last published date30 ms004848
Scenario: Modify a role that was deleted10 ms0099
Scenario: Modify an existing account7 ms0044
Scenario: Modify last child expiration so that it still expires before parent11 ms001414
Scenario: Modify middle child expiration so that it still expires before parent6 ms001414
Scenario: Modify middle child expiration to outlive parent7 ms001515
Scenario: Modify nonexisting account7 ms0066
Scenario: Modify parent expiration so that it still expires after child8 ms001414
Scenario: Modify parent expiration to before child expiration11 ms001515
Scenario: Modifying Sub-account of a different parent account15 ms002525
Scenario: Moving Device From One Group With Description to Another11 ms001414
Scenario: Nameless role entry6 ms0077
Scenario: Negative scenario when client connects twice with same client id15 ms001111
Scenario: New connection with reserved ID13 ms003434
Scenario: Permission factory sanity checks5 ms0033
Scenario: Positive scenario without stealing link27 ms001212
Scenario: Query based on message ordering38 ms002020
Scenario: Query based on metrics ordering50 ms002020
Scenario: Query before schema search22 ms008282
Scenario: Query for a specific group by name5 ms001616
Scenario: Query for all the access info entities of a specific user5 ms001818
Scenario: Query for all the access info entities of an invalid user8 ms001010
Scenario: Query for executions of a specific job7 ms001818
Scenario: Query for jobs with specified name5 ms0099
Scenario: Query for step definitions6 ms0077
Scenario: Query user5 ms0066
Scenario: Querying Other Items With All Account Permissions13 ms003939
Scenario: Regular connection4 ms0077
Scenario: Regular creation of Access Role entity6 ms001414
Scenario: Regular domain8 ms0055
Scenario: Regular group in random scope11 ms0077
Scenario: Regular group in root scope16 ms0077
Scenario: Regular job creation4 ms001010
Scenario: Regular job execution creation4 ms0077
Scenario: Regular role creation9 ms0099
Scenario: Regular step creation13 ms0011-111-1
Scenario: Regular step definition creation7 ms0077
Scenario: Regular step definition with a property list6 ms0044
Scenario: Reset Security Context for all scenarios0.19 sec004848
Scenario: Restarting a job with Asset Write and Bundle Start steps20 ms002828
Scenario: Restarting a job with Command Execution and Bundle Start steps20 ms002828
Scenario: Restarting a job with Configuration Put and Bundle Start steps30 ms002828
Scenario: Restarting a job with Package Uninstall and Bundle Start steps21 ms002828
Scenario: Restarting a job with invalid Configuration Put and multiple devices two times33 ms003333
Scenario: Restarting a job with invalid Configuration Put step two times53 ms003636
Scenario: Restarting a job with invalid Package Install step and multiple devices two times26 ms003131
Scenario: Restarting a job with invalid Package Install step two times35 ms003434
Scenario: Restarting a job with invalid Package Uninstall step and multiple devices two times43 ms003232
Scenario: Restarting a job with invalid Package Uninstall step two times42 ms003434
Scenario: Restarting a job with valid Configuration Put step and multiple devices two times31 ms003333
Scenario: Restarting a job with valid Configuration Put step two times41 ms003636
Scenario: Restarting a job with valid Package Install step and multiple devices two times31 ms002929
Scenario: Restarting a job with valid Package Install step two times36 ms003434
Scenario: Restarting a job with valid Package Uninstall step and multiple devices two times26 ms003030
Scenario: Restarting a job with valid Package Uninstall step two times26 ms003232
Scenario: Restarting job With invalid Asset Write and multiple two times28 ms003434
Scenario: Restarting job With valid Asset Write step two times28 ms003636
Scenario: Restarting job with Asset Write and Bundle Start steps and multiple devices23 ms003131
Scenario: Restarting job with Asset Write step55 ms002525
Scenario: Restarting job with Asset Write step and multiple devices25 ms002828
Scenario: Restarting job with Bundle Start step24 ms002525
Scenario: Restarting job with Bundle Start step and multiple devices24 ms002727
Scenario: Restarting job with Bundle Stop and Bundle Start step and multiple devices25 ms003131
Scenario: Restarting job with Bundle Stop and Bundle Start steps23 ms002929
Scenario: Restarting job with Bundle Stop step18 ms002525
Scenario: Restarting job with Bundle Stop step and multiple devices33 ms002727
Scenario: Restarting job with Command Execution and Bundle Start steps and multiple devices22 ms003131
Scenario: Restarting job with Command Execution step33 ms002525
Scenario: Restarting job with Command Execution step and multiple devices21 ms002727
Scenario: Restarting job with Configuration Put and Bundle Start steps and multiple devices27 ms003131
Scenario: Restarting job with Configuration Put step26 ms002525
Scenario: Restarting job with Configuration Put step and multiple devices32 ms002727
Scenario: Restarting job with Package Download/Install and Bundle Start steps and multiple devices48 ms005959
Scenario: Restarting job with Package Download/Install step and multiple devices23 ms002727
Scenario: Restarting job with Package Install step20 ms002525
Scenario: Restarting job with Package Uninstall and Bundle start steps and multiple device34 ms003131
Scenario: Restarting job with Package Uninstall step44 ms002525
Scenario: Restarting job with Package Uninstall step and multiple device28 ms002727
Scenario: Restarting job with invalid Asset Write step two times32 ms003636
Scenario: Restarting job with invalid Bundle Start and Bundle Stop steps and multiple devices two times31 ms004141
Scenario: Restarting job with invalid Bundle Start and Bundle Stop steps two times33 ms004343
Scenario: Restarting job with invalid Bundle Start step and multiple devices two times52 ms003535
Scenario: Restarting job with invalid Bundle Start step two times23 ms003737
Scenario: Restarting job with invalid Bundle Stop step and multiple devices two times45 ms003535
Scenario: Restarting job with invalid Bundle Stop step two times25 ms003737
Scenario: Restarting job with invalid Command Execution and Package Install step two times38 ms003636
Scenario: Restarting job with invalid Command Execution and Package Install steps and multiple devices two times20 ms003737
Scenario: Restarting job with invalid Command Execution step and multiple devices two times49 ms003131
Scenario: Restarting job with invalid Command Execution step two times52 ms003232
Scenario: Restarting job with invalid Configuration Put And Command Execution steps two times28 ms003838
Scenario: Restarting job with invalid Configuration Put and Command Execution steps and multiple devices two times47 ms003737
Scenario: Restarting job with invalid Package Uninstall and Asset Write steps and multiple devices two times47 ms003838
Scenario: Restarting job with invalid Package Uninstall and Asset Write steps two times24 ms004040
Scenario: Restarting job with two Bundle Start steps24 ms002929
Scenario: Restarting job with two Bundle Start steps and multiple devices36 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 times27 ms004343
Scenario: Restarting job with valid Bundle Start and Bundle Stop steps and multiple devices two times51 ms004141
Scenario: Restarting job with valid Bundle Start step and multiple devices two times57 ms003535
Scenario: Restarting job with valid Bundle Start step two times29 ms003737
Scenario: Restarting job with valid Bundle Stop step and multiple devices two times40 ms003535
Scenario: Restarting job with valid Bundle Stop step two times39 ms003737
Scenario: Restarting job with valid Command Execution and Package Install steps and multiple devices two times51 ms003333
Scenario: Restarting job with valid Command Execution and Package Install steps two times30 ms003434
Scenario: Restarting job with valid Command Execution step and multiple devices two times47 ms003131
Scenario: Restarting job with valid Command Execution step two times60 ms003232
Scenario: Restarting job with valid Configuration Put and Command Execution steps and multiple devices two times30 ms003737
Scenario: Restarting job with valid Configuration Put and Command Execution steps two times36 ms003838
Scenario: Restarting job with valid Package Uninstall and Asset Write steps and multiple devices two times44 ms003636
Scenario: Restarting job with valid Package Uninstall and Asset Write steps two times37 ms003838
Scenario: Role creator sanity checks5 ms0022
Scenario: Role entry with no actions6 ms0066
Scenario: Role object equality check6 ms0022
Scenario: Role service related objects sanity checks8 ms0044
Scenario: Search By Client ID And Get Multiple Matches38 ms003737
Scenario: Search By Client ID And Get No Matches7 ms001010
Scenario: Search By Client ID And Get One Match13 ms0088
Scenario: Search By Client ID and Display Name13 ms001212
Scenario: Search By Client ID and Serial Number6 ms001212
Scenario: Search By Client ID and Status5 ms001212
Scenario: Search By Client ID, Display Name and Serial Number11 ms001212
Scenario: Search By Client ID, Display Name and Status11 ms001212
Scenario: Search By Client ID, Display Name, Serial Number and Status8 ms001212
Scenario: Search By Device Status And Get No Matches8 ms0088
Scenario: Search By Device's Display Name And Get One Match8 ms0088
Scenario: Search By Display Name and Serial Number9 ms001212
Scenario: Search By Display Name and Status12 ms001212
Scenario: Search By Full Client ID And Get One Match19 ms001010
Scenario: Search By Non-existing Client ID And Get No Matches15 ms0088
Scenario: Search By One Letter Of Display Name13 ms0088
Scenario: Search By One Letter Of Serial Number6 ms001212
Scenario: Search By Serial Number And Get Multiple Matches13 ms001414
Scenario: Search By Serial Number And Get No Matches9 ms001010
Scenario: Search By Serial Number And Get One Match10 ms001111
Scenario: Search By Serial Number and Status5 ms001212
Scenario: Search By Serial Number, Display Name and Status13 ms001212
Scenario: Search By Specific Serial Number10 ms001010
Scenario: Search By Status And Get Multiple Matches9 ms001010
Scenario: Search by Device Status And Get One Match11 ms001010
Scenario: Search for a non existent client ID5 ms0066
Scenario: Search for an access info entity by an incorrect user ID8 ms001111
Scenario: Search the role database for a random ID6 ms0077
Scenario: Send BIRTH message and then DC message27 ms001515
Scenario: Send BIRTH message and then DC message while broker ip is NOT set38 ms0066
Scenario: Send BIRTH message and then DC message while broker ip is set by System53 ms0088
Scenario: Send BIRTH message and then DC message while broker ip is set by config file51 ms0088
Scenario: Set a correct minimum for password length7 ms0033
Scenario: Set an incorrect minimum for password length9 ms0066
Scenario: Set environment variables0.16 sec006161
Scenario: Setting InfiniteChildAccounts To False And Increasing MaxNumberChildAccounts When Sub-accounts Are Already Created10 ms001414
Scenario: Setting InfiniteChildAccounts To False When Sub-accounts Are Already Created7 ms001515
Scenario: Setting InfiniteChildAccounts To True And Decreasing MaxNumberChildAccounts When Sub-accounts Are Already Created9 ms001414
Scenario: Setting Lockout Duration To 0 Seconds9 ms001515
Scenario: Setting Lockout Duration To Negative Value10 ms0077
Scenario: Setting Max Failures To 011 ms001515
Scenario: Setting Max Failures To 18 ms001515
Scenario: Setting Max Failures To 10014 ms001515
Scenario: Setting Max Failures To Negative Value9 ms0077
Scenario: Setting Reset After Login Counter To 0 Seconds15 ms001717
Scenario: Setting Reset After Login Counter To Negative Value14 ms0077
Scenario: Setting configuration without mandatory items must raise an error4 ms0055
Scenario: Simple create6 ms001111
Scenario: Simple positive scenario for creating daily index18 ms001414
Scenario: Simple positive scenario for creating default - weekly index13 ms001212
Scenario: Simple positive scenario for creating hourly index17 ms001414
Scenario: Start broker for all scenarios0.32 sec004444
Scenario: Start datastore for all scenarios0.62 sec003030
Scenario: Start event broker for all scenarios0.46 sec005050
Scenario: Starting a job with Asset Write and Bundle Start steps31 ms003636
Scenario: Starting a job with Asset Write step20 ms002525
Scenario: Starting a job with Bundle Start step20 ms003434
Scenario: Starting a job with Bundle Stop and Bundle Start steps27 ms003939
Scenario: Starting a job with Bundle Stop step25 ms003535
Scenario: Starting a job with Command Execution and Bundle Start steps29 ms003737
Scenario: Starting a job with Command Execution step21 ms002525
Scenario: Starting a job with Configuration Put and Bundle Start steps25 ms003737
Scenario: Starting a job with Configuration Put step25 ms002525
Scenario: Starting a job with Package Install and Bundle Start steps24 ms003939
Scenario: Starting a job with Package Install step20 ms003232
Scenario: Starting a job with Package Uninstall and Bundle Start steps23 ms003636
Scenario: Starting a job with Package Uninstall step31 ms003333
Scenario: Starting a job with invalid Asset Write step32 ms003131
Scenario: Starting a job with invalid Asset Write step and multiple targets38 ms002929
Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps25 ms003636
Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps and multiple devices74 ms003535
Scenario: Starting a job with invalid Bundle Start step25 ms003131
Scenario: Starting a job with invalid Bundle Stop step22 ms003131
Scenario: Starting a job with invalid Bundle Stop step and multiple devices40 ms002929
Scenario: Starting a job with invalid Command Execution step27 ms002727
Scenario: Starting a job with invalid Configuration Put step36 ms003030
Scenario: Starting a job with invalid Configuration Put step and multiple devices63 ms002828
Scenario: Starting a job with invalid Package Install step40 ms002929
Scenario: Starting a job with invalid Package Install step and multiple devices40 ms002626
Scenario: Starting a job with invalid Package Uninstall and Asset Write steps36 ms003434
Scenario: Starting a job with invalid Package Uninstall and Asset Write steps and multiple devices61 ms003232
Scenario: Starting a job with invalid Package Uninstall step42 ms002929
Scenario: Starting a job with invalid Package Uninstall step and multiple targets42 ms002626
Scenario: Starting a job with two Bundle Start steps22 ms003939
Scenario: Starting a job with valid Asset Write step38 ms003131
Scenario: Starting a job with valid Asset Write step and multiple targets59 ms002929
Scenario: Starting a job with valid Bundle Start and Bundle Stop steps20 ms003636
Scenario: Starting a job with valid Bundle Start and Bundle Stop steps and multiple devices64 ms003434
Scenario: Starting a job with valid Bundle Start step31 ms003131
Scenario: Starting a job with valid Bundle Stop step24 ms003131
Scenario: Starting a job with valid Bundle Stop step and multiple devices51 ms002929
Scenario: Starting a job with valid Command Execution step36 ms002727
Scenario: Starting a job with valid Configuration Put step31 ms003131
Scenario: Starting a job with valid Configuration Put step and multiple devices42 ms002626
Scenario: Starting a job with valid Package Install step27 ms002929
Scenario: Starting a job with valid Package Install step and multiple devices24 ms002626
Scenario: Starting a job with valid Package Uninstall and Asset Write steps19 ms003333
Scenario: Starting a job with valid Package Uninstall and Asset Write steps and multiple devices58 ms003232
Scenario: Starting a job with valid Package Uninstall step45 ms003030
Scenario: Starting a job with valid Package Uninstall step and multiple targets42 ms002626
Scenario: Starting and stopping the simulator should create a device entry and properly set its status13 ms002020
Scenario: Starting job with Asset Write and Bundle Start steps and multiple devices20 ms003232
Scenario: Starting job with Asset Write step and multiple devices31 ms002828
Scenario: Starting job with Bundle Start step and multiple devices21 ms002828
Scenario: Starting job with Bundle Stop and Bundle Start step and multiple devices25 ms003232
Scenario: Starting job with Bundle Stop step and multiple devices34 ms002828
Scenario: Starting job with Command Execution and Bundle Start steps and multiple devices22 ms003232
Scenario: Starting job with Command Execution step and multiple devices20 ms002828
Scenario: Starting job with Configuration Put and Bundle Start steps and multiple devices26 ms003232
Scenario: Starting job with Configuration Put step and multiple devices24 ms002828
Scenario: Starting job with Package Download/Install and Bundle Start steps and multiple devices25 ms003838
Scenario: Starting job with Package Download/Install step and multiple devices22 ms003434
Scenario: Starting job with Package Uninstall and Bundle start steps and multiple device22 ms003232
Scenario: Starting job with Package Uninstall step and multiple device26 ms002727
Scenario: Starting job with invalid Bundle Start step and multiple devices29 ms002929
Scenario: Starting job with invalid Command Execution and Package Install steps33 ms003131
Scenario: Starting job with invalid Command Execution step and multiple devices47 ms002828
Scenario: Starting job with invalid Command Execution, invalid Package Install steps and multiple devices63 ms002929
Scenario: Starting job with invalid Configuration Put and Command Execution steps33 ms003232
Scenario: Starting job with invalid Configuration Put and Command Execution steps and multiple devices47 ms003131
Scenario: Starting job with two Bundle Start steps and multiple devices15 ms003232
Scenario: Starting job with valid Bundle Start step and multiple devices40 ms002929
Scenario: Starting job with valid Command Execution and Package Install steps34 ms003131
Scenario: Starting job with valid Command Execution step and multiple devices36 ms002626
Scenario: Starting job with valid Command Execution, valid Package Install steps and multiple devices48 ms002929
Scenario: Starting job with valid Configuration Put and Command Execution steps28 ms003232
Scenario: Starting job with valid Configuration Put and Command Execution steps and multiple devices47 ms003030
Scenario: Stealing link scenario7 ms002828
Scenario: Step definition factory sanity checks4 ms0022
Scenario: Step definition with a duplicate name6 ms0066
Scenario: Step definition with a null name5 ms0066
Scenario: Step definition with a null scope ID5 ms0066
Scenario: Step definition with an empty name5 ms0055
Scenario: Step factory sanity checks3 ms0022
Scenario: Step with a null scope ID6 ms0011-111-1
Scenario: Stop broker after all scenarios0.41 sec004646
Scenario: Stop datastore after all scenarios0.24 sec003030
Scenario: Stop event broker for all scenarios0.4 sec005050
Scenario: Stop job with multiple Asset Write and Package Install steps and one target27 ms003737
Scenario: Stop job with multiple Bundle Start and Package Install steps and one target40 ms003737
Scenario: Stop job with multiple Bundle Stop and Package Uninstall steps and one target42 ms003737
Scenario: Stop job with multiple Command Execution and Package Install steps and one target37 ms003434
Scenario: Stop job with multiple Configuration Put and Package Uninstall steps and one target29 ms003535
Scenario: Stop job with multiple targets and Asset Write and Package Install steps and one target55 ms003737
Scenario: Stop job with multiple targets and Bundle Start and Package Install steps40 ms003636
Scenario: Stop job with multiple targets and Bundle Stop and Package Uninstall steps44 ms003737
Scenario: Stop job with multiple targets and Command Execution and Package Install steps82 ms003434
Scenario: Stop job with multiple targets and Configuration Put and Package Uninstall steps26 ms003737
Scenario: Test LOOSE user coupling on single connection10 ms002828
Scenario: Test LOOSE user coupling with 3 connections11 ms003838
Scenario: Test STRICT user coupling on single connection25 ms002525
Scenario: Test STRICT user coupling with 3 connections and a reserved user16 ms006363
Scenario: Test STRICT user coupling with user change allowed on single connection10 ms003636
Scenario: Test account query7 ms0044
Scenario: Test the message store with server timestamp indexing38 ms002626
Scenario: Test the message store with timestamp indexing52 ms002626
Scenario: The Client ID is case sensitive3 ms0088
Scenario: To be defined14 ms001313
Scenario: Translating "CommandRequestMessage" to "KuraRequestMessage"38 ms0044
Scenario: Translating CommandRequestMessage to null7 ms0044
Scenario: Translating empty message to empty message11 ms0044
Scenario: Translating from "AssetRequestMessage" to "AssetResponseMessage"5 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 message4 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 metrics3 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 message3 ms0055
Scenario: Translating kura data message with valid channel, and with null payload3 ms0055
Scenario: Translating kura data message with valid channel, body and metrics into jms message3 ms0055
Scenario: Translating kura data message with valid channel, metrics and without body into jms 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 message2 ms0055
Scenario: Translating of jms message with empty payload and valid topic into kura data message3 ms0066
Scenario: Translating of jms message with invalid payload and valid topic into kura data message3 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 message3 ms0055
Scenario: Translating of mqtt message with invalid payload and with null topic into kura data message5 ms0055
Scenario: Translation of kura data message with valid channel and without body and metrics into mqtt message6 ms0055
Scenario: Translation of kura data message with valid channel, body and metrics into mqtt message5 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 message5 ms0066
Scenario: Translation of mqtt message with invalid payload and invalid topic into kura response message4 ms0055
Scenario: Translation of mqtt message with invalid payload and valid topic into kura data message12 ms0066
Scenario: Translation of mqtt message with invalid payload and valid topic into kura response message6 ms0066
Scenario: Translation of mqtt message with valid payload and invalid topic into kura response message4 ms0055
Scenario: Translation of mqtt message with valid payload and valid topic into kura data message7 ms0066
Scenario: Translation of mqtt message with valid payload and valid topic into kura response message4 ms0066
Scenario: Try to add two different roles with same permissions30 ms002121
Scenario: Try to change an existing connection ID4 ms0077
Scenario: Try to create an access into entity with an invalid role id6 ms001212
Scenario: Try to delete a non existing device from the registry2 ms0044
Scenario: Try to find a device with an invalid client ID4 ms0033
Scenario: Try to find a device with an invalid registry ID4 ms0033
Scenario: Try to find users granted to "admin" role17 ms001212
Scenario: Try to find users that have assigned specific role17 ms001212
Scenario: Try to modify the connection client ID3 ms0077
Scenario: Try to update the device client ID4 ms0044
Scenario: Uncorrect Login While Lockout Policy Is Disabled8 ms001717
Scenario: Uncorrect Login While Lockout Policy Is Enabled13 ms001717
Scenario: Update a group entry in the database9 ms0099
Scenario: Update a group entry with a false ID8 ms001010
Scenario: Update a job XML definition9 ms001010
Scenario: Update a job description11 ms001010
Scenario: Update a job name11 ms001010
Scenario: Update a non existing device4 ms0055
Scenario: Update a nonexistent job4 ms001010
Scenario: Update a nonexistent step definition4 ms0077
Scenario: Update a step definition name6 ms0077
Scenario: Update a step definition processor name4 ms0088
Scenario: Update a step definition target type15 ms0088
Scenario: Update existing role name9 ms0088
Scenario: Update job id of an existing execution item11 ms0088
Scenario: Update schedule which doesn't exist7 ms0055
Scenario: Update scheduler end date8 ms0099
Scenario: Update scheduler name9 ms0088
Scenario: Update scheduler start date7 ms0088
Scenario: Update the end time of an existing execution item5 ms0099
Scenario: Update trigger definition8 ms0088
Scenario: Update user8 ms0077
Scenario: Update user that doesn't exist6 ms0055
Scenario: User locking itself out by using out login attempts4 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 unlock9 ms001717
Scenario: User login with wrong pass, but with enough time between login failures4 ms001919
Scenario: User not locking itself out by using less than max failed login attempts5 ms001717
Scenario: Validate a device client based search with a null client ID2 ms0055
Scenario: Validate a device client based search with an empty client ID2 ms0055
Scenario: Validate a device client search with null scope3 ms0055
Scenario: Validate a device creator with a null client ID3 ms0066
Scenario: Validate a device creator with a null scope ID6 ms0066
Scenario: Validate a device query with a null Scope ID3 ms0044
Scenario: Validate a device search with a null device ID3 ms0066
Scenario: Validate a device search with a null scope ID2 ms0066
Scenario: Validate a null creator5 ms0055
Scenario: Validate a null device3 ms0055
Scenario: Validate a null device count3 ms0055
Scenario: Validate a null device query3 ms0055
Scenario: Validate a regular creator6 ms0044
Scenario: Validate a regular device client search3 ms0044
Scenario: Validate a regular device count3 ms0044
Scenario: Validate a regular device query4 ms0044
Scenario: Validate a regular device search4 ms0055
Scenario: Validate deleting a device with a null device ID7 ms0066
Scenario: Validate deleting a device with a null scope ID1 ms0066
Scenario: Waiting For Lock Duration Time To Pass8 ms001919
Scenario: Waiting For Reset After Login Counter To Pass9 ms001818
empty) scope1 ms0044