Test Result : (root)

37 failures (±0) , 179 skipped (±0)
16,563 tests (±0)
Took 44 sec.

All Failed Tests

Test NameDurationAge
 Scenario: Add datastore permissions to the role.And I search for data message with id "fake-id"1 ms12
 Scenario: Add datastore permissions to the role.Scenario: Add datastore permissions to the role2 ms12
 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 id3 ms14
 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"}"2 ms14
 Scenario: Create same user in different accounts.Scenario: Create same user in different accounts1.9 sec12
 Scenario: Create scheduler with correct end date.Scenario: Create scheduler with correct end date3 ms10
 Scenario: Create scheduler with correct end date.Then I create a new trigger from the existing creator with previously defined date properties2 ms10
 Scenario: Create scheduler with end date before start date.Scenario: Create scheduler with end date before start date9 ms10
 Scenario: Create scheduler with end date before start date.Then I create a new trigger from the existing creator with previously defined date properties9 ms10
 Scenario: Creating unique Access Group with special symbols in description.Scenario: Creating unique Access Group with special symbols in description12 ms32
 Scenario: Creating unique Access Group with special symbols in description.Then I find the group with name "groupName53"11 ms32
 Scenario: Deleting user in account that is higher in hierarchy.Scenario: Deleting user in account that is higher in hierarchy1.8 sec12
 Scenario: Deleting user in account that is lower in hierarchy.Scenario: Deleting user in account that is lower in hierarchy1.8 sec12
 Scenario: Execute possible docker steps to show its usage.Given List images by name "kapua/kapua-broker:1.5.0-SNAPSHOT"2 ms19
 Scenario: Execute possible docker steps to show its usage.Scenario: Execute possible docker steps to show its usage3 ms19
 Scenario: Init Security Context for all scenarios.Scenario: Init Security Context for all scenarios1.9 sec12
 Scenario: List Endpoints Created From Sub-Account.And I create endpoint with schema "Schema1", domain "abc.com" and port 22222 ms12
 Scenario: List Endpoints Created From Sub-Account.Scenario: List Endpoints Created From Sub-Account3 ms12
 Scenario: List Endpoints From "kapua-sys" Account.Scenario: List Endpoints From "kapua-sys" Account2 ms12
 Scenario: List Endpoints From "kapua-sys" Account.Then I find 3 endpoints2 ms12
 Scenario: List Endpoints From Sub-Account Of Another Sub-Account.And I create endpoint with schema "Schema1", domain "abc.com" and port 22221 ms12
 Scenario: List Endpoints From Sub-Account Of Another Sub-Account.Scenario: List Endpoints From Sub-Account Of Another Sub-Account3 ms12
 Scenario: List Endpoints From Sub-account.And I create endpoint with schema "Schema1", domain "abc.com" and port 22222 ms12
 Scenario: List Endpoints From Sub-account.Scenario: List Endpoints From Sub-account4 ms12
 Scenario: Reset Security Context for all scenarios.Scenario: Reset Security Context for all scenarios1.9 sec12
 Scenario: Simple Jetty with rest-api war.Scenario: Simple Jetty with rest-api war2 ms14
 Scenario: Simple Jetty with rest-api war.When REST POST call at "/v1/authentication/user" with JSON "{"password": "kapua-password", "username": "kapua-sys"}"2 ms14
 Scenario: Start Jetty server for all scenarios.Given Start Jetty Server on host "127.0.0.1" at port "8081"1 ms14
 Scenario: Start Jetty server for all scenarios.Scenario: Start Jetty server for all scenarios2 ms14
 Scenario: Start datastore for all scenarios.Given Start Datastore1 ms12
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios2 ms12
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios1.9 sec12
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios1.8 sec12
 Scenario: Update scheduler end date.And I try to edit end date to 13-12-2020 at 10:002 ms10
 Scenario: Update scheduler end date.Scenario: Update scheduler end date3 ms10
 Scenario: Update trigger definition.And I try to edit trigger definition to "Cron Job"2 ms10
 Scenario: Update trigger definition.Scenario: Update trigger definition3 ms10

All Tests

ClassDurationFail(diff)Skip(diff)Pass(diff)Total(diff)
Scenario: A fresh database must contain 1 default role in the root scope7 ms0044
Scenario: A newly created account must have some metadata6 ms0033
Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic8 ms0088
Scenario: Access info service sanity checks11 ms0044
Scenario: Access service comparison sanity checks11 ms0033
Scenario: Account based ClientInfo data check23 ms002424
Scenario: Account exactly on its expiration date8 ms001414
Scenario: Account name must not be mutable7 ms0066
Scenario: Account past its expiration date8 ms001414
Scenario: Account wide metrics check15 ms002828
Scenario: Account with future expiration date8 ms001313
Scenario: Account with no expiration date9 ms001313
Scenario: Add Access Info domain permissions to new user14 ms002626
Scenario: Add Account permissions to the role in child account31 ms002828
Scenario: Add Credential domain permissions to new user14 ms001818
Scenario: Add Datastore domain permissions to new user0.29 sec001919
Scenario: Add Device Connection domain permissions to kapua-sys user13 ms001111
Scenario: Add Device Connection domain permissions to new user15 ms002323
Scenario: Add Device Event domain permissions to new user15 ms001616
Scenario: Add Device domain permissions to new user25 ms001717
Scenario: Add Domain domain permissions to kapua-sys user14 ms001717
Scenario: Add Domain domain permissions to new user14 ms003232
Scenario: Add Endpoint Permission To The User14 ms003030
Scenario: Add Endpoint_info permissions to the role in child account22 ms003030
Scenario: Add Group domain permissions to new user13 ms001717
Scenario: Add Group permissions to the role in child account21 ms002626
Scenario: Add Job domain permissions to new user16 ms001919
Scenario: Add Role domain permissions to new user17 ms001717
Scenario: Add Role permissions to the role in child account23 ms002626
Scenario: Add Scheduler Permissions With Job Permissions14 ms003131
Scenario: Add Scheduler Permissions Without Job Permissions15 ms002121
Scenario: Add Scheduler permissions to the role in child account25 ms003636
Scenario: Add Tag domain permissions to new user15 ms001515
Scenario: Add Tag permissions to the role in child account35 ms002626
Scenario: Add User domain permissions to new user14 ms002020
Scenario: Add account permissions to the role24 ms001919
Scenario: Add admin role to the user28 ms004444
Scenario: Add and delete Account permissions from the "admin" role22 ms001414
Scenario: Add and delete Device permissions from the "admin" role23 ms001414
Scenario: Add and delete Endpoint_info permissions from the "admin" role22 ms001414
Scenario: Add and delete Group permissions from the "admin" role26 ms001414
Scenario: Add and delete Job permissions from the "admin" role24 ms001414
Scenario: Add and delete Role permissions from the "admin" role23 ms001414
Scenario: Add and delete User permissions from the "admin" role23 ms001515
Scenario: Add datastore permissions to the role3 ms232227
Scenario: Add deleted role again21 ms001010
Scenario: Add device event permissions to the role23 ms003232
Scenario: Add device permissions to the role29 ms001919
Scenario: Add device permissions to the role in child account21 ms002626
Scenario: Add domain, user and access_info permissions to the role28 ms002323
Scenario: Add endpoint_info permissions to the role24 ms003131
Scenario: Add group permissions to the role23 ms001818
Scenario: Add job permissions to the role29 ms001919
Scenario: Add job permissions to the role in child account21 ms002626
Scenario: Add role permissions to the role23 ms001919
Scenario: Add same permission twice to the same role31 ms001414
Scenario: Add same role to user twice24 ms001313
Scenario: Add scheduler permissions to the role23 ms003131
Scenario: Add tag permissions to the role33 ms001818
Scenario: Add user permissions to the role28 ms001919
Scenario: Add user permissions to the role in child account23 ms002626
Scenario: Adding "Cron Job" Schedule With All Valid Parameters7 ms001010
Scenario: Adding "Cron Job" Schedule With All Valid Parameters And Null Cron Value8 ms001010
Scenario: Adding "Cron Job" Schedule With All Valid Parameters Except Cron Format7 ms001111
Scenario: Adding "Cron Job" Schedule With End Date Only8 ms001010
Scenario: Adding "Cron Job" Schedule With End Time before Start time9 ms001212
Scenario: Adding "Cron Job" Schedule With Non-Unique End Date Parameter8 ms001616
Scenario: Adding "Cron Job" Schedule With Non-Unique Start Date Parameter10 ms001515
Scenario: Adding "Cron Job" Schedule With Start Date Only8 ms001111
Scenario: Adding "Cron Job" Schedule With the same Start and End time18 ms001212
Scenario: Adding "Cron Job" Schedule Without The Start Date Parameter11 ms001010
Scenario: Adding "Device Connect" Schedule With All Valid Parameters10 ms0088
Scenario: Adding "Device Connect" Schedule With End Date Only9 ms001010
Scenario: Adding "Device Connect" Schedule With End Time before Start time9 ms001111
Scenario: Adding "Device Connect" Schedule With Max Length Name9 ms0088
Scenario: Adding "Device Connect" Schedule With Min Length Name10 ms0088
Scenario: Adding "Device Connect" Schedule With Name Only8 ms0099
Scenario: Adding "Device Connect" Schedule With Non-Unique End Date Parameter8 ms001313
Scenario: Adding "Device Connect" Schedule With Non-Unique Name8 ms001414
Scenario: Adding "Device Connect" Schedule With Non-Unique Start Date Parameter8 ms001111
Scenario: Adding "Device Connect" Schedule With Start Date Only15 ms001010
Scenario: Adding "Device Connect" Schedule With the same Start and End time19 ms001111
Scenario: Adding "Device Connect" Schedule Without Name7 ms001010
Scenario: Adding "Device Connect" Schedule Without The Start Date Parameter10 ms0099
Scenario: Adding "Empty" Tag To Device7 ms0055
Scenario: Adding "Interval Job" Schedule With All Valid Parameters8 ms001010
Scenario: Adding "Interval Job" Schedule With End Date Only9 ms001010
Scenario: Adding "Interval Job" Schedule With End Time before Start time7 ms001212
Scenario: Adding "Interval Job" Schedule With Max Length Name10 ms001010
Scenario: Adding "Interval Job" Schedule With Min Length Name9 ms001010
Scenario: Adding "Interval Job" Schedule With Name Only10 ms001010
Scenario: Adding "Interval Job" Schedule With Non-Unique End Date Parameter10 ms001616
Scenario: Adding "Interval Job" Schedule With Non-Unique Name10 ms001515
Scenario: Adding "Interval Job" Schedule With Non-Unique Start Date Parameter9 ms001515
Scenario: Adding "Interval Job" Schedule With Null Interval Number9 ms001212
Scenario: Adding "Interval Job" Schedule With Start Date Only8 ms001111
Scenario: Adding "Interval Job" Schedule With the same Start and End time8 ms001212
Scenario: Adding "Interval Job" Schedule Without Interval Number8 ms001111
Scenario: Adding "Interval Job" Schedule Without The Start Date Parameter11 ms0099
Scenario: Adding "Interval Job" Schedule Without a Name11 ms001111
Scenario: Adding "admin" role to a user in a child account24 ms001414
Scenario: Adding "admin" role to multiple users37 ms001818
Scenario: Adding "admin" role twice46 ms001313
Scenario: Adding Account:Delete permission to user in same scope16 ms002525
Scenario: Adding Account:Delete permission to user in sub-account scope18 ms003030
Scenario: Adding Account:Read and Account:Delete permissions to user in same scope14 ms002121
Scenario: Adding Account:Read and Account:Write permissions to user in same scope15 ms001919
Scenario: Adding Account:Read permission to user in same scope14 ms002323
Scenario: Adding Account:Read permission to user in sub-account scope14 ms002929
Scenario: Adding Account:Write and Account:Delete permission to user in same scope18 ms002323
Scenario: Adding Account:Write permission to user in same scope17 ms002525
Scenario: Adding Account:Write permission to user in sub-account scope18 ms003131
Scenario: Adding Multiple Permissions To User15 ms002020
Scenario: Adding One Permission To User16 ms001111
Scenario: Adding Permissions To Child User16 ms001818
Scenario: Adding Permissions To Parallel User15 ms001818
Scenario: Adding Previously Deleted Permission15 ms002828
Scenario: Adding Previously Deleted Tag From Device Again6 ms001111
Scenario: Adding Regular Device to a Group With Description9 ms001010
Scenario: Adding Regular Device to a Group Without a Description9 ms001212
Scenario: Adding Regular Group Without Description to Device38 ms001010
Scenario: Adding Regular Tag Without Description To Device8 ms0066
Scenario: Adding Same Regular Group Without Description to Device34 ms001414
Scenario: Adding Tag With Long Name Without Description To Device7 ms0066
Scenario: Adding Tag With Numbers Without Description To Device7 ms0066
Scenario: Adding Tag With Short Name Without Description To Device8 ms0066
Scenario: Adding Tag With Special Symbols Without Description To Device7 ms0066
Scenario: Adding all Account permissions to user in same scope19 ms001717
Scenario: Adding all Account permissions to user in sub-account scope24 ms002424
Scenario: Adding existing roles to user61 ms001515
Scenario: Adding role from child account to user in new child account22 ms001515
Scenario: Adding role to multiple users in child account24 ms001818
Scenario: Adding same role twice to user in child account23 ms001515
Scenario: Adding the same role to user twice in child account23 ms001313
Scenario: All device parameters must match the device creator8 ms0033
Scenario: Assign 100 Devices to One Group33 ms001111
Scenario: B1 Broker publish to CTRL_ACC_REPLY6 ms0099
Scenario: B10 Broker create sub-topic on ACL_DATA_ACC is not allowed6 ms0099
Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed9 ms0088
Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI7 ms0099
Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed8 ms0099
Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed7 ms0088
Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY6 ms0099
Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY9 ms0099
Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account8 ms0099
Scenario: B5 Broker publish to CTRL_ACC is not allowed7 ms0099
Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed6 ms0099
Scenario: B7 Broker subscribe on CTRL_ACC is not allowed8 ms0088
Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI6 ms0099
Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed10 ms0099
Scenario: Basic Device Event queries17 ms001010
Scenario: Birth and applications event handling12 ms001212
Scenario: Birth and death message handling6 ms001212
Scenario: Birth and missing event handling6 ms001212
Scenario: Birth message handling from a new device8 ms001313
Scenario: Birth message handling from an existing device7 ms001212
Scenario: Both the parent and child accounts do not expire8 ms001111
Scenario: Both the parent and child accounts have the same expiration date12 ms001111
Scenario: Bug when user can retrieve user in another account if it has other account's user id6 ms2121933
Scenario: Captured date based ClientInfo data check15 ms003030
Scenario: Case sensitiveness of named device searches16 ms0044
Scenario: Change an existing step name4 ms001111
Scenario: Change role name so it is too short5 ms0066
Scenario: Change the account parent path10 ms0055
Scenario: Changing Client ID6 ms0099
Scenario: Changing Description On Group With Long Description8 ms0077
Scenario: Changing Description On Group With Long Name11 ms0077
Scenario: Changing Description On Group With Numbers In Name10 ms001010
Scenario: Changing Description On Group With Permitted Symbols8 ms0077
Scenario: Changing Description On Group With Short Description11 ms0077
Scenario: Changing Description On Group With Short Name10 ms0077
Scenario: Changing Description On Tag With Long Description20 ms0044
Scenario: Changing Description On Tag With Long Name6 ms0055
Scenario: Changing Description On Tag With Numbers In Name7 ms0066
Scenario: Changing Description On Tag With Permitted Symbols In Name6 ms0044
Scenario: Changing Description On Tag With Short Description6 ms0044
Scenario: Changing Description On Tag With Short Name7 ms0044
Scenario: Changing Device Status To Disabled7 ms0099
Scenario: Changing Device Status To Enabled6 ms0099
Scenario: Changing Group's Description To Non-Uniqe One9 ms0077
Scenario: Changing Group's Description To Uniqe One8 ms0077
Scenario: Changing Group's Name To Contain Invalid Symbols In Name Without Changing Description10 ms0088
Scenario: Changing Group's Name To Contain Permitted Symbols In Name Without Changing Description9 ms0077
Scenario: Changing Group's Name To Non-Unique One10 ms0099
Scenario: Changing Group's Name To Short One Without Changing Description8 ms0077
Scenario: Changing Group's Name To Unique One11 ms0077
Scenario: Changing Group's Name To a Long One Without Changing Description8 ms0077
Scenario: Changing Group's Name To a Too Long One Without Changing Description8 ms0088
Scenario: Changing Group's Name To a Too Short One Without Changing Description9 ms0088
Scenario: Changing Tag's Description To Non-Unique One7 ms0055
Scenario: Changing Tag's Description To Unique One6 ms0077
Scenario: Changing Tag's Name To Contain Invalid Symbols In Name Without Description6 ms0055
Scenario: Changing Tag's Name To Contain Permitted Symbols In Name Without Description6 ms0055
Scenario: Changing Tag's Name To Non-Unique One8 ms0066
Scenario: Changing Tag's Name To Short One Without Description7 ms0077
Scenario: Changing Tag's Name To Unique One7 ms0077
Scenario: Changing Tag's Name To a Long One Without Description8 ms0077
Scenario: Changing Tag's Name To a Too Long One Without Description6 ms0055
Scenario: Changing Tag's Name To a Too Short One Without Description10 ms0055
Scenario: Changing description of a nonexisting role4 ms0077
Scenario: Changing job description to non-unique one10 ms0077
Scenario: Changing job description to the long one12 ms0066
Scenario: Changing job description to unique one10 ms0066
Scenario: Changing job description to very short one13 ms0077
Scenario: Changing job name to a long one without description12 ms0077
Scenario: Changing job name to a too long one without description9 ms0055
Scenario: Changing job name to a too short one without description11 ms0066
Scenario: Changing job name to contain invalid symbols in name without description11 ms0044
Scenario: Changing job name to contain permitted symbols in name without description12 ms0055
Scenario: Changing job name to non-unique one11 ms0088
Scenario: Changing job name to short one without description10 ms0077
Scenario: Changing job name to unique one13 ms0099
Scenario: Changing name of a nonexisting role5 ms0077
Scenario: Changing role description to a valid one5 ms0066
Scenario: Changing role name so it is too long5 ms0066
Scenario: Changing role name to contain special character5 ms0044
Scenario: Changing role name to null6 ms0066
Scenario: Changing role's name to a valid one5 ms0066
Scenario: Channel info queries based on datastore channel filters19 ms005050
Scenario: ChannelInfo client ID and topic data based on the client id18 ms002828
Scenario: ChannelInfo client ID based on the account id13 ms002626
Scenario: ChannelInfo last published date17 ms003030
Scenario: ChannelInfo topic data based on the account id16 ms002626
Scenario: Check account properties10 ms0044
Scenario: Check the Device Connection Domain data seetting6 ms0022
Scenario: Check the database cache coherency14 ms003030
Scenario: Check the mapping for message semantic topics15 ms003030
Scenario: Check the message store29 ms002020
Scenario: Check the sanity of the Device Connection Domain data initialization6 ms0022
Scenario: Child account expires after parent11 ms0099
Scenario: Child account expires before parent11 ms001111
Scenario: Child account has null expiration date11 ms0099
Scenario: Client Id based ClientInfo data check15 ms002828
Scenario: Compare domain entries12 ms0033
Scenario: Connect to the system and publish some data0.17 sec002222
Scenario: Connection Service factory sanity checks6 ms0022
Scenario: Count access info entities in a specific scope45 ms002424
Scenario: Count access role entities by scope27 ms003939
Scenario: Count connections in empty scope9 ms0044
Scenario: Count connections in scope18 ms0055
Scenario: Count devices with a specific BIOS version6 ms0066
Scenario: Count domains in a blank database10 ms0044
Scenario: Count domains in the database11 ms0077
Scenario: Count events in empty scope12 ms0066
Scenario: Count groups11 ms001414
Scenario: Count groups in a blank database9 ms0055
Scenario: Count job items5 ms0077
Scenario: Count job items in wrong - empty - scope4 ms0088
Scenario: Count role permissions in specific scopes9 ms001818
Scenario: Count roles in specific scopes9 ms001515
Scenario: Count step definition items10 ms0044
Scenario: Count step definitions in wrong (empty) scope10 ms0011
Scenario: Count steps in the database4 ms001414
Scenario: Count user10 ms0066
Scenario: Counting created roles items in the DB5 ms0055
Scenario: Create a regular event31 ms0088
Scenario: Create a single device with an empty string for clientID9 ms0044
Scenario: Create a single device with null clientID value9 ms0044
Scenario: Create a valid job entry42 ms0066
Scenario: Create an event with a null scope ID23 ms0077
Scenario: Create and count several execution items for a job5 ms001111
Scenario: Create index with specific prefix7 ms001212
Scenario: Create multiple users8 ms0055
Scenario: Create regular access permissions18 ms002020
Scenario: Create same user in different accounts1.9 sec114015
Scenario: Create scheduler with correct end date5 ms2158
Scenario: Create scheduler with empty schedule name20 ms0088
Scenario: Create scheduler with end date before start date19 ms2169
Scenario: Create scheduler with invalid Retry Interval property14 ms0099
Scenario: Create scheduler with invalid cron job trigger property43 ms0099
Scenario: Create scheduler with invalid schedule name27 ms0088
Scenario: Create scheduler with short schedule name19 ms0088
Scenario: Create scheduler with too long schedule name18 ms0088
Scenario: Create scheduler with valid Retry Interval property15 ms0077
Scenario: Create scheduler with valid cron job trigger property21 ms0077
Scenario: Create scheduler with valid schedule name53 ms0066
Scenario: Create scheduler without Cron Job Trigger property39 ms0099
Scenario: Create scheduler without Retry Interval property13 ms0099
Scenario: Create scheduler without start date18 ms0077
Scenario: Create some regular role permissions8 ms0099
Scenario: Create user that already exist11 ms0077
Scenario: Create user that has more than DB allowed length14 ms0055
Scenario: Create user with short name15 ms0055
Scenario: Create user with special characters in his name11 ms0055
Scenario: Create with permissions22 ms001414
Scenario: Create with permissions and a role41 ms001717
Scenario: Create with permissions and a role in the wrong scope32 ms001515
Scenario: Creating 100 Sub-accounts While InfiniteChildAccounts Is Set To True10 ms0077
Scenario: Creating A Device With Disabled Status7 ms0077
Scenario: Creating A Device With Enabled Status7 ms0077
Scenario: Creating A Device With Long Display Name7 ms0077
Scenario: Creating A Device With Long Name6 ms0077
Scenario: Creating A Device With Name Containing Invalid Symbols10 ms0088
Scenario: Creating A Device With Name Containing Permitted Symbols9 ms0077
Scenario: Creating A Device With No Name7 ms0088
Scenario: Creating A Device With Non-unique Display Name8 ms0077
Scenario: Creating A Device With Non-unique Name8 ms001010
Scenario: Creating A Device With Short Display Name8 ms0077
Scenario: Creating A Device With Short Name7 ms0077
Scenario: Creating A Device With Too Long Display Name5 ms0088
Scenario: Creating A Device With Too Long Name9 ms0088
Scenario: Creating A Device With Unique Name7 ms0099
Scenario: Creating A Valid Account15 ms0055
Scenario: Creating An Account With Long Name9 ms0055
Scenario: Creating An Account With Long Organization Name8 ms0055
Scenario: Creating An Account With Non-unique Name7 ms0088
Scenario: Creating An Account With Numbers And Valid Symbols In Name9 ms0055
Scenario: Creating An Account With Short Name10 ms0055
Scenario: Creating An Account With Short Organization Name8 ms0055
Scenario: Creating An Account With Special Symbols In Organization Name9 ms0055
Scenario: Creating An Account With Too Long Organization Name10 ms0066
Scenario: Creating An Account With Unique Name8 ms0077
Scenario: Creating An Account With Wrong TLD Format In Email10 ms001010
Scenario: Creating An Account Without Email9 ms0066
Scenario: Creating An Account Without Name9 ms0066
Scenario: Creating An Account Without Ogranization Name8 ms0066
Scenario: Creating And Account Without "@" In Email9 ms0066
Scenario: Creating Devices And Than Setting Device Service So It Does Not Allow Devices10 ms001212
Scenario: Creating Devices And Then Changing Device Service Values9 ms001010
Scenario: Creating Devices Under Account That Allows Infinite Child Devices12 ms001010
Scenario: Creating Devices Under Account That Does Not Allow Devices12 ms0099
Scenario: Creating Devices Under Account That Has Limited Child Devices10 ms001313
Scenario: Creating Endpoint Non-Unique "Domain Name"7 ms0088
Scenario: Creating Endpoint Non-Unique "Port"5 ms0088
Scenario: Creating Endpoint Non-Unique "Schema"6 ms0099
Scenario: Creating Endpoint With "Domain Name" Only6 ms0066
Scenario: Creating Endpoint With "Port" Only6 ms0066
Scenario: Creating Endpoint With "Schema" Only6 ms0066
Scenario: Creating Endpoint With Disabled Secure Field7 ms0066
Scenario: Creating Endpoint With Enabled Secure Field5 ms0066
Scenario: Creating Endpoint With Invalid "Domain Name"6 ms0066
Scenario: Creating Endpoint With Invalid "Schema" containing symbols4 ms0066
Scenario: Creating Endpoint With Long "Domain Name"5 ms0055
Scenario: Creating Endpoint With Max Length "Port"7 ms0055
Scenario: Creating Endpoint With NULL parameters10 ms0066
Scenario: Creating Endpoint With Schema Containing "http://"6 ms0066
Scenario: Creating Endpoint With Schema Containing "https://"9 ms0066
Scenario: Creating Endpoint With Short "Domain Name"6 ms0066
Scenario: Creating Endpoint With Short "Schema"7 ms0066
Scenario: Creating Endpoint With Small Number "Port"5 ms0066
Scenario: Creating Endpoint With Too Big "Port"5 ms0066
Scenario: Creating Endpoint With Too Long "Domain Name"6 ms0066
Scenario: Creating Endpoint With Too Long "Schema"8 ms0066
Scenario: Creating Endpoint Without "Domain Name"7 ms0066
Scenario: Creating Endpoint Without "Port"8 ms0066
Scenario: Creating Endpoint Without "Schema"7 ms0066
Scenario: Creating Endpoint Without Long "Schema"8 ms0055
Scenario: Creating Endpoint with invalid "Schema" which contains only numbers5 ms0066
Scenario: Creating Group Invalid Symbols In Name Without Description8 ms0077
Scenario: Creating Group With Invalid Symbols In Name With Valid Description9 ms0077
Scenario: Creating Group With Long Name With Valid Description9 ms0066
Scenario: Creating Group With Long Name Without Description9 ms0066
Scenario: Creating Group With Numbers In Name With Valid Description11 ms0088
Scenario: Creating Group With Permitted Symbols And Numbers In Name Without Description11 ms0066
Scenario: Creating Group With Permitted Symbols In Name With Valid Description9 ms0066
Scenario: Creating Group With Short Name With Valid Description9 ms0066
Scenario: Creating Group With Short Name Without Description10 ms0066
Scenario: Creating Group With Too Long Name With Valid Description9 ms0077
Scenario: Creating Group With Too Long Name Without Description8 ms0077
Scenario: Creating Group With Too Short Name With Valid Description13 ms0077
Scenario: Creating Group With Too Short Name Without Description8 ms0077
Scenario: Creating Group Without a Name And With Valid Description8 ms0077
Scenario: Creating Group Without a Name And Without Description11 ms0077
Scenario: Creating Groups And Than Setting Group Service So It Does Not Allow Groups12 ms001111
Scenario: Creating Groups And Then Changing InfiniteChildGroups To False And Set MaxNumberChildGroups11 ms001010
Scenario: Creating Groups Under Account That Allows Infinite Child Groups9 ms0099
Scenario: Creating Groups Under Account That Does Not Allow Groups9 ms0099
Scenario: Creating Groups Under Account That Has Limited Child Groups8 ms001212
Scenario: Creating Jobs And Than Setting Job Service So It Does Not Allow Jobs8 ms001212
Scenario: Creating Jobs And Then Changing Job Service Values12 ms001010
Scenario: Creating Jobs Under Account That Allows Infinite Child Devices12 ms001010
Scenario: Creating Jobs Under Account That Does Not Allow Jobs8 ms0099
Scenario: Creating Jobs Under Account That Has Limited Child Jobs9 ms001313
Scenario: Creating Non-Unique Group With Valid Description10 ms0088
Scenario: Creating Non-Unique Tag With Valid Description9 ms0055
Scenario: Creating Non-unique Group Without Description11 ms0088
Scenario: Creating Non-unique Tag Without Description15 ms0044
Scenario: Creating Roles And Than Setting Role Service So It Does Not Allow Roles10 ms001111
Scenario: Creating Roles And Then Changing Role Service Values11 ms001010
Scenario: Creating Roles Under Account That Allows Infinite Child Roles8 ms001010
Scenario: Creating Roles Under Account That Does Not Allow Roles12 ms0099
Scenario: Creating Roles Under Account That Has Limited Child Roles9 ms001212
Scenario: Creating Sub-accounts When InfiniteChildAccoounts Is Set To False And maxNumberChildAccounts Is Set41 ms001313
Scenario: Creating Sub-accounts When InfiniteChildAccoounts Is Set To True And maxNumberChildAccounts Is Set9 ms001414
Scenario: Creating Sub-accounts When InfiniteChildAccounts Is Set To False7 ms0099
Scenario: Creating Sub-accounts when InfiniteChildAccounts Is Set To True11 ms001212
Scenario: Creating Tag With Invalid Symbols In Name With Valid Description11 ms0044
Scenario: Creating Tag With Invalid Symbols In Name Without Description12 ms0044
Scenario: Creating Tag With Long Name With Valid Description29 ms0044
Scenario: Creating Tag With Long Name Without Description12 ms0044
Scenario: Creating Tag With Numbers In Name With Valid Description8 ms0044
Scenario: Creating Tag With Numbers In Name Without Description13 ms0044
Scenario: Creating Tag With Permitted Symbols In Name With Valid Description8 ms0044
Scenario: Creating Tag With Permitted Symbols In Name Without Description11 ms0044
Scenario: Creating Tag With Short Name With Valid Description8 ms0044
Scenario: Creating Tag With Short Name Without Description16 ms0044
Scenario: Creating Tag With Too Long Name With Valid Description8 ms0044
Scenario: Creating Tag With Too Long Name Without Description31 ms0044
Scenario: Creating Tag With Too Short Name With Valid Description9 ms0044
Scenario: Creating Tag With Too Short Name Without Description33 ms0044
Scenario: Creating Tag Without a Name And With Valid Description8 ms0044
Scenario: Creating Tag Without a Name And Without Description11 ms0044
Scenario: Creating Tags And Than Setting Tag Service So It Does Not Allow Tags8 ms001111
Scenario: Creating Tags And Then Changing Tag Service Values7 ms001010
Scenario: Creating Tags Under Account That Allows Infinite Child Devices10 ms001010
Scenario: Creating Tags Under Account That Does Not Allow Tags9 ms0099
Scenario: Creating Tags Under Account That Has Limited Child Tags11 ms001212
Scenario: Creating Unique Group With Long Description8 ms0066
Scenario: Creating Unique Group With Non-unique Description11 ms0077
Scenario: Creating Unique Group With Short Description11 ms0066
Scenario: Creating Unique Group With Unique Description12 ms0066
Scenario: Creating Unique Group Without Description8 ms0066
Scenario: Creating Unique Tag With Long Description12 ms0044
Scenario: Creating Unique Tag With Non-unique Description10 ms0055
Scenario: Creating Unique Tag With Short Description7 ms0044
Scenario: Creating Unique Tag With Unique Description9 ms0044
Scenario: Creating Unique Tag Without Description51 ms0044
Scenario: Creating Users And Than Setting User Service So It Does Not Allow Users9 ms001111
Scenario: Creating Users And Then Changing User Service Values8 ms001010
Scenario: Creating Users Under Account That Allows Infinite Child Users7 ms001010
Scenario: Creating Users Under Account That Does Not Allow Users8 ms0099
Scenario: Creating Users Under Account That Has Limited Child Users8 ms001212
Scenario: Creating Valid Endpoint9 ms0066
Scenario: Creating a Access Group with invalid special symbols in name1 ms0044
Scenario: Creating a Device With Permitted Symbols in its Display Name8 ms0077
Scenario: Creating a Device With Unique Display Name8 ms0088
Scenario: Creating a job with name only31 ms0066
Scenario: Creating a job with null name25 ms0055
Scenario: Creating a job without name with valid description14 ms0055
Scenario: Creating a new PASSWORD Credential meeting a custom length requirement13 ms0044
Scenario: Creating a new PASSWORD Credential meeting the standard length requirement40 ms0033
Scenario: Creating a new PASSWORD Credential not meeting a custom length requirement12 ms0055
Scenario: Creating a new PASSWORD Credential not meeting the standard length requirement26 ms0044
Scenario: Creating a role name with allowed symbols in its name4 ms0055
Scenario: Creating a role with 255 characters long description6 ms0055
Scenario: Creating a role with a name and description that contain digits only5 ms0055
Scenario: Creating a role with forbidden symbols in its name0 ms0044
Scenario: Creating a role with name only5 ms0055
Scenario: Creating a role with null name6 ms0055
Scenario: Creating a role with regular name and very short description" as description cannot be too short, as even one character is enough5 ms0055
Scenario: Creating a role with special characters in the description5 ms0044
Scenario: Creating a role with the name that contains digits5 ms0055
Scenario: Creating a role with too long name4 ms0055
Scenario: Creating a role with too short name6 ms0055
Scenario: Creating a role with valid name and with too long description7 ms0033
Scenario: Creating a role wtih 255 characters long name5 ms0055
Scenario: Creating a single device with case sensitive clientID9 ms0055
Scenario: Creating a single device with clientID that contains 255 characters9 ms0055
Scenario: Creating a single device with clientID that contains 256 characters9 ms0044
Scenario: Creating a single device with clientID that contains invalid character8 ms0044
Scenario: Creating a single device with clientID that contains invalid characters13 ms0044
Scenario: Creating a single device with spaces in clientID8 ms0055
Scenario: Creating a single device with valid clientID8 ms0055
Scenario: Creating a valid Access Group with numbers in name15 ms0055
Scenario: Creating a valid Access Group with only numbers in name7 ms0055
Scenario: Creating a valid Access Group with unique name11 ms0055
Scenario: Creating a valid Access Group with valid special symbols in name7 ms0055
Scenario: Creating a valid role7 ms0055
Scenario: Creating an Access Group with empty name9 ms0044
Scenario: Creating an Access Group with long name9 ms0055
Scenario: Creating an Access Group with short name8 ms0055
Scenario: Creating an Access Group with too long name8 ms0044
Scenario: Creating an Access Group with too short name8 ms0044
Scenario: Creating an Access Group without name and with description5 ms0044
Scenario: Creating and Deleting Endpoint Two Times12 ms002525
Scenario: Creating index with regular user8 ms002525
Scenario: Creating job with invalid symbols in name without description11 ms0044
Scenario: Creating job with long name and valid description14 ms0066
Scenario: Creating job with long name without description19 ms0066
Scenario: Creating job with numbers in name and valid description13 ms0066
Scenario: Creating job with numbers in name without description19 ms0066
Scenario: Creating job with permitted symbols in name without description18 ms0033
Scenario: Creating job with short name and valid job description13 ms0066
Scenario: Creating job with short name without description20 ms0066
Scenario: Creating job with too long name and valid description13 ms0055
Scenario: Creating job with too long name without description16 ms0055
Scenario: Creating job with too short name and valid description27 ms0055
Scenario: Creating job with too short name without description39 ms0055
Scenario: Creating job without name and without description36 ms0055
Scenario: Creating new device and tagging it with specific Tag9 ms001414
Scenario: Creating new device, tagging it with specific Tag and then deleting this Tag8 ms001616
Scenario: Creating non-unique Access Group8 ms0055
Scenario: Creating non-unique Access Group with unique description7 ms0055
Scenario: Creating non-unique job name with valid job description13 ms0077
Scenario: Creating two device with the same clientID11 ms0055
Scenario: Creating two indexes with daily index9 ms001717
Scenario: Creating two indexes with hourly index11 ms001717
Scenario: Creating two indexes with weekly index9 ms001717
Scenario: Creating two roles with the same description6 ms0066
Scenario: Creating two roles with the same name4 ms0077
Scenario: Creating unique Access Group with long description6 ms0055
Scenario: Creating unique Access Group with non-unique description7 ms0066
Scenario: Creating unique Access Group with numbers in description7 ms0055
Scenario: Creating unique Access Group with only numbers in description8 ms0055
Scenario: Creating unique Access Group with short description6 ms0055
Scenario: Creating unique Access Group with special symbols in description23 ms2114
Scenario: Creating unique Access Group with unique description6 ms0055
Scenario: Creating unique job with long description16 ms0066
Scenario: Creating unique job with non-unique description17 ms001010
Scenario: Creating unique job with short description26 ms0066
Scenario: Creating user47 ms0055
Scenario: Creation of access role with neither acess info and role entities12 ms001212
Scenario: Creation of access role without an acess info entity28 ms001212
Scenario: D1 Device publish to CTRL_ACC_REPLY6 ms0099
Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI8 ms0099
Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed8 ms0099
Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed6 ms0077
Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY13 ms0099
Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY5 ms0099
Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account5 ms0099
Scenario: D5 Device subscribe - publish - admin on CTRL_ACC5 ms0099
Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI6 ms0099
Scenario: D7 Device publish to ACL_DATA_ACC is not allowed6 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 allowed6 ms0088
Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed13 ms0099
Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI7 ms0099
Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed6 ms0099
Scenario: DM13 Data manage subscribe on ACL_CTRL_ACC_NOTIFY is not allowed7 ms0088
Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY7 ms0099
Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY8 ms0099
Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account7 ms0099
Scenario: DM5 Data manage publish to CTRL_ACC is not allowed6 ms0099
Scenario: DM6 Data manage create sub-topic on CTRL_ACC is not allowed10 ms0099
Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed5 ms0088
Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI7 ms0099
Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC5 ms0099
Scenario: DV1 Data view publish to CTRL_ACC_REPLY6 ms0099
Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed6 ms0099
Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed6 ms001010
Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed6 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 allowed6 ms0099
Scenario: DV17 Data view subscribe on ACL_CTRL_ACC_NOTIFY is not allowed7 ms0088
Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY9 ms0099
Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY6 ms0099
Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account6 ms0099
Scenario: DV5 Data view publish to CTRL_ACC is not allowed9 ms0099
Scenario: DV6 Data view create sub-topic on CTRL_ACC is not allowed5 ms0099
Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed8 ms0088
Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI9 ms0099
Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed6 ms0099
Scenario: Decreasing MaxNumberChildAccounts When Sub-accounts Are Already Created8 ms001515
Scenario: Delete Kapua system user23 ms0055
Scenario: Delete a access info entity with permissions and roles46 ms001717
Scenario: Delete a connection from the database6 ms0088
Scenario: Delete a group from the database9 ms001010
Scenario: Delete a group from the database - Unknown group ID8 ms0066
Scenario: Delete a job6 ms001111
Scenario: Delete a job execution item6 ms0088
Scenario: Delete a job execution item twice6 ms0099
Scenario: Delete a job twice5 ms001010
Scenario: Delete a non existent event17 ms0077
Scenario: Delete a non existing connection9 ms0077
Scenario: Delete a non existing permission entity30 ms001616
Scenario: Delete a non existing role entry10 ms001111
Scenario: Delete a non-existing step5 ms001212
Scenario: Delete a nonexistent domain10 ms0055
Scenario: Delete a step definition10 ms0088
Scenario: Delete a step definition twice10 ms0077
Scenario: Delete access role from user35 ms001212
Scenario: Delete an access info entity twice49 ms001111
Scenario: Delete an access info entity using the wrong scope ID40 ms001111
Scenario: Delete an existing access info entity13 ms001212
Scenario: Delete an existing access permission entity18 ms001515
Scenario: Delete an existing access role entry12 ms002222
Scenario: Delete an existing account9 ms0055
Scenario: Delete an existing device from the registry6 ms0044
Scenario: Delete an existing event12 ms0099
Scenario: Delete an existing role10 ms001010
Scenario: Delete an existing role twice13 ms001616
Scenario: Delete an existing step6 ms001111
Scenario: Delete items based on query results18 ms008484
Scenario: Delete items by date ranges1.1 sec00132132
Scenario: Delete items by the datastore ID15 ms006666
Scenario: Delete middle child expiration8 ms001515
Scenario: Delete nonexisting account11 ms0044
Scenario: Delete nonexisting role permission7 ms001313
Scenario: Delete parent expiration9 ms001414
Scenario: Delete permissions from role22 ms001818
Scenario: Delete role permissions8 ms001010
Scenario: Delete scheduler11 ms0088
Scenario: Delete scheduler which doesn't exist13 ms0055
Scenario: Delete the Kapua system account7 ms0055
Scenario: Delete the last created domain entry13 ms0088
Scenario: Delete user13 ms0066
Scenario: Delete user that doesn't exist12 ms0055
Scenario: Deleting "Cron Schedule" Triggering10 ms001313
Scenario: Deleting "Device Schedule" Triggering10 ms001111
Scenario: Deleting "Interval Schedule" Triggering9 ms001313
Scenario: Deleting Device With Disabled Status7 ms001010
Scenario: Deleting Device With Enabled Status6 ms001010
Scenario: Deleting Endpoint Domain Name And Leaving it Empty5 ms0088
Scenario: Deleting Endpoint Which Does Not Exist5 ms0066
Scenario: Deleting Existing Group8 ms0088
Scenario: Deleting Existing Group And Creating It Again With Same Name8 ms001212
Scenario: Deleting Existing Tag And Creating It Again With Same Name7 ms0077
Scenario: Deleting Group's Name And Leaving It Empty Without Changing Description11 ms0088
Scenario: Deleting Non-Existent Tag6 ms0077
Scenario: Deleting Tag From Device32 ms0088
Scenario: Deleting Tag's Name And Leaving It Empty Without Description6 ms0055
Scenario: Deleting Unexisitng Group8 ms001111
Scenario: Deleting a Permission14 ms002121
Scenario: Deleting a non-existing Access Group5 ms0066
Scenario: Deleting a role twice5 ms0077
Scenario: Deleting admin role21 ms0077
Scenario: Deleting an existing Access Group5 ms0055
Scenario: Deleting an existing Access Group and creating it again with the same name5 ms0077
Scenario: Deleting an existing role5 ms0066
Scenario: Deleting default permissions from admin role21 ms001212
Scenario: Deleting existing tag6 ms0099
Scenario: Deleting role after adding it to user22 ms001414
Scenario: Deleting role after it has been added to user in child account26 ms001616
Scenario: Deleting user in account that is higher in hierarchy1.8 sec122023
Scenario: Deleting user in account that is lower in hierarchy1.8 sec123024
Scenario: Device connection update6 ms0077
Scenario: Device factory sanity checks6 ms0022
Scenario: Device queries6 ms001010
Scenario: Device query - find by BIOS version19 ms0077
Scenario: Domain entry query12 ms0055
Scenario: Domain with null actions11 ms0055
Scenario: Domain with null name11 ms0055
Scenario: Domains with duplicate names12 ms0088
Scenario: Duplicate group name in root scope9 ms001010
Scenario: Duplicate role names10 ms0077
Scenario: Editing Access Group description to description with numbers6 ms0055
Scenario: Editing Access Group description to description with only numbers5 ms0055
Scenario: Editing Access Group description to description with special symbols34 ms0044
Scenario: Editing Access Group description to long description5 ms0055
Scenario: Editing Access Group description to non-unique one6 ms0055
Scenario: Editing Access Group description to short description16 ms0055
Scenario: Editing Access Group description to unique one6 ms0077
Scenario: Editing Access Group name to a long one6 ms0077
Scenario: Editing Access Group name to a too long one6 ms0055
Scenario: Editing Access Group name to empty name6 ms0055
Scenario: Editing Access Group name to name that contains numbers5 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 name1 ms0055
Scenario: Editing Access Group name to name with valid special symbols5 ms0077
Scenario: Editing Access Group name to non-unique one5 ms0066
Scenario: Editing Access Group name to short one9 ms0077
Scenario: Editing Access Group name to too short one5 ms0055
Scenario: Editing Access Group name to valid one6 ms0077
Scenario: Editing Endpoint Domain Name So It Contains Invalid Symbols5 ms0088
Scenario: Editing Endpoint Domain Name So It Contains Only Numbers8 ms0088
Scenario: Editing Endpoint Domain Name So It Has Max Value8 ms0077
Scenario: Editing Endpoint Domain Name So It Has Min Value8 ms0077
Scenario: Editing Endpoint Domain Name To Non-unique Value5 ms0099
Scenario: Editing Endpoint Domain Name To Unique Value8 ms0077
Scenario: Editing Endpoint Port To Non-unique Value6 ms0099
Scenario: Editing Endpoint Port To Unique Value6 ms0077
Scenario: Editing Endpoint Schema And Leaving It Empty6 ms0088
Scenario: Editing Endpoint Schema So It Contains "http://"8 ms0088
Scenario: Editing Endpoint Schema So It Contains "https://"6 ms0088
Scenario: Editing Endpoint Schema So It Contains Invalid Symbols6 ms0088
Scenario: Editing Endpoint Schema So It Contains Only Numbers7 ms0088
Scenario: Editing Endpoint Schema So It Has Max Length5 ms0077
Scenario: Editing Endpoint Schema So It Has Min Length12 ms0077
Scenario: Editing Endpoint Schema To Non-unique Value5 ms0088
Scenario: Editing Endpoint Schema To Unique Value7 ms0077
Scenario: Editing Endpoint Secure Field To Non-unique Value4 ms0099
Scenario: Editing Endpoint Secure Field To Unique Value6 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 Description9 ms0077
Scenario: Editing Tag's Name To Contain Numbers Without Description6 ms0077
Scenario: Empty query results are supported11 ms0088
Scenario: Event factory sanity checks14 ms0022
Scenario: Event service domain check9 ms0022
Scenario: Every account must have the default configuration items11 ms0033
Scenario: Execute possible docker steps to show its usage5 ms231033
Scenario: Executing Job And Then Restarting Device15 ms004545
Scenario: Executing Job When Device Connected After End Date And Time15 ms003939
Scenario: Executing Job When Device Connected After The Specified Start Date And Time19 ms003838
Scenario: Executing Job When Device Connected Before End Date And Time17 ms003939
Scenario: Executing Job When Device Connected Before The Specified Start Date And Time16 ms003737
Scenario: Executing Job Without Steps33 ms004040
Scenario: Extra long continuous test with multiple subscenarios with LOOSE default connection mode26 ms00419419
Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode25 ms00397397
Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode and no previously defined devices14 ms00305305
Scenario: Find a connection by its IDs6 ms0066
Scenario: Find a connection by its client ID7 ms0066
Scenario: Find a group entry in the database10 ms0099
Scenario: Find a non existing event15 ms0066
Scenario: Find account by Id11 ms0044
Scenario: Find account by Ids10 ms0044
Scenario: Find account by name10 ms0044
Scenario: Find account by random Id11 ms0033
Scenario: Find all child accounts39 ms0033
Scenario: Find an access info entity19 ms001111
Scenario: Find an access info entity by user ID42 ms001010
Scenario: Find an event by its ID18 ms0066
Scenario: Find an existing access role entity12 ms001313
Scenario: Find by name nonexisting account9 ms0033
Scenario: Find correct number of messages by corresponding metric0.34 sec005858
Scenario: Find device by client ID8 ms0033
Scenario: Find device by registry ID10 ms0044
Scenario: Find last created permission14 ms001212
Scenario: Find multiple users6 ms0055
Scenario: Find role by ID10 ms0077
Scenario: Find self account by id11 ms001111
Scenario: Find self account by id and scope id9 ms001111
Scenario: Find self account by name8 ms001111
Scenario: Find the last created domain entry10 ms0055
Scenario: Find user by id42 ms0055
Scenario: Find user by its email17 ms0066
Scenario: Find user by its phone number6 ms0066
Scenario: Find user by name14 ms0055
Scenario: Find user by name that doesn't exist7 ms0033
Scenario: Find user with id and scope id that doesn't exist12 ms0033
Scenario: Finding all messages by selecting all metrics0.31 sec004040
Scenario: Finding correct number of messages by corresponding two metrics0.49 sec005252
Scenario: Finding messages with incorrect metric parameters3.2 sec007272
Scenario: Finding user by expiration date in the future7 ms0055
Scenario: Finding user by expiration date in the past9 ms0066
Scenario: Finding user by expiration date in the present7 ms0066
Scenario: Generic connection query7 ms0088
Scenario: Get metadata8 ms0033
Scenario: Group with a null name8 ms0077
Scenario: Handle account creation58 ms0033
Scenario: Handle duplicate account names52 ms0055
Scenario: Handle null account name12 ms0044
Scenario: Handling of 2 birth messages7 ms001212
Scenario: Handling of a disconnect message from a non existing device8 ms001010
Scenario: Have Two Devices in The Same Group Without Description28 ms001313
Scenario: I try to find a non-existing connection7 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 inclusive7 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 login4 ms001313
Scenario: If user expiration date is before today, user can not login9 ms001313
Scenario: If user expiration date is today, user can not login because expiration date was reached7 ms001313
Scenario: If user expiration date is tomorrow, user can login5 ms001212
Scenario: Init Security Context for all scenarios2.7 sec114648
Scenario: Installing a package12 ms001313
Scenario: Interval Job" Schedule With Too Long Name7 ms001111
Scenario: It must be possible to query for specific entries in the role database8 ms0088
Scenario: It should not be possible to change the configuration items7 ms0055
Scenario: Job execution factory sanity checks4 ms0022
Scenario: Job factory sanity checks3 ms0033
Scenario: Job with a duplicate name6 ms0099
Scenario: Job with a null name5 ms0088
Scenario: Job with a null scope ID6 ms0099
Scenario: Job with an empty name4 ms0088
Scenario: List Endpoints Created From Sub-Account5 ms223126
Scenario: List Endpoints From "kapua-sys" Account4 ms24511
Scenario: List Endpoints From Sub-Account Of Another Sub-Account4 ms223126
Scenario: List Endpoints From Sub-account6 ms212115
Scenario: MetricsInfo client ID and topic data based on the client id15 ms003434
Scenario: MetricsInfo last published date15 ms004848
Scenario: Modify a role that was deleted10 ms0099
Scenario: Modify an existing account12 ms0044
Scenario: Modify last child expiration so that it still expires before parent8 ms001414
Scenario: Modify middle child expiration so that it still expires before parent12 ms001414
Scenario: Modify middle child expiration to outlive parent9 ms001515
Scenario: Modify nonexisting account9 ms0066
Scenario: Modify parent expiration so that it still expires after child10 ms001414
Scenario: Modify parent expiration to before child expiration9 ms001515
Scenario: Modifying Sub-account of a different parent account15 ms002525
Scenario: Moving Device From One Group With Description to Another8 ms001414
Scenario: Nameless role entry10 ms0077
Scenario: Negative scenario when client connects twice with same client id18 ms001111
Scenario: New connection with reserved ID3.3 sec003434
Scenario: Permission factory sanity checks8 ms0033
Scenario: Positive scenario without stealing link19 ms001212
Scenario: Query based on message ordering14 ms002020
Scenario: Query based on metrics ordering15 ms002020
Scenario: Query before schema search10 ms008282
Scenario: Query for a specific group by name8 ms001616
Scenario: Query for all the access info entities of a specific user37 ms001818
Scenario: Query for all the access info entities of an invalid user12 ms001010
Scenario: Query for executions of a specific job5 ms001818
Scenario: Query for jobs with specified name6 ms0099
Scenario: Query for step definitions9 ms0077
Scenario: Query user10 ms0066
Scenario: Querying Other Items With All Account Permissions16 ms003939
Scenario: Regular connection7 ms0077
Scenario: Regular creation of Access Role entity27 ms001414
Scenario: Regular domain13 ms0055
Scenario: Regular group in random scope8 ms0077
Scenario: Regular group in root scope9 ms0077
Scenario: Regular job creation5 ms001010
Scenario: Regular job execution creation6 ms0077
Scenario: Regular role creation8 ms0099
Scenario: Regular step creation5 ms001111
Scenario: Regular step definition creation10 ms0077
Scenario: Regular step definition with a property list12 ms0044
Scenario: Reset Security Context for all scenarios2.1 sec114648
Scenario: Restarting a job with Asset Write and Bundle Start steps21 ms002828
Scenario: Restarting a job with Command Execution and Bundle Start steps19 ms002828
Scenario: Restarting a job with Configuration Put and Bundle Start steps21 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 times98 ms003333
Scenario: Restarting a job with invalid Configuration Put step two times23 ms003636
Scenario: Restarting a job with invalid Package Install step and multiple devices two times0.15 sec003131
Scenario: Restarting a job with invalid Package Install step two times26 ms003434
Scenario: Restarting a job with invalid Package Uninstall step and multiple devices two times74 ms003232
Scenario: Restarting a job with invalid Package Uninstall step two times25 ms003434
Scenario: Restarting a job with valid Configuration Put step and multiple devices two times70 ms003333
Scenario: Restarting a job with valid Configuration Put step two times27 ms003636
Scenario: Restarting a job with valid Package Install step and multiple devices two times0.17 sec002929
Scenario: Restarting a job with valid Package Install step two times25 ms003434
Scenario: Restarting a job with valid Package Uninstall step and multiple devices two times23 ms003030
Scenario: Restarting a job with valid Package Uninstall step two times24 ms003232
Scenario: Restarting job With invalid Asset Write and multiple two times71 ms003434
Scenario: Restarting job With valid Asset Write step two times62 ms003636
Scenario: Restarting job with Asset Write and Bundle Start steps and multiple devices26 ms003131
Scenario: Restarting job with Asset Write step27 ms002525
Scenario: Restarting job with Asset Write step and multiple devices17 ms002828
Scenario: Restarting job with Bundle Start step22 ms002525
Scenario: Restarting job with Bundle Start step and multiple devices22 ms002727
Scenario: Restarting job with Bundle Stop and Bundle Start step and multiple devices0.16 sec003131
Scenario: Restarting job with Bundle Stop and Bundle Start steps20 ms002929
Scenario: Restarting job with Bundle Stop step19 ms002525
Scenario: Restarting job with Bundle Stop step and multiple devices34 ms002727
Scenario: Restarting job with Command Execution and Bundle Start steps and multiple devices19 ms003131
Scenario: Restarting job with Command Execution step28 ms002525
Scenario: Restarting job with Command Execution step and multiple devices24 ms002727
Scenario: Restarting job with Configuration Put and Bundle Start steps and multiple devices23 ms003131
Scenario: Restarting job with Configuration Put step24 ms002525
Scenario: Restarting job with Configuration Put step and multiple devices18 ms002727
Scenario: Restarting job with Package Download/Install and Bundle Start steps and multiple devices53 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 device22 ms003131
Scenario: Restarting job with Package Uninstall step19 ms002525
Scenario: Restarting job with Package Uninstall step and multiple device22 ms002727
Scenario: Restarting job with invalid Asset Write step two times39 ms003636
Scenario: Restarting job with invalid Bundle Start and Bundle Stop steps and multiple devices two times19 ms004141
Scenario: Restarting job with invalid Bundle Start and Bundle Stop steps two times28 ms004343
Scenario: Restarting job with invalid Bundle Start step and multiple devices two times49 ms003535
Scenario: Restarting job with invalid Bundle Start step two times37 ms003737
Scenario: Restarting job with invalid Bundle Stop step and multiple devices two times75 ms003535
Scenario: Restarting job with invalid Bundle Stop step two times73 ms003737
Scenario: Restarting job with invalid Command Execution and Package Install step two times76 ms003636
Scenario: Restarting job with invalid Command Execution and Package Install steps and multiple devices two times25 ms003737
Scenario: Restarting job with invalid Command Execution step and multiple devices two times58 ms003131
Scenario: Restarting job with invalid Command Execution step two times86 ms003232
Scenario: Restarting job with invalid Configuration Put And Command Execution steps two times23 ms003838
Scenario: Restarting job with invalid Configuration Put and Command Execution steps and multiple devices two times42 ms003737
Scenario: Restarting job with invalid Package Uninstall and Asset Write steps and multiple devices two times0.16 sec003838
Scenario: Restarting job with invalid Package Uninstall and Asset Write steps two times43 ms004040
Scenario: Restarting job with two Bundle Start steps25 ms002929
Scenario: Restarting job with two Bundle Start steps and multiple devices21 ms003131
Scenario: Restarting job with valid Asset Write step and multiple devices two times29 ms003434
Scenario: Restarting job with valid Bundle Start And Bundle Stop steps two times19 ms004343
Scenario: Restarting job with valid Bundle Start and Bundle Stop steps and multiple devices two times96 ms004141
Scenario: Restarting job with valid Bundle Start step and multiple devices two times86 ms003535
Scenario: Restarting job with valid Bundle Start step two times25 ms003737
Scenario: Restarting job with valid Bundle Stop step and multiple devices two times61 ms003535
Scenario: Restarting job with valid Bundle Stop step two times72 ms003737
Scenario: Restarting job with valid Command Execution and Package Install steps and multiple devices two times29 ms003333
Scenario: Restarting job with valid Command Execution and Package Install steps two times87 ms003434
Scenario: Restarting job with valid Command Execution step and multiple devices two times0.13 sec003131
Scenario: Restarting job with valid Command Execution step two times0.11 sec003232
Scenario: Restarting job with valid Configuration Put and Command Execution steps and multiple devices two times79 ms003737
Scenario: Restarting job with valid Configuration Put and Command Execution steps two times80 ms003838
Scenario: Restarting job with valid Package Uninstall and Asset Write steps and multiple devices two times95 ms003636
Scenario: Restarting job with valid Package Uninstall and Asset Write steps two times79 ms003838
Scenario: Role creator sanity checks6 ms0022
Scenario: Role entry with no actions9 ms0066
Scenario: Role object equality check10 ms0022
Scenario: Role service related objects sanity checks8 ms0044
Scenario: Search By Client ID And Get Multiple Matches23 ms003737
Scenario: Search By Client ID And Get No Matches7 ms001010
Scenario: Search By Client ID And Get One Match6 ms0088
Scenario: Search By Client ID and Display Name8 ms001212
Scenario: Search By Client ID and Serial Number8 ms001212
Scenario: Search By Client ID and Status7 ms001212
Scenario: Search By Client ID, Display Name and Serial Number7 ms001212
Scenario: Search By Client ID, Display Name and Status7 ms001212
Scenario: Search By Client ID, Display Name, Serial Number and Status6 ms001212
Scenario: Search By Device Status And Get No Matches8 ms0088
Scenario: Search By Device's Display Name And Get One Match6 ms0088
Scenario: Search By Display Name and Serial Number6 ms001212
Scenario: Search By Display Name and Status8 ms001212
Scenario: Search By Full Client ID And Get One Match7 ms001010
Scenario: Search By Non-existing Client ID And Get No Matches6 ms0088
Scenario: Search By One Letter Of Display Name6 ms0088
Scenario: Search By One Letter Of Serial Number7 ms001212
Scenario: Search By Serial Number And Get Multiple Matches7 ms001414
Scenario: Search By Serial Number And Get No Matches7 ms001010
Scenario: Search By Serial Number And Get One Match9 ms001111
Scenario: Search By Serial Number and Status7 ms001212
Scenario: Search By Serial Number, Display Name and Status8 ms001212
Scenario: Search By Specific Serial Number7 ms001010
Scenario: Search By Status And Get Multiple Matches8 ms001010
Scenario: Search by Device Status And Get One Match6 ms001010
Scenario: Search for a non existent client ID6 ms0066
Scenario: Search for an access info entity by an incorrect user ID45 ms001111
Scenario: Search the role database for a random ID8 ms0077
Scenario: Send BIRTH message and then DC message53 ms001515
Scenario: Send BIRTH message and then DC message while broker ip is NOT set16 ms0066
Scenario: Send BIRTH message and then DC message while broker ip is set by System27 ms0088
Scenario: Send BIRTH message and then DC message while broker ip is set by config file32 ms0088
Scenario: Set a correct minimum for password length38 ms0033
Scenario: Set an incorrect minimum for password length12 ms0066
Scenario: Set environment variables0.23 sec006161
Scenario: Setting InfiniteChildAccounts To False And Increasing MaxNumberChildAccounts When Sub-accounts Are Already Created11 ms001414
Scenario: Setting InfiniteChildAccounts To False When Sub-accounts Are Already Created12 ms001515
Scenario: Setting InfiniteChildAccounts To True And Decreasing MaxNumberChildAccounts When Sub-accounts Are Already Created11 ms001414
Scenario: Setting Lockout Duration To 0 Seconds11 ms001515
Scenario: Setting Lockout Duration To Negative Value9 ms0077
Scenario: Setting Max Failures To 011 ms001515
Scenario: Setting Max Failures To 110 ms001515
Scenario: Setting Max Failures To 10010 ms001515
Scenario: Setting Max Failures To Negative Value8 ms0077
Scenario: Setting Reset After Login Counter To 0 Seconds11 ms001717
Scenario: Setting Reset After Login Counter To Negative Value12 ms0077
Scenario: Setting configuration without mandatory items must raise an error8 ms0055
Scenario: Simple Jetty with rest-api war4 ms2316
Scenario: Simple create54 ms001111
Scenario: Simple positive scenario for creating daily index8 ms001414
Scenario: Simple positive scenario for creating default - weekly index11 ms001212
Scenario: Simple positive scenario for creating hourly index9 ms001414
Scenario: Start Jetty server for all scenarios3 ms2002
Scenario: Start broker for all scenarios0.44 sec004444
Scenario: Start datastore for all scenarios0.29 sec202830
Scenario: Start event broker for all scenarios2.1 sec115052
Scenario: Starting a job with Asset Write and Bundle Start steps18 ms003636
Scenario: Starting a job with Asset Write step34 ms002525
Scenario: Starting a job with Bundle Start step25 ms003434
Scenario: Starting a job with Bundle Stop and Bundle Start steps19 ms003939
Scenario: Starting a job with Bundle Stop step29 ms003535
Scenario: Starting a job with Command Execution and Bundle Start steps16 ms003737
Scenario: Starting a job with Command Execution step19 ms002525
Scenario: Starting a job with Configuration Put and Bundle Start steps17 ms003737
Scenario: Starting a job with Configuration Put step20 ms002525
Scenario: Starting a job with Package Install and Bundle Start steps30 ms003939
Scenario: Starting a job with Package Install step22 ms003232
Scenario: Starting a job with Package Uninstall and Bundle Start steps77 ms003636
Scenario: Starting a job with Package Uninstall step18 ms003333
Scenario: Starting a job with invalid Asset Write step27 ms003131
Scenario: Starting a job with invalid Asset Write step and multiple targets54 ms002929
Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps46 ms003636
Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps and multiple devices65 ms003535
Scenario: Starting a job with invalid Bundle Start step58 ms003131
Scenario: Starting a job with invalid Bundle Stop step28 ms003131
Scenario: Starting a job with invalid Bundle Stop step and multiple devices33 ms002929
Scenario: Starting a job with invalid Command Execution step41 ms002727
Scenario: Starting a job with invalid Configuration Put step20 ms003030
Scenario: Starting a job with invalid Configuration Put step and multiple devices86 ms002828
Scenario: Starting a job with invalid Package Install step24 ms002929
Scenario: Starting a job with invalid Package Install step and multiple devices0.11 sec002626
Scenario: Starting a job with invalid Package Uninstall and Asset Write steps57 ms003434
Scenario: Starting a job with invalid Package Uninstall and Asset Write steps and multiple devices0.2 sec003232
Scenario: Starting a job with invalid Package Uninstall step41 ms002929
Scenario: Starting a job with invalid Package Uninstall step and multiple targets92 ms002626
Scenario: Starting a job with two Bundle Start steps20 ms003939
Scenario: Starting a job with valid Asset Write step78 ms003131
Scenario: Starting a job with valid Asset Write step and multiple targets75 ms002929
Scenario: Starting a job with valid Bundle Start and Bundle Stop steps23 ms003636
Scenario: Starting a job with valid Bundle Start and Bundle Stop steps and multiple devices42 ms003434
Scenario: Starting a job with valid Bundle Start step28 ms003131
Scenario: Starting a job with valid Bundle Stop step32 ms003131
Scenario: Starting a job with valid Bundle Stop step and multiple devices24 ms002929
Scenario: Starting a job with valid Command Execution step0.11 sec002727
Scenario: Starting a job with valid Configuration Put step23 ms003131
Scenario: Starting a job with valid Configuration Put step and multiple devices28 ms002626
Scenario: Starting a job with valid Package Install step23 ms002929
Scenario: Starting a job with valid Package Install step and multiple devices27 ms002626
Scenario: Starting a job with valid Package Uninstall and Asset Write steps22 ms003333
Scenario: Starting a job with valid Package Uninstall and Asset Write steps and multiple devices0.1 sec003232
Scenario: Starting a job with valid Package Uninstall step0.12 sec003030
Scenario: Starting a job with valid Package Uninstall step and multiple targets0.1 sec002626
Scenario: Starting and stopping the simulator should create a device entry and properly set its status7 ms002020
Scenario: Starting job with Asset Write and Bundle Start steps and multiple devices17 ms003232
Scenario: Starting job with Asset Write step and multiple devices15 ms002828
Scenario: Starting job with Bundle Start step and multiple devices17 ms002828
Scenario: Starting job with Bundle Stop and Bundle Start step and multiple devices18 ms003232
Scenario: Starting job with Bundle Stop step and multiple devices21 ms002828
Scenario: Starting job with Command Execution and Bundle Start steps and multiple devices17 ms003232
Scenario: Starting job with Command Execution step and multiple devices17 ms002828
Scenario: Starting job with Configuration Put and Bundle Start steps and multiple devices21 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 devices51 ms003838
Scenario: Starting job with Package Download/Install step and multiple devices74 ms003434
Scenario: Starting job with Package Uninstall and Bundle start steps and multiple device18 ms003232
Scenario: Starting job with Package Uninstall step and multiple device18 ms002727
Scenario: Starting job with invalid Bundle Start step and multiple devices56 ms002929
Scenario: Starting job with invalid Command Execution and Package Install steps23 ms003131
Scenario: Starting job with invalid Command Execution step and multiple devices64 ms002828
Scenario: Starting job with invalid Command Execution, invalid Package Install steps and multiple devices40 ms002929
Scenario: Starting job with invalid Configuration Put and Command Execution steps20 ms003232
Scenario: Starting job with invalid Configuration Put and Command Execution steps and multiple devices27 ms003131
Scenario: Starting job with two Bundle Start steps and multiple devices20 ms003232
Scenario: Starting job with valid Bundle Start step and multiple devices87 ms002929
Scenario: Starting job with valid Command Execution and Package Install steps32 ms003131
Scenario: Starting job with valid Command Execution step and multiple devices93 ms002626
Scenario: Starting job with valid Command Execution, valid Package Install steps and multiple devices62 ms002929
Scenario: Starting job with valid Configuration Put and Command Execution steps46 ms003232
Scenario: Starting job with valid Configuration Put and Command Execution steps and multiple devices62 ms003030
Scenario: Stealing link scenario6 ms002828
Scenario: Step definition factory sanity checks8 ms0022
Scenario: Step definition with a duplicate name10 ms0066
Scenario: Step definition with a null name10 ms0066
Scenario: Step definition with a null scope ID11 ms0066
Scenario: Step definition with an empty name10 ms0055
Scenario: Step factory sanity checks4 ms0022
Scenario: Step with a null scope ID6 ms001111
Scenario: Stop Jetty server for all scenarios3 ms0022
Scenario: Stop broker after all scenarios0.24 sec004646
Scenario: Stop datastore after all scenarios0.22 sec003030
Scenario: Stop event broker for all scenarios2 sec115052
Scenario: Stop job with multiple Asset Write and Package Install steps and one target95 ms003737
Scenario: Stop job with multiple Bundle Start and Package Install steps and one target73 ms003737
Scenario: Stop job with multiple Bundle Stop and Package Uninstall steps and one target55 ms003737
Scenario: Stop job with multiple Command Execution and Package Install steps and one target0.1 sec003434
Scenario: Stop job with multiple Configuration Put and Package Uninstall steps and one target20 ms003535
Scenario: Stop job with multiple targets and Asset Write and Package Install steps and one target30 ms003737
Scenario: Stop job with multiple targets and Bundle Start and Package Install steps0.1 sec003636
Scenario: Stop job with multiple targets and Bundle Stop and Package Uninstall steps23 ms003737
Scenario: Stop job with multiple targets and Command Execution and Package Install steps59 ms003434
Scenario: Stop job with multiple targets and Configuration Put and Package Uninstall steps25 ms003737
Scenario: Test LOOSE user coupling on single connection9 ms002828
Scenario: Test LOOSE user coupling with 3 connections8 ms003838
Scenario: Test STRICT user coupling on single connection14 ms002525
Scenario: Test STRICT user coupling with 3 connections and a reserved user15 ms006363
Scenario: Test STRICT user coupling with user change allowed on single connection9 ms003636
Scenario: Test account query6 ms0044
Scenario: Test the message store with server timestamp indexing14 ms002626
Scenario: Test the message store with timestamp indexing15 ms002626
Scenario: The Client ID is case sensitive6 ms0088
Scenario: To be defined7 ms001313
Scenario: Translating "CommandRequestMessage" to "KuraRequestMessage"40 ms0044
Scenario: Translating CommandRequestMessage to null14 ms0044
Scenario: Translating empty message to empty message12 ms0044
Scenario: Translating from "AssetRequestMessage" to "AssetResponseMessage"14 ms0044
Scenario: Translating invalid jms data message with valid channel, body and metrics into kura data message10 ms0055
Scenario: Translating invalid kura data message with valid channel, body and metrics into jms message7 ms0055
Scenario: Translating invalid kura data message with valid channel, body and metrics into mqtt message9 ms0055
Scenario: Translating kura data message with null channel, and payload without body and with metrics7 ms0055
Scenario: Translating kura data message with valid channel and with null payload7 ms0055
Scenario: Translating kura data message with valid channel and without body and metrics into jms message8 ms0055
Scenario: Translating kura data message with valid channel, and with null payload8 ms0055
Scenario: Translating kura data message with valid channel, body and metrics into jms message10 ms0055
Scenario: Translating kura data message with valid channel, metrics and without body into jms message12 ms0055
Scenario: Translating kura data message with valid channel, metrics and without body into mqtt message8 ms0055
Scenario: Translating null to KuraRequestMessage12 ms0044
Scenario: Translating of jms message with empty payload and invalid topic that contain only userName into kura data message7 ms0055
Scenario: Translating of jms message with empty payload and valid topic into kura data message6 ms0066
Scenario: Translating of jms message with invalid payload and valid topic into kura data message8 ms0066
Scenario: Translating of jms message with valid payload and valid topic into kura data message7 ms0066
Scenario: Translating of mqtt message with invalid payload and invalid topic into kura data message9 ms0055
Scenario: Translating of mqtt message with invalid payload and with null topic into kura data message20 ms0055
Scenario: Translation of kura data message with valid channel and without body and metrics into mqtt message9 ms0055
Scenario: Translation of kura data message with valid channel, body and metrics into mqtt message8 ms0055
Scenario: Translation of kura data message with valid channel, metrics and without body into mqtt message8 ms0055
Scenario: Translation of mqtt message with empty payload into kura data message9 ms0066
Scenario: Translation of mqtt message with invalid payload and invalid topic into kura response message10 ms0055
Scenario: Translation of mqtt message with invalid payload and valid topic into kura data message16 ms0066
Scenario: Translation of mqtt message with invalid payload and valid topic into kura response message12 ms0066
Scenario: Translation of mqtt message with valid payload and invalid topic into kura response message10 ms0055
Scenario: Translation of mqtt message with valid payload and valid topic into kura data message14 ms0066
Scenario: Translation of mqtt message with valid payload and valid topic into kura response message13 ms0066
Scenario: Try to add two different roles with same permissions31 ms002121
Scenario: Try to change an existing connection ID6 ms0077
Scenario: Try to create an access into entity with an invalid role id51 ms001212
Scenario: Try to delete a non existing device from the registry5 ms0044
Scenario: Try to find a device with an invalid client ID7 ms0033
Scenario: Try to find a device with an invalid registry ID8 ms0033
Scenario: Try to find users granted to "admin" role29 ms001212
Scenario: Try to find users that have assigned specific role27 ms001212
Scenario: Try to modify the connection client ID6 ms0077
Scenario: Try to update the device client ID6 ms0044
Scenario: Uncorrect Login While Lockout Policy Is Disabled12 ms001717
Scenario: Uncorrect Login While Lockout Policy Is Enabled8 ms001717
Scenario: Update a group entry in the database10 ms0099
Scenario: Update a group entry with a false ID22 ms001010
Scenario: Update a job XML definition5 ms001010
Scenario: Update a job description5 ms001010
Scenario: Update a job name5 ms001010
Scenario: Update a non existing device6 ms0055
Scenario: Update a nonexistent job6 ms001010
Scenario: Update a nonexistent step definition15 ms0077
Scenario: Update a step definition name10 ms0077
Scenario: Update a step definition processor name10 ms0088
Scenario: Update a step definition target type10 ms0088
Scenario: Update existing role name9 ms0088
Scenario: Update job id of an existing execution item6 ms0088
Scenario: Update schedule which doesn't exist14 ms0055
Scenario: Update scheduler end date5 ms2169
Scenario: Update scheduler name14 ms0088
Scenario: Update scheduler start date13 ms0088
Scenario: Update the end time of an existing execution item5 ms0099
Scenario: Update trigger definition5 ms2158
Scenario: Update user12 ms0077
Scenario: Update user that doesn't exist10 ms0055
Scenario: User locking itself out by using out login attempts5 ms001616
Scenario: User locking itself out with failed attempts and not waiting to unlock6 ms001717
Scenario: User locking itself out with failed attempts and waiting to unlock5 ms001717
Scenario: User login with wrong pass, but with enough time between login failures6 ms001919
Scenario: User not locking itself out by using less than max failed login attempts6 ms001717
Scenario: Validate a device client based search with a null client ID5 ms0055
Scenario: Validate a device client based search with an empty client ID6 ms0055
Scenario: Validate a device client search with null scope6 ms0055
Scenario: Validate a device creator with a null client ID7 ms0066
Scenario: Validate a device creator with a null scope ID8 ms0066
Scenario: Validate a device query with a null Scope ID6 ms0044
Scenario: Validate a device search with a null device ID7 ms0066
Scenario: Validate a device search with a null scope ID6 ms0066
Scenario: Validate a null creator7 ms0055
Scenario: Validate a null device6 ms0055
Scenario: Validate a null device count5 ms0055
Scenario: Validate a null device query6 ms0055
Scenario: Validate a regular creator19 ms0044
Scenario: Validate a regular device client search7 ms0044
Scenario: Validate a regular device count5 ms0044
Scenario: Validate a regular device query6 ms0044
Scenario: Validate a regular device search6 ms0055
Scenario: Validate deleting a device with a null device ID8 ms0066
Scenario: Validate deleting a device with a null scope ID6 ms0066
Scenario: Waiting For Lock Duration Time To Pass11 ms001919
Scenario: Waiting For Reset After Login Counter To Pass10 ms001818
empty) scope0 ms0044